fully support Windows
- Dominant language
- JavaScript
- Stars
- 137
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
npm start
> irc@0.5.0 start E:\Source\irc
> npm run sass && NODE_ENV=production electron ./
> irc@0.5.0 sass E:\Source\irc
> node-sass src/sass/app.scss --output src/static/
Rendering Complete, saving .css file...
Wrote CSS to E:\Source\irc\src\static\app.css
'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! irc@0.5.0 start: `npm run sass && NODE_ENV=production electron ./`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the irc@0.5.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with npm start on Windows and inspect the npm scripts shown in the error, especially the sass and Electron start commands. Check how src/sass/app.scss is compiled and how the production environment is set. Done means npm start completes successfully on Windows without the NODE_ENV command error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, sass
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100