fix bugs:

[snovey]

The value of process.env.NODE_ENV is never set to development in the project.

Only run npm run build will get correct value of process.env.NODE_ENV, other command will get undefined.

I want to lint no-debugger when run npm run lint or npm run build but not lint no-debugger when run npm run dev.(EsLint is going to read the .eslintrc.js file very early on, so to set the value of process.env.NODE_ENV before that, set the value in dev-runner file).

Sorry for my poor English...

[shavidzet]

I don't think it's right way to fix this bug.

[snovey]

So stupid mistake!
Thank you for reminding me. I have fixed it. Is this the desired result now?

[shavidzet]

1. process.env.NODE_ENV is undefined in .eslintrc.js in development mode, because we are not passing string while linter runs, but for production it reads production as string, it works how it should and .eslintrc.js doesn't need changes.
2. Highlighted third line in your code, I think is wrong way to pass data for NODE_ENV, you can do it same way as we did for production:
   

   electron-vue/template/package.json

   Line 34 in 8fae476

   "pack:renderer": "cross-env NODE_ENV=production webpack --progress --colors --config .electron-vue/webpack.renderer.config.js",

   
   right example:
   cross-env NODE_ENV=development webpack --progress --colors --config .electron-vue/webpack.renderer.config.js

Conclusion:
debugger for development environment already works fine and currently we have only two mode for NODE_ENV: development & production, in most cases NODE_ENV is undefined because we start coding from development and then we separate environment for production.
I hope you understand idea