question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm install fails on windows

See original GitHub issue

I have tried downloading master and a release (V1.7.9).

I cannot get it to run.

On my last attempt, after following instructions here when i run npm install I get…

c:\crowi-1.7.9>npm install

> node-sass@4.12.0 install c:\crowi-1.7.9\node_modules\node-sass
> node scripts/install.js

Cached binary found at C:\ProgramData\npmglobal-cache\node-sass\4.12.0\win32-x64-64_binding.node

> core-js@2.6.9 postinstall c:\crowi-1.7.9\node_modules\@babel\runtime-corejs2\node_modules\core-js
> node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> node-sass@4.12.0 postinstall c:\crowi-1.7.9\node_modules\node-sass
> node scripts/build.js

Binary found at c:\crowi-1.7.9\node_modules\node-sass\vendor\win32-x64-64\binding.node
Testing binary
Binary is fine

> nodemon@1.19.1 postinstall c:\crowi-1.7.9\node_modules\nodemon
> node bin/postinstall || exit 0


> crowi@1.7.9 postinstall c:\crowi-1.7.9
> npm run build


> crowi@1.7.9 build c:\crowi-1.7.9
> npm run prod:client


> crowi@1.7.9 prod:client c:\crowi-1.7.9
> NODE_ENV=production webpack --bail --colors --display-error-details --config tools/webpack.config.js

'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! crowi@1.7.9 prod:client: `NODE_ENV=production webpack --bail --colors --display-error-details --config tools/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crowi@1.7.9 prod:client 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:
npm ERR!     C:\ProgramData\npmglobal-cache\_logs\2019-10-03T10_11_32_360Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! crowi@1.7.9 build: `npm run prod:client`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crowi@1.7.9 build 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:
npm ERR!     C:\ProgramData\npmglobal-cache\_logs\2019-10-03T10_11_32_407Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! crowi@1.7.9 postinstall: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crowi@1.7.9 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Is there some pre-reqs I need other than listed in the documentation?

Could you guild me how to run crowi locally from SRC and from release?

Thanks, Steve.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
sotarokcommented, Oct 8, 2019

Hmm, it might be a path related issue. Sorry I don’t have Windows environment and I haven’t care of it, but It could be fixed by edit webpack or somewhere around the build path I think …

(And also sorry about missing translation for Admin screens. It could be a good first issue so could you please send a PR if you wanna try it 🙇 )

0reactions
sotarokcommented, Oct 24, 2019

@Steve-Mcl It would be work correctly. (The reason why there are en and en-US dir is because fluctuation of locale names between several libraries or environments.) If you try moving the directory and it works, could you please send a pull request? I don’t have Windows environment and I can’t try it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

This npm install is not working on Windows - node.js
This npm install is not working on Windows · ran it as admin, · tried npm install -g · restarted the XAMPP server...
Read more >
5 Ways to Fix the Npm Install Not Working Issue
Way 1. Make Sure Npm Is Installed · Way 2. Make Sure There Is a Package.json File · Way 3. Delete Lock File...
Read more >
How to fix npm install command not working
The error above happens when npm can't be found under the PATH environment variable. First, you need to make sure that npm is...
Read more >
Common errors | npm Docs
It's most likely a temporary npm registry glitch. Check npm server status and try again later. · If the error persists, perhaps the...
Read more >
NodeJS - npm install errors on Windows - YouTube
NOTE: If you are using Windows 10, you will want to open an Administrator PowerShell (right-click and choose "Run as administrator").
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found