-
Notifications
You must be signed in to change notification settings - Fork 183
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
Option to remove logging of tailwind CSS location #527
Comments
Closing this issue as it is believed to be resolved/stale now - please feel free to comment if it is still an issue in the latest version of the module. |
This is actually still an issue. Don't really need to see this on prod/CI environments |
Do you think this could be a Nuxt feature? The module only really uses the kit utilities' logger. Just adding this check may not be intuitive, and some may want to keep the log message to ensure what files are being used in the build. |
Well, that could be part of a larger conversation. :) I'd love a Nuxt option to only show errors and warnings outside of the core nuxt info, but maybe that's just me. |
I just checked the logger provided by nuxt/kit. It is simply a reference to consola: https://github.com/nuxt/nuxt/blob/main/packages/kit/src/logger.ts Would you take a PR if I add a |
Please 🙂 |
Hi, sorry this has been stale for a while - I thought I had mentioned this - do you think we can make use of CONSOLA_LEVEL for this instead? Could set as environment variable before build and try values 2 or 1. |
This adds the possibility of disabling the following logs: - Tailwind Viewer url - Defined TailwindCSS config path This only happens if everything is ok. Errors will still be visible. The default is set to the nuxt logLevel setting.
@ineshbose I've recreated a PR for this issue based on his work + feedback. |
This issue is relevant to me, as it is populating the terminal and it is useless. |
Lately, this log has been on my mind too and I'm thinking too it should be removed from build logs. Let me see if I do it as part of #798 or a separate commit. |
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
An ability to set an option to disable the console logging of the tailwind.css location.
Describe alternatives you've considered
If not an option, then maybe only log outside production environments?
Additional context
Like to minimize console output during build so I can identify actual problems.
The text was updated successfully, but these errors were encountered: