Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autocomplete stops working with an insiders build of Tailwind CSS #562

Closed
arekbartnik opened this issue Jun 2, 2022 · 0 comments · Fixed by #571
Closed

Autocomplete stops working with an insiders build of Tailwind CSS #562

arekbartnik opened this issue Jun 2, 2022 · 0 comments · Fixed by #571

Comments

@arekbartnik
Copy link

What version of Tailwind CSS IntelliSense are you using?

v0.8.5

What version of Tailwind CSS are you using?

insiders

What package manager are you using?

yarn

What operating system are you using?

macOS

Reproduction URL

https://github.com/ArekBartnik/tailwind-insiders-intellisense-bug
main branch: Nextjs app with Tailwind CSS v3.0.24 (autocomplete works)
tw-insiders branch: Nextjs app with Tailwind CSS insiders (autocomplete doesn't work)

Describe your issue

Whenever I use an insiders build of Tailwind CSS autocomplete stops working.

In "output" I can see:

Found Tailwind CSS config file: [redacted]/tailwind-insiders-intellisense-bug/tailwind.config.js
Loaded postcss v8.4.14: [redacted]/tailwind-insiders-intellisense-bug/node_modules/postcss
Loaded tailwindcss v0.0.0-insiders.1f74568: [redacted]/tailwind-insiders-intellisense-bug/node_modules/tailwindcss

warn - The `purge`/`content` options have changed in Tailwind CSS v3.0.
warn - Update your configuration file to eliminate this warning.
warn - https://tailwindcss.com/docs/upgrade-guide#configure-content-sources

warn - The `content` option in your Tailwind CSS configuration is missing or empty.
warn - Configure your content sources or your generated CSS will be missing styles.
warn - https://tailwindcss.com/docs/content-configuration

I know using an insiders build means not everything working correctly, but I would like to know if this is a fixable bug or something I should expect?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant