[ERR_MODULE_NOT_FOUND]: Cannot find package 'tailwindcss'
Just followed the
https://docs.opensaas.sh/start/getting-started/ page
I 'm not able to launch the blog,
see the error bellow
not sure about how to manage that
OpenSaaS.sh
Getting Started
Open SaaS is a free, open-source, full-stack SaaS starter kit for React + NodeJS.
12 Replies
Hi @arnaudlpz. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but as an AI assistant for Wasp, I can only provide information related to the Wasp framework. The error you're encountering seems to be related to the OpenSaaS project, which is not directly related to Wasp.
However, the error message
[ERR_MODULE_NOT_FOUND]: Cannot find package 'tailwindcss' typically indicates that the tailwindcss package is not installed in your project. You might need to install it using npm or yarn.
In a Wasp project, you would typically add support for Tailwind by adding two config files — tailwind.config.cjs and postcss.config.cjs — to the root directory of your project. Wasp then installs the necessary dependencies and copies your configuration to the generated project. You can then use Tailwind CSS directives in your CSS and Tailwind classes on your React components source (https://wasp-lang.dev/docs/project/css-frameworks#tailwind).
If you're using Wasp and have followed these steps but are still encountering the error, make sure to restart wasp start. This is sometimes needed to ensure that Wasp picks up the changes and enables Tailwind integration source (https://wasp-lang.dev/docs/project/css-frameworks#tailwind).
If you're not using Wasp, I recommend checking the documentation of the framework or tool you're using for how to add support for Tailwind CSS.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @arnaudlpz, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Did you run
npm install in the blog folder?yep
Did you install anything extra or modify the code in any way?
I just tried it with wasp 0.15 and it works for me hm! I thought that our newly added
type: module in package.json of blog might be an issue, but I can't replicate it on my side.
What is your node / npm version @arnaudlpz ?latests
The blog works for me with:
I'm not sure how to help you next, this is not really a Wasp related issue, but rather Astro related issue. Could you maybe ask in their Github / Discord and see what they say?
Got it thanks @miho !
Wohooo @arnaudlpz, you just became a Waspeteer level 1!
Note: odd node versions are usually meant for experimentation / testing -> so try it with node 22.
@martinsos thanks of the head's up