node-env-run
node-env-run copied to clipboard
dkundel
🏃 Node script to load .env variables and execute the give Node file afterwards
It is a good practice to make your test command exit with non-zero code when one of the tests fails. This may be then interpreted easily by i.e. a CI...
Using the `{ "scripts": { "dev": "nodenv .", "test": "nodenv -E test/.env test/test.js" } }` seems rather unclear and not very comprehensive. I tried registering the command for multiple windows...
Running this locally (as a convenience thing), however I noted it broke my CI because no .env file was found. There are a few solutions, however the simplest solution would...
It'd be good to see what's actually changed in each tag instead of just leaving the commit message. For example upgrading from `v4.X.X` to `v3.X.X`. https://github.com/dkundel/node-env-run/releases/tag/v4.0.1
Silences Warning `npm WARN deprecated @types/[email protected]: This is a stub types definition. dotenv provides its own type definitions, so you do not need this installed.`
I want to load `.env` into the current shell environment, does it support this feature?
I have a package.json set up with a "server" script. Running` nodenv server` triggers `start` instead of `server/index.js`. The setup is the generic create-react-app folder. A subfolder added named server...
