Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm install issues #234

Open
RenzoMarchisi opened this issue Jan 27, 2022 · 4 comments
Open

npm install issues #234

RenzoMarchisi opened this issue Jan 27, 2022 · 4 comments

Comments

@RenzoMarchisi
Copy link

C:\Users\user\janusweb>npm install --only=prod
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '0.10 || 0.12 || 4 || 5' },
npm WARN EBADENGINE current: { node: 'v17.4.0', npm: '8.3.1' }
npm WARN EBADENGINE }

[email protected] postinstall
./utils/init.sh

'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code 1
npm ERR! path C:\Users\user\janusweb
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c ./utils/init.sh

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Local\npm-cache_logs\2022-01-27T19_04_15_622Z-debug-0.log

@jbaicoianu
Copy link
Owner

The build process currently doesn't work directly in Windows, since it uses shell scripts for some of the build steps. The recommended way of building in Windows is to use WSL (I use Ubuntu, but other distros may work as well), and follow the Linux build instructions.

Also, it's a bit strange that npm is trying to install karma even with the --only=prod parameter, karma is only listed in devDependencies, so it should be skipped unless you want to run the unit tests (which are a bit out of date). You might try with --production instead, it seems the argument has changed a couple times over the years.

@RenzoMarchisi
Copy link
Author

ill give that a shot then thanks

@RenzoMarchisi
Copy link
Author

wsl did not seem to wat to work

@madjin
Copy link
Contributor

madjin commented Sep 17, 2022

wsl worked for me, just tested and was able to build 1.5.42 without any issues following same instructions as README

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants