C
Join ServerC#
help
npm version error
Wwiz11/28/2022
Hi guys,
An old project running core 3.1 is using 11.15.0 of npm, I have previously a installation of 18.12.0.
I have tried to change this with nvm to match the version of the build:
So it is failing when I am trying to build and saying that I am still using 18.12.0.
Best regards
An old project running core 3.1 is using 11.15.0 of npm, I have previously a installation of 18.12.0.
I have tried to change this with nvm to match the version of the build:
So it is failing when I am trying to build and saying that I am still using 18.12.0.
Best regards
Wwiz11/28/2022
Worth to mention is that I am new with npm/nvm, mostly been sitting on the integrations end further down.
Wwiz11/28/2022
so it could be something different I am missing.
AAntonC11/28/2022
Now using node v11.15.0 (npm v6.7.0)
don't you need 11.15.0 of npm
and not node?Wwiz11/28/2022
Yes, it might be the case. Trying now to figure out how to install npm 11.15.0
Wwiz11/28/2022
I tried to do:
$ npm install 11.15.0
but I got:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/11.15.0 - Not found
npm ERR! 404
npm ERR! 404 '11.15.0@latest' is not in the npm registry.
npm ERR! 404 Your package name is not valid, because
npm ERR! 404 1. name can only contain URL-friendly characters
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
$ npm install 11.15.0
but I got:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/11.15.0 - Not found
npm ERR! 404
npm ERR! 404 '11.15.0@latest' is not in the npm registry.
npm ERR! 404 Your package name is not valid, because
npm ERR! 404 1. name can only contain URL-friendly characters
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
Wwiz11/28/2022
Wwiz11/28/2022
But that is a variant of Node, not Npm
Wwiz11/28/2022
And yes, 6.7.0 seem to be my installed version of npm:
$ npm -v
6.7.0
$ npm -v
6.7.0
Wwiz11/28/2022

Wwiz11/28/2022
this is confusing tho.
Wwiz11/28/2022
it seem to be correct? Node v11.15.0 on npm v6.7.0
AAntonC11/28/2022
node is the server-side js runtime, npm is their package manager
Wwiz11/28/2022
yeah
AAntonC11/28/2022
they come together but they are two different things
Wwiz11/28/2022
Not sure what I have changed but the build can now build.
AAntonC11/28/2022
npm install npm 11.15.0
Wwiz11/28/2022
on
$ npm -v
6.7.0
$ npm -v
6.7.0
AAntonC11/28/2022
you're trying to install just the package named 11.15.0
Wwiz11/28/2022
I see
Wwiz11/28/2022
$ node -v
v11.15.0
v11.15.0
Wwiz11/28/2022
When I am now trying to do a
npm start
I am getting errors with
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "^6.6.0"
npm start
I am getting errors with
There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "^6.6.0"
Wwiz11/28/2022
I guess I do a npm i eslint@6.6.0
Wwiz11/28/2022
??
AAntonC11/28/2022
did you do npm install?
AAntonC11/28/2022
you need to do npm install to initialize the project
Wwiz11/28/2022
ok
Wwiz11/28/2022
Great
Wwiz11/28/2022
Now I have a instance of the build running locally
Wwiz11/28/2022
Thank you Anton :)
Wwiz11/28/2022
What is best pracc to do with this post, Close or Unfollow?
Wwiz11/28/2022
Maybe somebody else has similar issue in future
AAntonC11/28/2022
i think it stays reachable through search even if you close it
Wwiz11/28/2022
Yes, just closed and could still find through search.
Thanks again!
Thanks again!
AAntonC11/28/2022
np