next »

[Laurent G.]

Hi,

I'm sharing this in case in can help someone else. Best,

Laurent

----

Environment:
Windows 10 64bit

λ nvm use 16.15.1 (required for GBC 1.00.61)
Now using node v16.15.1 (64-bit)

λ node -v
v16.15.1

λ npm -v
8.11.0

λ nvm -v | head -2
Running version 1.1.7

Error:

Solution:

The key to success was to update nvm to 1.1.9 following the steps described here https://tecadmin.net/install-nodejs-with-nvm-on-windows/
The github project is located here https://github.com/coreybutler/nvm-windows/releases
Note that I had to run nvm-setup.exe as admin
Consequently, I had to run 'nvm install 16.15.0' (did also 'nvm uninstall 16.15.0') + 'nvm use 16.15.0' in a command prompt with Admin privileges
Every other subsequent documented commands could be run with standard user privileges
Finally the GBC dev project was polluted from the previous test, so I had to wipe it and unzipping 'fresh' again from the downloaded package
Note also that I patched npm + npm.cmd to avoid the -g / global warning and now 'npm -v' runs without warning. However, npm run install-gbc still displays the warnings ... not sure why (didn't spend much time investigating, this is more of an FYI at this point since everything else works)[/li][/list]

[Laurent G.]

Hi,

I'm sharing this in case in can help someone else. Best,

Laurent

----

Environment:
Windows 10 64bit

λ nvm use 16.15.1 (required for GBC 1.00.61)
Now using node v16.15.1 (64-bit)

λ node -v
v16.15.1

λ npm -v
8.11.0

λ nvm -v | head -2
Running version 1.1.7

Error:
λ npm install
npm ERR! Unexpected token '.'

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\LaurentGalais\AppData\Local\npm-cache\_logs\2022-06-14T17_58_40_210Z-debug-0.log

Solution:

The key to success was to update nvm to 1.1.9 following the steps described here https://tecadmin.net/install-nodejs-with-nvm-on-windows/
The github project is located here https://github.com/coreybutler/nvm-windows/releases
Note that I had to run nvm-setup.exe as admin
Consequently, I had to run 'nvm install 16.15.0' (did also 'nvm uninstall 16.15.0') + 'nvm use 16.15.0' in a command prompt with Admin privileges
Every other subsequent documented commands could be run with standard user privileges
Finally the GBC dev project was polluted from the previous test, so I had to wipe it and unzipping 'fresh' again from the downloaded package
Note also that I patched npm + npm.cmd to avoid the -g / global warning and now 'npm -v' runs without warning. However, npm run install-gbc still displays the warnings ... not sure why (didn't spend much time investigating, this is more of an FYI at this point since everything else works)

[Laurent G.]

Second post is the corrected one with the error listed. Sorry about that!