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

request: log-level option #7

Closed
builtbylane opened this issue Nov 29, 2014 · 5 comments
Closed

request: log-level option #7

builtbylane opened this issue Nov 29, 2014 · 5 comments

Comments

@builtbylane
Copy link
Sponsor

to allow for console.warn and console.error to remain for instance

@artemyarulin
Copy link

Hi there, +1 for this! Would be really cool to have this options.
I can take care about gulp plugin after it will be implemented

@sindresorhus
Copy link
Owner

Why do you need this? This is meant for stripping debug logging for production. I can see no reason to keep any of that in production.

@artemyarulin
Copy link

Originally my idea was to use this tool during development as well: For example I would like to make my application max verbose during test runs (no strip-debug is used), but during everyday development I have no need to see console.info as it to detailed for me, and for production - absolutely no logs is used.

But now when I wrote it I realized that I just need to use logging framework :) Sorry I took your time, thanks for the project BTW!

@sindresorhus
Copy link
Owner

Yup. A logging framework is the way to go for that :)

@jlocans
Copy link

jlocans commented Mar 22, 2017

Hey.
I am developing sort of javascript api that other client applications can use. Some functions become depricated and it would be nice to keep console.warn() statements there. Maybe you can reconsider adding this option...

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

No branches or pull requests

4 participants