-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 ERR! Unexpected token '.' #4303
Comments
+1 |
literally unusable |
same here, |
Seems to be a change with Node 17.4.0 causing this break, works fine on 17.3.1 otherwise. I personally blame Gabe |
hi @syedbilal07 I'll close this issue in favor of keeping the conversation over at #4234, thanks! |
Ok sure. |
+1 |
1 similar comment
+1 |
With npm 8.5.0 and node 16.14.2 on windows I have the same issue tryign to clone a repo |
for me every |
I have also the same problem |
i have also the same problem |
I also have same problem |
I am also facing same problem in npm version 8.5.5 and nvm -v Running version 1.1.7. |
Just a heads up, this has been fixed in nvm 1.1.10. |
npm ERR! Unexpected token '.' $ npm -v $ nvm version $ node -v $ npm i |
Why has this been closed?
I'm on windows 11. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have updated to the latest npm v8.3.2 and it is showing me an error while using the command "npm install". What is the solution?
Please see my previous issue: #4234 (same was present in v8.3.1). I don't want to switch my nodejs to LTS release
Expected Behavior
It should install the required package
Steps To Reproduce
I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment.
Environment
; 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.
The text was updated successfully, but these errors were encountered: