Set $NODE_ENV to "development" works best with mocha --require=env-development
npm install env-developmentSet $NODE_ENV to "development".
Works best with mocha --requireenv-development.
Because to force environment, I was used to add process.env.NODE_ENV = "development" at the beginning of every file.
Because relying on Makefile or package.json to set this environment is almost always OK, but when one user just throws mocha in his terminal we don't want to punish him with data loss or any other hell.
Whereas relying on mocha.opts makes it easy (no more ugly line in each test file) and reliable (always loaded).
Install with npm:
npm install env-development
- Install with npm install --save-dev env-development
- Edit test/mocha.opts and add the line --requir env-development
- byteclubfr/node-env-test: Set $NODE_ENV to "test" works best with mocha --require=env-test
See Releases page.
Install devDependencies and Run npm test:
npm i -d && npm test
Pull requests and stars are always welcome.
For bugs and feature requests, please create an issue.
1. Fork it!
2. Create your feature branch: git checkout -b my-new-feature
3. Commit your changes: git commit -am 'Add some feature'
4. Push to the branch: git push origin my-new-feature
5. Submit a pull request :D
MIT © azu