npm ERR! Unexpected token '.' with with nvm-windows <= 1.1.7

[syedbilal07]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

I have updated to the latest npm v8.3.1 and it is showing me an error while using the command "npm outdated -g --depth=0". See the image; https://imgur.com/a/5fMZlye. It was fine on v8.3.0. What is the solution?

Expected Behavior

It should return the outdated packages after a successful run. But it is giving error.

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...
   I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment.

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

; "user" config from C:\Users\Bilal.npmrc

registry = "http://registry.npmjs.org/"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Users\Bilal
; HOME = C:\Users\Bilal
; Run npm config ls -l to show all defaults.

[syedbilal07]

27 verbose stack SyntaxError: Unexpected token '.'
27 verbose stack at Object.compileFunction (node:vm:352:18)
27 verbose stack at wrapSafe (node:internal/modules/cjs/loader:1026:15)
27 verbose stack at Module._compile (node:internal/modules/cjs/loader:1061:27)
27 verbose stack at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
27 verbose stack at Module.load (node:internal/modules/cjs/loader:975:32)
27 verbose stack at Function.Module._load (node:internal/modules/cjs/loader:822:12)
27 verbose stack at Module.require (node:internal/modules/cjs/loader:999:19)
27 verbose stack at require (node:internal/modules/cjs/helpers:102:18)
27 verbose stack at Object. (C:\Program Files\nodejs\node_modules\npm\lib\commands\outdated.js:11:18)
27 verbose stack at Module._compile (node:internal/modules/cjs/loader:1097:14)

[syedbilal07]

Fixed it on my own. Please replace it with my version https://files.fm/u/sz3yrgsvj

[dcodeIO]

Seeing this issue on GitHub actions as well. Seems to be isolated to "windows" images running Node.js 17:

https://github.com/AssemblyScript/assemblyscript/runs/4856320026?check_suite_focus=true#step:4:4

OS: Microsoft Windows Server 2019 10.0.17763
Node.js: 17.4.0
npm: 8.3.1

[syedbilal07]

Facing this issue on npm install script too.

[syedbilal07]

27 verbose stack ../workspaces/libnpmfund
27 verbose stack ^
27 verbose stack
27 verbose stack SyntaxError: Unexpected token '.'

[bonesoul]

same here..

[bonesoul]

any fixes for this?

[syedbilal07]

Not yet. Waiting for the community member to resolve this

[ruyadorno]

hi @syedbilal07 it would be interesting to look at the log files to see understand better what could have happened there, if that's something you can provide us. (or anyone else having this issue)

[UziTech]

I don't know if there is a way to look at the logs in github actions but here is one that is failing. https://github.com/coffeelint/coffeelint/runs/4960440881

Run npm ci
  npm ci
  shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
npm ERR! Unexpected token '.'

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\npm\cache\_logs\2022-01-27T01_47_31_169Z-debug-0.log
Error: Process completed with exit code 1.

[halcwb]

The log files for the error:

log file

