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
no console.log warnings anymore #301
Comments
I fount it comes from nuxt/eslint#2, this rule is only enabled in production now. |
@clarkdo Thanks for the reply, that already solves the development part. But I don't get any warnings/errors when I am in production: e.g. running |
I’ll discuss with team and provide a proper solution, for now I think should be prepending “NODE_ENV=production” in lint scripts link. |
Or override it in eslintrc.js: // add your custom rules here
rules: {
'no-console': 'off'
} |
@miteyema I made a pr for making it |
@manniL Awesome, thank you so much for this fast response! |
Hi
Kudos on the new v2.9.0.
I've used it to scaffold a new project using
yarn create nuxt-app
.It have the following dependencies in
package.json
:When I write for example this:
I don't get any warnings of
console.log
in my code, not foryarn dev
nor foryarn build
.When I used the previous
yarn create nuxt-app
to scaffold a new project, I did get those warnings forconsole.log
.Why this change? Or did I miss something?
The text was updated successfully, but these errors were encountered: