I downloaded my IBM bluemix nodeJS app, and trying to install all the dependencies of the project. For some reason, ibmconfig is throwing an exception. However, the URL works fine from the browser. Looks like a npm registry exception.This module is a dependency for ibmsecurity.
Here is the package.json dependency content:
"dependencies": {
"express": "4.*",
"body-parser": "*",
"ibmsecurity": "*",
"twilio": "*",
"ibmbluemix":"*",
"ibmdata":"*"
}
Here is the 404 exception:
npm WARN package.json # license should be a valid SPDX license expression
npm ERR! Darwin 14.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "ibmconfig"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/ibmconfig
npm ERR! 404
npm ERR! 404 'ibmconfig' 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! Please include the following file with any support request:
Thanks for your help
Although that registry file still exists, if you go to the ibmconfig package page you'll see that it does not exist. I suspect that the package has been unpublished. You may have to contact the original maintainer to find out what happened.
Review of the ibmsecurity npm package's Git log for the package.json file, it looks like the dependency on an ibmconfig package was removed on 2015-07-29. You may need to update the package with npm update ibmsecurity
You will only see this error if you use the beta version of ibmsecurity (0.3.x). Change your dependency to use "latest" or "1.0.x" and you will not have this problem.
Related
Node version: 10.16.0
Sails version (sails): 1.2.3
When I try to create new project using sails cli it just gives me below error and I can not do anything.
And I see there is a package https://www.npmjs.com/package/socket.io-redis but it doesn't have #sailshq prefix in the package name.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/#sailshq%2fsocket.io-redis - Not Found
npm ERR! 404
npm ERR! 404 '#sailshq/socket.io-redis#latest' 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.
Can someone help me please?
Thanks
Maybe you should use npm i #sailshq/socket.io-redis?
https://www.npmjs.com/package/#sailshq/socket.io-redis
I am trying to install protractor but receiving following error.
command:
npm install -g protractor
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code E404
npm ERR! 404 no such package available : #types/jasmine
npm ERR! 404
npm ERR! 404 '#types/jasmine' 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 It was specified as a dependency of 'protractor'
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! Please include the following file with any support request:
npm ERR! F:\temp\chrome downloads\npm-debug.log
I came across this issue today and my problem was that I had set a custom registry within the npm config file. Have you ever used "npm set registry"?
If so, you can manually tell npm where to look for the '#types' registry with the following command:
npm config set #types:registry https://registry.npmjs.org/
The problem is coming from the fact that you're using a private registry that has not yet added support for #organization packages.
In my case, I was using Sonatype Nexus and my version didn't have support for those types of packages. #Willie Valdez's suggestion is probably the best solution for you, right now.
Also, check if you have a .npmrc file in your home directory or in your project directory. The registry might be there. If that's the case, just rename the file to npmrc_bak or something else until you install the package and then revert back to its original name.
You can also include a .npmrc file in your current project with the below details:
#angular:registry=https://registry.npmjs.org
#types:registry=https://registry.npmjs.org
#ngtools:registry=https://registry.npmjs.org
#angular-cli:registry=https://registry.npmjs.org
its handy and resuable across new projects.
I successfully managed to get a private npm server up and running, which resides inside a Ubuntu VM on my Windows 10 machine.
I replicated the npm repository using https://skimdb.npmjs.com/registry as a source for CouchDB and can query packages such as jquery from my Windows 10 machine just fine.
PS D:\Sources\NodeJS\test> npm view jquery
{ name: 'jquery',
description: 'JavaScript library for DOM operations',
'dist-tags': { beta: '3.0.0-rc1', latest: '2.2.4' },
...
gitHead: 'c0185ab7c75aab88762c5aae780b9d83b80eda72',
dist:
{ shasum: '2c89d6889b5eac522a7eea32c14521559c6cbf02',
tarball: 'http://registry.npmjs.org/jquery/-/jquery-2.2.4.tgz' },
directories: {} }
However, all of the #angular/* packages appear to be missing. If I point npm to skimdb directly I get the exact same result, so it can't be a problem with replication.
PS D:\Sources\NodeJS\test> npm view #angular/common
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "view" "#angular/common"
npm ERR! node v5.9.1
npm ERR! npm v3.7.3
npm ERR! code E404
npm ERR! 404 Not Found: #angular/common
npm ERR! 404
npm ERR! 404 '#angular/common' 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! Please include the following file with any support request:
npm ERR! D:\Sources\NodeJS\test\npm-debug.log
Is this the proper registry to start with?
Ok, this appears to boil down to scoped packages where #angular is some kind of namespace.
I solved this problem by pointing to the official repository for packages from the #angular scope, i.e. my .npmrc now looks as follows:
registry=http://<couchdb server ip>:5984/registry/_design/app/_rewrite
#angular:registry=https://registry.npmjs.org/
I am setting up an Ember application on a new laptop. I installed node, npm through brew and I also have the Ember CLI. Within the Ember CLI app, I'm trying to do an npm install but when I do, I get this error in the terminal:
npm WARN package.json npm#1.4.21 Non-dependency in bundleDependencies: inherits
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.33
npm ERR! npm v2.1.11
npm ERR! code E404
npm ERR! 404 Not Found: expresss
npm ERR! 404
npm ERR! 404 'expresss' 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 It was specified as a dependency of 'ember-cli'
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! Please include the following file with any support request:
npm ERR! /Users/Nagarjun/Code/sumo-list/web-client/npm-debug.log
I can't run my projects until this is resolved. What am I missing? I even Googled but couldn't find anything for expresss.
My guess is 'expresss' (with an extra s) is a package on npm that was pulled. The dependency was in fact listed in the package.json file for ember-cli but I don't think anyone ever noticed it until later versions.
Proof: https://github.com/stefanpenner/ember-cli/blob/ec8a6ab898599746bddbb8f72f7633c29f0ee95b/package.json#L58
I was able to resolve this issue by uninstalling node and npm completely using brew. Then, installing node.js using the package from nodejs.org. Now, my npm version is 1.4.28. Looks like the issue was caused by the newer npm 2.1.10. Not sure why brew automatically picks up the new npm.
Look in your package.json dependencies section. Looks like a typo.
I faced the same issue but it got fixed by running sudo npm install -g ember-cli
I have an express project that accesses some common node code that I keep in a private repository in github. I have a line like the following in my package.json file
git+ssh://git#github.com:MYGITHUBACCT/MYPROJECT.git#master
When I run npm install, everything works correctly and it pulls my common code from the private repo and places it in my node_modules directory. However, when I run npm update, it fails on my private repo and displays the following:
npm ERR! 404 'MYPROJECT' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.
npm ERR! System Darwin 12.2.0
npm ERR! command "node" "/usr/local/bin/npm" "update"
npm ERR! cwd /Users/ginnyd/dev/gg-web
npm ERR! node -v v0.8.16
npm ERR! npm -v 1.1.69
npm ERR! code E404
Is there anything special I need to do in the package.json so that I can run the update and have it pull from GitHub?
Thanks
Ginny
Apparently, this is still an open issue with npm.
Meanwhile, to update git dependencies, you have to remove them first and then doing an npm install.
rm -rf node_modules/MYPROJECT
npm install
This have fixed in npm, please upgrade to npm >= 1.3.10
Sample usage
"dependencies": {
"thing": "git://github.com/myGitHubRepo/repo.js.git#56477cb",
}
Some day later
"dependencies": {
"thing": "git://github.com/myGitHubRepo/repo.js.git#67f90b5",
}
Then npm install again and you will get new ref!
If your "myGitHubRepo/repo.js" is a private package you should set "private": true there to ensure it doesn't get accidentally published to npm registry