0 verbose cli [ 0 verbose cli 'C:\\Program Files\\nodejs\\node.exe', 0 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 0 verbose cli 'install' 0 verbose cli ] 1 info using npm@8.3.1 2 info using node@v17.4.0 3 timing npm:load:whichnode Completed in 0ms 4 timing config:load:defaults Completed in 2ms 5 timing config:load:file:C:\Users\halcw\AppData\Roaming\nvm\v17.4.0\node_modules\npm\npmrc Completed in 24ms 6 timing config:load:builtin Completed in 24ms 7 timing config:load:cli Completed in 2ms 8 timing config:load:env Completed in 0ms 9 timing config:load:file:C:\Development\halcwb\apps\GenPres2\.npmrc Completed in 0ms 10 timing config:load:project Completed in 3ms 11 timing config:load:file:C:\Users\halcw\.npmrc Completed in 0ms 12 timing config:load:user Completed in 0ms 13 timing config:load:file:C:\Program Files\nodejs\etc\npmrc Completed in 1ms 14 timing config:load:global Completed in 1ms 15 timing config:load:validate Completed in 0ms 16 timing config:load:credentials Completed in 1ms 17 timing config:load:setEnvs Completed in 1ms 18 timing config:load Completed in 36ms 19 timing npm:load:configload Completed in 36ms 20 timing npm:load:setTitle Completed in 1ms 21 timing config:load:flatten Completed in 3ms 22 timing npm:load:display Completed in 5ms 23 verbose logfile C:\Users\halcw\AppData\Local\npm-cache\_logs\2022-01-26T17_31_57_523Z-debug-0.log 24 timing npm:load:logFile Completed in 52ms 25 timing npm:load:timers Completed in 0ms 26 timing npm:load:configScope Completed in 0ms 27 timing npm:load Completed in 94ms 28 verbose stack C:\Users\halcw\AppData\Roaming\nvm\v17.4.0\node_modules\npm\node_modules\libnpmfund:1 28 verbose stack ../workspaces/libnpmfund 28 verbose stack ^ 28 verbose stack 28 verbose stack SyntaxError: Unexpected token '.' 28 verbose stack at Object.compileFunction (node:vm:352:18) 28 verbose stack at wrapSafe (node:internal/modules/cjs/loader:1026:15) 28 verbose stack at Module._compile (node:internal/modules/cjs/loader:1061:27) 28 verbose stack at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10) 28 verbose stack at Module.load (node:internal/modules/cjs/loader:975:32) 28 verbose stack at Function.Module._load (node:internal/modules/cjs/loader:822:12) 28 verbose stack at Module.require (node:internal/modules/cjs/loader:999:19) 28 verbose stack at require (node:internal/modules/cjs/helpers:102:18) 28 verbose stack at Object. (C:\Users\halcw\AppData\Roaming\nvm\v17.4.0\node_modules\npm\lib\utils\reify-output.js:16:38) 28 verbose stack at Module._compile (node:internal/modules/cjs/loader:1097:14) 29 verbose cwd C:\Development\halcwb\apps\GenPres2 30 verbose Windows_NT 10.0.19043 31 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" 32 verbose node v17.4.0 33 verbose npm v8.3.1 34 error Unexpected token '.' 35 verbose exit 1 36 timing npm Completed in 308ms 37 verbose code 1 38 error A complete log of this run can be found in: 38 error C:\Users\halcw\AppData\Local\npm-cache\_logs\2022-01-26T17_31_57_523Z-debug-0.log

On my machine:
Runtime Environment:
OS Name: Windows
OS Version: 10.0.19043
OS Platform: Windows
RID: win10-x64

Luckily I use nvm so I could easily revert back to node 17.3.1.

[syedbilal07]

Hi @ruyadorno, I am now using npm v8.3.0 with node 17.4.0. I cannot provide the full log right now and I do not want to upgrade to npm v8.3.2. Please check the logs on your end and run tests on Github so you can figure it out. I have provided stack trace of the issue above. I think that could help.

[feeldiac]

I had a similar issue when using npm init and npm install. I downgrade my node version to 16.13.2 (recommended for most users) and it works.

[RodEsp]

Heya @syedbilal07 was this actually fixed or did you just close it because you're using your own workaround?

[bonesoul]

use the newest version of npm and u should be fine. just skip 8.3.1.

[kernju]

I also have the same issue, using nvm for Windows (Node 17.4.0, npm 8.3.1).

