I am trying to install ArcGIS JS API 4.7 with npm (for a Vue.JS application), and when running
npm install arcgis-js-api
I am getting a NPM error:
npm ERR! code E404
npm ERR! 404 Not Found: #dojo/i18n#~0.6.0
I am using the latest version of Node (v10), but I also tried it with v9 and v6.
Has anyone faced it in the past?
Is it possible you are using a different NPM mirror? Maybe for private packages?
Does the answer provided in this SO answer help you?
Related
I am currently using Node.js v13.6.0 in Windows 8. When I am trying to install the NPM package, it's showing this:
npm i npm#6.4.1
npm does not support Node.js v13.6.0
You should probably upgrade to a newer version of node as we
can't make any promises that npm will work with this version.
You can find the latest version at https://nodejs.org/
npm ERR! code ERR_REQUIRE_ESM
npm ERR! Must use import to load ES Module: C:\Users\microshine\AppData\Roaming\npm\node_modules\npm\node_modules\just-diff\index.mjs
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\microshine\AppData\Local\npm-cache\_logs\2022-04-28T09_17_19_815Z-debug-0.log
My system does not support other versions of Node.js so I have to bear with it. Are there any other alternatives to install NPM with this version of Node?
This same issue happened to me. Then I installed npm#6.12.1, & it works for me so npm install -g npm should fix this issue.
If the problem still happens then try to upgrade to Windows 10 with node v16. it will surely help you.
Trying to install and utilize the https://developer.sonos.com/tools/developer-tools/sonos-simulator/
When following the install instructions and trying to install the node package via the npm install command within the directory it fails with a 404 error trying to find node-ssdp as seen from the snippet below:
P:\sonosDevel\sonos-simulator-0.4.34>npm install
npm notice
npm notice New minor version of npm available! 7.5.1 -> 7.6.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.6.3
npm notice Run npm install -g npm#7.6.3 to update!
npm notice
npm ERR! code E404
npm ERR! 404 Not Found - GET https://github.com/sonos/node-ssdp/archive/master.tar.gz
npm ERR! 404
npm ERR! 404 'node-ssdp#https://github.com/sonos/node-ssdp/archive/master.tar.gz' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
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 ERR! A complete log of this run can be found in:
npm ERR! C:\Users\duart\AppData\Local\npm-cache\_logs\2021-03-18T21_59_44_515Z-debug.log
I am doubtful there is much to do other than hope the sonos developers reupload the package and potentially update the Sonos Simulator but I may as well throw it on here to see if anyone has a solution to have get the Simulator running or perhaps some other solution to simulate a Sonos Device on the network without actually owning a Sonos device.
I was having a play around with this today, and managed to get it working.
I installed an old (4.x) version of node as this is what the documentation said it worked with (I honestly didn't try anything newer as I couldn't get the simulator to do what I wanted so uninstalled it after).
The main issue was with node-ssdp, as the included package file with the simulator was trying to get it from a repo that no longer exists. After some trial and error, I found that if you edit the package file to specify node-ssdp 2.7.0 (which is the version that was released when the simulator was), the npm install should go through ok. (If you install a newer version the simulator crashes a few seconds after you run it).
Hopefully this helps!
im a new beginner in html/css development with windows 10. I'm trying to use Saas for my website project but when I am trying to install node-sass, I get the following errors:
PS C:\wamp64\www\flexbox> npm install node-saas --save-dev
npm ERR! code E404
npm ERR! 404 Not Found: node-saas#latest
npm version is : 6.3.0
node version is : 8.11.3
I've already try this: Unable to install node-sass in my project but it doesn't work.
I'v try to open cmd as administrator, and try executing the same commands. Same problem again...
Can you please help me to find a solution ? Thanks !
You're installing node-saas. You meant to install node-sass, double s and a single a.
The problem I face is when I will install one of the packages NPM is always show
[............] /roolbackFailedOptional: verb npm-session ....
and the final show error like :
npm ERR! code e503
npm ERR! 503 Service Unavailable:
npm ERR! A complete log of this run can be found in:
npm ERR! C:Users\.......\AppData\Roaming\npm-cache\_logs\2018-08-08t08_09_25_773Z-debug.log
I have already found a solution from here. But it didn't worked.
The configuration NodeJS in my system :
and i use version for
NodeJS : 10.8.0
npm : 6.2.3
Please help me for fixed my problem...
not sure if it will fix your issue but i used
npm install --proxy proxy_address:port install package_name --save
when i had troubles with proxy, if this works, then you might have configured npm settings not the way you need to.
How can I update npm on OpenShift?
I'm having problems while deploying because npm started using ^1.2.3 version notations and it's not compatible with the current npm in my application:
remote: npm ERR! Error: No compatible version found: through#'^2.3.4'
remote: npm ERR! Valid install targets:
remote: npm ERR! ["0.0.1","0.0.2","0.0.3","0.0.4","0.1.0","0.1.1","0.1.2","0.1.3","0.1.4","1.0.0","1.1.0","1.1.1","1.1.2","2.0.0","2.1.0","2.2.0","2.2.1","2.2.2","2.2.4","2.2.5","2.2.6","2.2.7","2.3.1","2.3.2","2.3.3","2.3.4"]
Is there a way of fixing this, or I'll have to go back to outdated packages?
OpenShift does not provide root access to developers, but you can still select a custom version of npm by running your own nodejs binary in user space.
Developers can also package up their own custom nodejs cartridge, allowing teams to define and standardize their dependencies in a reusable way.
Here is an answer that helps you run a custom version of Nodejs on OpenShift
You can also try working with user-defined npm globals on OpenShift