You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've also updated everything and found a curious anomaly... When using npx tailwind init to create a tailwind.config.js file, the purge property accepts an array. However it's an object in the tailwind docs so we start with purge: [], at the top of the file and with all other changes everything works fine. But as soon as we want to force a purge (according to the tailwind docs by setting purge to true inside an purge object) like this
purge {
enabled: true
},
// ... other settings here
the tailwind intellisense plugin stops providing suggestions. What's more... when you revert purge back to an empty array (i.e. what you started with), it takes a VS Code reload/restart for intellisense to start providing suggestions again.
I've also updated everything and found a curious anomaly... When using
npx tailwind init
to create atailwind.config.js
file, the purge property accepts an array. However it's an object in the tailwind docs so we start withpurge: [],
at the top of the file and with all other changes everything works fine. But as soon as we want to force a purge (according to the tailwind docs by setting purge to true inside an purge object) like thisthe tailwind intellisense plugin stops providing suggestions. What's more... when you revert purge back to an empty array (i.e. what you started with), it takes a VS Code reload/restart for intellisense to start providing suggestions again.
Curious! Hope that helps to debug.
Originally posted by @gavinworks in #130 (comment)
The text was updated successfully, but these errors were encountered: