Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
tailwind.config.js file not generated on Windows
See original GitHub issueHi! I’m having the same problem described on issue #26 , same error, I have updated the Vue CLI to verion 4.9.6 but it dit not fix the error. I’m running vue add tailwind on a freshly created project using the vue ui tool.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
tailwind.config.js file not being generated - Stack Overflow
I installed tailwindcss on my next.js project but I couldn't find the tailwind.config.js file. Here is the command I used to install
Read more >Installation - Tailwind CSS
The simplest and fastest way to get up and running with Tailwind CSS from scratch ... Install tailwindcss via npm, and create your...
Read more >Tailwind Setup on Windows - RedwoodJS Community
js file wasn't found in the “web” directory. I did have a tailwind.config.js file in the root of the app and this shed...
Read more >Setting up a Tailwind Project 101 - Visual Code on Windows
config.js file in play. Powershell: "npm install touch-cli -g". Needed in order to command line create files ( ...
Read more >Tailwind CSS | PhpStorm Documentation - JetBrains
PhpStorm recognizes tailwind.config.js files and provides completion based on ... To configure your Tailwind CSS installation, generate a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Have this issue, fixed it by removing spaces from file path directory of my source code.
Thanks, this was the problem!
The source of the problem is that apt-get does not install the latest version of nodejs. Since I had just ran apt-get, I thought I had everything up to date (and IMO its pretty dumb that it wasn’t). Once I manually installed node version 14.18.0 (latest version here), everything worked.