You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to start extreme-carpaccio server in Windows 11.
C:\Users\nicolas-delsaux\Documents\open-source\extreme-carpaccio\server>npm install
> extreme-carpaccio-server@1.0.0 postinstall
> node_modules/.bin/bower install
'node_modules' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
npm ERR! code 1
npm ERR! path C:\Users\nicolas-delsaux\Documents\open-source\extreme-carpaccio\server
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node_modules/.bin/bower install
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\nicolas-delsaux\AppData\Local\npm-cache\_logs\2022-01-06T13_12_18_644Z-debug.log
NOTICE in the command trying to be run, the path has forward slashes, which are not compatible with Windows path ... I guess it's a bower bug
The text was updated successfully, but these errors were encountered:
I just realised in server/package.json we've got 2 different notations for scripts: ./node_modules and node_modules. npm test uses the former.
I'm wondering whether Windows would treat both the same way.
Another way to work around this is to replace node_modules/.bin/bower by bower in server/package.json . But that would mean you would have to have bower in the PATH.
I'm trying to start extreme-carpaccio server in Windows 11.
NOTICE in the command trying to be run, the path has forward slashes, which are not compatible with Windows path ... I guess it's a bower bug
The text was updated successfully, but these errors were encountered: