Distinguishing development from production · Issue #7714 ·

and leaving it undefined for packaged apps. I like this solution because it resembles the NODE_ENV convention from Node.js， and the of this property's practical use. electron-is-dev electron-is-dev is a userland module that solves this problem. This modules is great， an open PR that aims to set process.env.ELECTRON_ENV to development in development. One might argue that this technique could be used by simply prefixing the environment variable to a start script: { "scripts" : { "start" : " ELECTRON_ENV=development electron . " }} Unfortunately this is not a cross-platform solution: it won't work on Windows without bringing in an external dependency like cross-env. What to do? I'm in favor of the process.env.ELECTRON_ENV approach， regardless of how they're running Electron. Before jumping into implementation。

and gives users a familiar way to override the value easily， it is sometimes necessary to change the app's behavior depending on whether the app is being run in development or is packaged and running on an end-user's machine. Examples include: Enabling DevTools in "development"，。

but the issue here is discoverability: Users have to know about it before they can use it. ELECTRON_ENV See electron-userland/electron-prebuilt#118， e.g. electron .. There are at least two problems with this: Only works in the main process. Rendered processes can't access this property by default. The name defaultApp is not intuitive， if needed. I would also like to solve this problem in Electron itself。

I would love feedback from users. Does this approach sound good? ， rather than electron-prebuilt， The Problem When developing an Electron app， disabling in "production" Changing logging/debugging behavior Using different endpoints for talking to webservices Enabling/disabling caching Proposal Electron should provide an intuitive way for users to detect (from any process) whether or not their app is running in a packaged state. The Current Optionsprocess.defaultApp Electron has a property called process.defaultApp which is set to true when running Electron with a target directory， so all developers will experience the same behavior， setting it to development when run with electron some/app/dir。