fix: allow nuxt.options.pages to be unset

[maddysrc]

Weirdly enough the default isn't always set. The default is actually equal to "is the pages directory not empty" but assuming undefined means true is fine in this case as its only used to add a glob.

I also noticed use of nuxt.options.dir.modules causes an error to be logged to console, but removing that would be a breaking change now.

[16:13:24]  ERROR  This module cannot be imported in the Vue part of your app. [importing nuxt/kit from modules/my-module.ts]

[ineshbose]

I also noticed use of nuxt.options.dir.modules causes an error to be logged to console

That's a good point; Tailwind JIT is picking up nuxt/kit string and causes that warning - I am up for removing modules, as it can be added by users' configs and merged using defu.

As modules was never added in the content paths by this module in the first place (before 6.9.0), I don't believe it'll be a breaking change.

[maddysrc]

As modules was never added in the content paths by this module in the first place (before 6.9.0), I don't believe it'll be a breaking change.

As it got a proper release on npm, even for just a day, I would say it is. I'm up to remove the pattern in this or another PR though.

[ineshbose]

I've opened a separate PR for that #748 - let's take discussion there if we want to continue.

[ineshbose]

Thanks for this PR though - this is a brilliant spot! 😄

[netlify]

‼️ Deploy request for nuxt-tailwindcss rejected.

Name	Link
🔨 Latest commit	4052e11