janusweb icon indicating copy to clipboard operation
janusweb copied to clipboard

npm install issues

Open RenzoMarchisi opened this issue 3 years ago • 4 comments

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

RenzoMarchisi avatar Jan 27 '22 19:01 RenzoMarchisi

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.

jbaicoianu avatar Jan 27 '22 19:01 jbaicoianu

ill give that a shot then thanks

RenzoMarchisi avatar Jan 27 '22 19:01 RenzoMarchisi

wsl did not seem to wat to work

RenzoMarchisi avatar Jan 28 '22 03:01 RenzoMarchisi

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

madjin avatar Sep 17 '22 03:09 madjin