'NODE_ENV' is not recognized as an internal or external command, operable program or batch file. Windows
- Dominant language
- Vue
- Stars
- 257
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
the back-end will not run on Windows, after following all the steps due to the error
> 'NODE_ENV' is not recognized as an internal or external command, operable program or batch file.
only way to get back-end to run is to edit the script source in package.json to
> "scripts": {
> "start": "npm run start:local",
> "start:local": "SET NODE_ENV=local & nodemon index.js",
> "start:dev": "SET NODE_ENV=development & nodemon index.js",
> "start:prod": "SET NODE_ENV=production & node index.js",
> "test": "jest --coverage",
> "seed": "node scripts/seed.js",
> "update-permissions": "node scripts/update-permissions.js",
> "precommit": "lint-staged",
> "lint": "eslint --fix **/*.js ./"
> },
as explained [here](https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the scripts in package.json and run the affected backend start command on Windows to reproduce the NODE_ENV error. Compare the listed start scripts with the Windows workaround in the issue, then verify that the backend starts successfully through the documented commands without manual package.json edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100