0 verbose cli [
0 verbose cli 'C:\Program Files\nodejs\node.exe',
0 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
0 verbose cli 'install',
0 verbose cli '-g',
0 verbose cli '@angular/cli'
0 verbose cli ]
1 info using npm@8.3.1
2 info using node@v17.4.0
3 timing npm:load:whichnode Completed in 0ms
4 timing config:load:defaults Completed in 1ms
5 timing config:load:file:C:\Users\xxx\AppData\Roaming\nvm\v17.4.0\node_modules\npm\npmrc Completed in 2ms
6 timing config:load:builtin Completed in 2ms
7 timing config:load:cli Completed in 2ms
8 timing config:load:env Completed in 0ms
9 timing config:load:project Completed in 3ms
10 timing config:load:file:C:\Users\xxx.npmrc Completed in 1ms
11 timing config:load:user Completed in 1ms
12 timing config:load:file:C:\Program Files\nodejs\etc\npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:validate Completed in 1ms
15 timing config:load:credentials Completed in 1ms
16 timing config:load:setEnvs Completed in 1ms
17 timing config:load Completed in 12ms
18 timing npm:load:configload Completed in 12ms
19 timing npm:load:setTitle Completed in 0ms
20 timing config:load:flatten Completed in 2ms
21 timing npm:load:display Completed in 3ms
22 verbose logfile C:\Users\xxx\AppData\Local\npm-cache_logs\2022-02-04T14_14_48_111Z-debug-0.log
23 timing npm:load:logFile Completed in 13ms
24 timing npm:load:timers Completed in 0ms
25 timing npm:load:configScope Completed in 0ms
26 timing npm:load Completed in 30ms
27 verbose stack C:\Users\xxx\AppData\Roaming\nvm\v17.4.0\node_modules\npm\node_modules\libnpmfund:1
27 verbose stack ../workspaces/libnpmfund
27 verbose stack ^
27 verbose stack
27 verbose stack SyntaxError: Unexpected token '.'
27 verbose stack at Object.compileFunction (node:vm:352:18)
27 verbose stack at wrapSafe (node:internal/modules/cjs/loader:1026:15)
27 verbose stack at Module._compile (node:internal/modules/cjs/loader:1061:27)
27 verbose stack at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
27 verbose stack at Module.load (node:internal/modules/cjs/loader:975:32)
27 verbose stack at Function.Module._load (node:internal/modules/cjs/loader:822:12)
27 verbose stack at Module.require (node:internal/modules/cjs/loader:999:19)
27 verbose stack at require (node:internal/modules/cjs/helpers:102:18)
27 verbose stack at Object. (C:\Users\xxx\AppData\Roaming\nvm\v17.4.0\node_modules\npm\lib\utils\reify-output.js:16:38)
27 verbose stack at Module._compile (node:internal/modules/cjs/loader:1097:14)
28 verbose cwd C:\Program Files\nodejs
29 verbose Windows_NT 10.0.19043
30 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "@angular/cli"
31 verbose node v17.4.0
32 verbose npm v8.3.1
33 error Unexpected token '.'
34 verbose exit 1
35 timing npm Completed in 208ms
36 verbose code 1
37 error A complete log of this run can be found in:
37 error C:\Users\xxx\AppData\Local\npm-cache_logs\2022-02-04T14_14_48_111Z-debug-0.log

[shubhambattoo]

use the newest version of npm and u should be fine. just skip 8.3.1.

how to do that? to update npm you need npm.

[kernju]

I finally used the latest Node.js LTS, 16.3.2, and it worked.

[cristiand391]

Yesterday node v16.14.0 (latest LTS) was released, and it includes npm v8.3.1 so there's no way to make npm update itself.
If you see this error when running latest LTS on windows, you might want to install previous LTS v16.13.2 👍🏼

[gfieremans]

use the newest version of npm and u should be fine. just skip 8.3.1.

how to do that? to update npm you need npm.

Just ran in the same issue with node 16.14.0. You can download 8.3.2 tgz file and manually replace npm in your node_modules directory of the node version you have.

[piotr-kubica]

Similar issue for v16.17.0.

[micke-dahlgren]

Why is this closed? any resolution? Issue still exists

This issue was fixed with nvm 1.1.9. See @TGTGamer reply for instructions.

[nelsson]

Why is this closed? any resolution? Issue still exists

This issue was fixed with nvm 1.1.9. See @TGTGamer reply for instructions.

It works!

[pillesy]

Upgrading to nvm 1.1.9. did not immediately fix the issue for me, I had to uninstall and reinstall the broken node version.

• Uninstall broken versions of node (nvm uninstall )
• Reinstall needed node version (nvm install )
• Use node version just installed (nvm use )

[micke-dahlgren]

@TGTGamer already outlined this. :)
#4234 (comment)

[jkupcho]

I'm also having this issue, it seems like this problem started with version 8.3.1.

[arcreigh]

Can confirm in current NPM build this is a problem.

[WORMSS]

NVM Version 1.1.10 has all these problems (plus the elevation problem) fixed.
Upgrade nvm, and then remove the broken node versions and re-install them.

Everything now works as expected.

[j-avila]

in my case I fix it uninstalling nvm and all versions of node and install everything again via chocolatey, nvm (latest version) and node 16.13.0 and works as expected.

[SensSebastianSchlosser]

NVM Version 1.1.10 has all these problems (plus the elevation problem) fixed. Upgrade nvm, and then remove the broken node versions and re-install them.

Everything now works as expected.

This is the solution!

[aoneahsan]

these are the versions that led me to this thread: nvm: 1.1.5 node: 16.14.0 npm: 8.3.1

I was getting that nasty "Unexpected token '.'" error when trying to install, check version, and using npx (which was my main concern since I needed it for a script). I then tried switching versions:

nvm: 1.1.5 node: 16.17.0 npm: 8.15.0

I was still getting that error, so I did something similar to what @srsgores mentioned (all from a PowerShell command prompt running as Administrator):

