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

Option to remove logging of tailwind CSS location #527

Closed
JohnCampionJr opened this issue Sep 1, 2022 · 10 comments
Closed

Option to remove logging of tailwind CSS location #527

JohnCampionJr opened this issue Sep 1, 2022 · 10 comments
Labels
enhancement New feature or request

Comments

@JohnCampionJr
Copy link

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.

@JohnCampionJr JohnCampionJr added the enhancement New feature or request label Sep 1, 2022
@ineshbose
Copy link
Collaborator

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.

@ineshbose ineshbose closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2023
@JohnCampionJr
Copy link
Author

This is actually still an issue. Don't really need to see this on prod/CI environments

@ineshbose
Copy link
Collaborator

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.

@JohnCampionJr
Copy link
Author

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.

@JohnCampionJr
Copy link
Author

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 quiet option? Would default to false as to be a non-breaking change.

@ineshbose
Copy link
Collaborator

Please 🙂

@ineshbose
Copy link
Collaborator

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.

jpsc added a commit to jpsc/tailwindcss that referenced this issue Oct 19, 2023
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.
@jpsc
Copy link

jpsc commented Oct 19, 2023

@ineshbose I've recreated a PR for this issue based on his work + feedback.

@Redskinsjo
Copy link

This issue is relevant to me, as it is populating the terminal and it is useless.

@ineshbose
Copy link
Collaborator

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.

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

Successfully merging a pull request may close this issue.

4 participants