Allow .env. file for environments other than 'production' or 'development'

[manguluka]

Ran into this while trying to create a .env.staging.local file, and having .env.development.local loaded, ignoring my NODE_ENV=staging override.

razzle/packages/razzle/config/createConfig.js

Line 62 in b6d3c35

process.env.NODE_ENV = IS_PROD ? 'production' : 'development';

I'd like to be able to set the NODE_ENV environment variable to any value, and have the .env files for that environment be usable. It seems like removing the linked line would allow this.

[stale]

Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

[stale]

ProBot automatically closed this due to inactivity. Holler if this is a mistake, and we'll re-open it.