1. updated nvm to 1.1.9 (did this using chocolatey, not using the .exe installer)
2. uninstalled both 16.14.0 and 16.17.0 versions of node
3. reinstalled 16.17.0 version of node (latest LTS release at the moment of writing this comment)

After that, everything was working correctly again. My guess is nvm's version was the culprit, but I'm not sure. I hope this is of use to someone.

This resolved the issue for me, uninstalled the "nvm" installed using ".exe" file and reinstall using "chocolatey"
and then install the node again and use that it will work (at least worked for me :)

[sleepinzombie]

The above works for me as well.
Thank you @aoneahsan!

[mohammadmoth]

these are the versions that led me to this thread: nvm: 1.1.5 node: 16.14.0 npm: 8.3.1
I was getting that nasty "Unexpected token '.'" error when trying to install, check version, and using npx (which was my main concern since I needed it for a script). I then tried switching versions:
nvm: 1.1.5 node: 16.17.0 npm: 8.15.0
I was still getting that error, so I did something similar to what @srsgores mentioned (all from a PowerShell command prompt running as Administrator):

1. updated nvm to 1.1.9 (did this using chocolatey, not using the .exe installer)
2. uninstalled both 16.14.0 and 16.17.0 versions of node
3. reinstalled 16.17.0 version of node (latest LTS release at the moment of writing this comment)

After that, everything was working correctly again. My guess is nvm's version was the culprit, but I'm not sure. I hope this is of use to someone.

This resolved the issue for me, uninstalled the "nvm" installed using ".exe" file and reinstall using "chocolatey" and then install the node again and use that it will work (at least worked for me :)

I deleted all versions of node 18, and then re-downloaded it, it works.

[webdevatanas]

I am using windows and here is how I fixed it:

1. Uninstall nvm from windows(you can do that from Add and remove programs). This will remove also the node versions installed with the nvm previously so you do not need manually to uninstall all before uninstall the whole nvm.
2. Install the latest nvm from here https://github.com/coreybutler/nvm-windows/tags . 1.1.10 is the latest to this date.
3. nvm install 'your prefered version' then nvm use 'the installed version'
4. Whoala!

[dosstx]

I am using windows and here is how I fixed it:

1. Uninstall nvm from windows(you can do that from Add and remove programs). This will remove also the node versions installed with the nvm previously so you do not need manually to uninstall all before uninstall the whole nvm.
2. Install the latest nvm from here https://github.com/coreybutler/nvm-windows/tags . 1.1.10 is the latest to this date.
3. nvm install 'your prefered version' then nvm use 'the installed version'
4. Whoala!

Fantastic step by step. THank you!

[maurymmarques]

I've updated my node version and it worked.

Linux/macOS:

1. Open the Terminal and check your current Node version:
   node -v
2. Install n package using the following command:
   npm install -g n
   This command will install a tool called "n" which you can use to update Node easily.
3. To update Node, run the following command in your terminal:
   n latest
   This command will install the latest version of Node on your system.
4. Now you can verify that your update is complete by rechecking your Node version:
   node -v

[coreybutler]

@maurymmarques - n is a tool for Linux/macOS, not for Windows.

[natesire]

If npm isn't working... then how can I use npm to fix itself. It's a circular problem. I cannot run any npm commands.

[natesire]

The easiest way to work around this is to either use Linux or the Ubuntu Subsystem on Windows to run your npm commands. And run with --verbose so you can see that it's the funding package libnpmfund that is tripping up over a path syntax error with the '.' on Windows.

[natesire]

It is happening with random npm packages. So that points to a problem with the npm code that calls out to these packages.

at Module._compile (node:internal/modules/cjs/loader:1159:14

[natesire]

I found the root cause. These paths inside these files that the loader is requiring need double quoted. They are regular expressions too.

Change
../workspaces/xxx

To
"../workspaces/xxx"

in each file and it will work on Windows. I don't know why this is only breaking on Windows.

[natesire]

#6601

[Tan-nn]

I faced issues with nvm 1.1.7, Solved this issue when updated to 1.1.12, but I can not uninstall nvm 1.1.7 only copy and replace file

[carlosananias]

A versão 1.1.10 do NVM tem todos esses problemas (mais o problema de elevação) corrigidos. Atualize o nvm e, em seguida, remova as versões do nó quebrado e reinstale-as.

Agora tudo funciona conforme o esperado.

this is excellent... works well for my team