Suggestion: Add a comment linking to full tailwind default config in tailwind.config.js

[connecteev]

As mentioned earlier here, I can no longer peek into my tailwind configuration to check what width values I have, etc.

Does it make sense to scaffold the entire default configuration using npx tailwind init --full as mentioned here? I am not sure, because it would defeat the purpose of a skinny tailwind config. Perhaps add a comment to this config file that either:

• shows the location of the full config file (still tedious to click several folders deep under node_modules, I am lazy and like convenience)
• links to a page (on tailwindcss.com) that has the full config file, based on what version of tailwind you're on (my preference)

[connecteev]

Closing this as it's not really a good solution, and I can peek into the tailwind docs or the generated css file.