Failed to compile - Error: Can't resolve '...' .bg-

[facos86]

What version of Tailwind CSS are you using?
"react": "^17.0.2",
"cross-env": "7.0.3",
"cssnano": "5.1.10",
"postcss-cli": "9.1.0",
"react-error-overlay": "^6.0.9",
"release-it": "13.6.4",
"tailwindcss": "^3.0.24",
"autoprefixer": "^10.4.7"

Describe your issue

Hi,
I am encountering a problem with the latest version of tailwindcss.
It generates "background-image: url('...');" in tailwind.output.css, the three dots '...' cannot be resolved.

Is there any configuration issues or is there a bug with my current stup ?

[adamwathan]

Hey! Those look like classes being generated based on Tailwind's test suite, which makes me think your content configuration is watching node_modules when it shouldn't be.

https://tailwindcss.com/docs/content-configuration#pattern-recommendations

[Drex72]

Were you able to solve this?

[boblamceo]

@ZeeshanAhmadKhalil same here

[tomBoyd9002]

I am getting this error:

Module not found: Can't resolve './${selectedImagePath}'

Import trace for requested module:
./styles/globals.css
./pages/_app.js

because I used variable inside the tailwind class as follows

bg-[url('${selectedImagePath}')]

Now i am unable to reset my output file globals.css and the error persists.

delete the

I am getting this error:

Module not found: Can't resolve './${selectedImagePath}'

Import trace for requested module:
./styles/globals.css
./pages/_app.js

because I used variable inside the tailwind class as follows

bg-[url('${selectedImagePath}')]

Now i am unable to reset my output file globals.css and the error persists.

Delete the bg variable save and restart the server, then put a working bg variable in, then save and refresh the server, it will reset your global css. I have no clue how to make it display properly sadly.

[ZeeshanAhmadKhalil]

@boblamceo i found an old yarn.lock file which made it run. I was unable to resolve the above error which I get when generating new yarn.lock file and then implementing the above solution.

[kenny-67]

@tomBoyd9002 How were you able to resolve your issue?