I have to install the validator package for node.js
That's what I did
npm install validator
That's the output
npm http GET https://registry.npmjs.org/validator
npm http 304 https://registry.npmjs.org/validator
npm WARN package.json policyfile#0.0.4 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
Any idea what to do here?
Ignore those. They are benign warnings and don't pertain to you as a user of the validator module. The author of the validator module could fix them by correcting it's package.json file. Not sure why NPM prints these here as they are mostly a nuisance to npm users and they are really messages for package authors.
Related
I am trying to install Bootstrap using the npm install method. I have been on this for a while now and am wondering if I am doing something wrong? the npm install is still included on Bootstrap site as well as github and the npm page.
From what I understand using bower has been deprecated. Had serious issues using gulp. Any assistance or a link to an updated tutorial would be greatly appreciated.
Following errors occured while trying to install via terminal:
~/GitHub/GitSite $ npm install boostrap
npm WARN deprecated boostrap#2.0.0: Package no longer supported.
Contact support#npmjs.com for more info.
npm WARN gitsite#1.0.0 No repository field.
+ boostrap#2.0.0
updated 1 package in 1.902s
~/GitHub/GitSite $ npm install boostrap jquery popper.js --save
npm WARN deprecated boostrap#2.0.0: Package no longer supported.
Contact support#npmjs.com for more info.
npm WARN gitsite#1.0.0 No repository field.
+ boostrap#2.0.0
+ jquery#3.3.1
+ popper.js#1.14.3
updated 3 packages in 2.216s
In the download was included all the correct folders, however, in node_modules > boostrap there was a README file that said:
Deprecated Package
This package is no longer supported and has been deprecated. To avoid
malicious use, npm is hanging on to the package name.
Please contact support#npmjs.com if you have questions about this
package.
~/GitHub/GitSite $ npm install boostrap
You made a typo buddy, npm install boostrap instead of npm install bootstrap
Try with the correct package name and it will work!
Try this:
npm install --save bootstrap#4.1.0
Do you have bootstrap#2.0.0 listed in your package.json dependencies?
try npm i bootstrap#4.1.0
I have been able to install node modules locally in a project for quite some time. All of sudden ALL attempts at installation fail, with the same type of error:
Homers-MacBook-Pro:test homer$ npm install bootstrap#3
/Users/homer
└── bootstrap#3.3.7
npm WARN enoent ENOENT: no such file or directory, open '/Users/homer/package.json'
npm WARN homer No description
npm WARN homer No repository field.
npm WARN homer No README data
npm WARN homer No license field.
I'm not using a package.json file, just hoping to install some modules in a local node-modules directory. I don't understand why npm suddenly thinks it needs a package,json in my Home directory.
I'm on MacOS 10.12.4. There have been no upgrades in the system or in Node since the last successful npm install a couple of weeks ago.
This is just a warning, not errorwhich means you can ignore it. And your package has been successfully installed.
npm WARN homer No description // no description in package.json
npm WARN homer No repository field. // no repository setted in package.json
npm WARN homer No README data // no introcude md found
npm WARN homer No license field. // no lisence type setted in package.json
Above warn messages is all about details of package.json which were caused by package.json not found.
package.json is a config file which stores libraries that you installed by npm. So that you don't have to copy/manage these libraries manually and locally.
Next time for a new environment, you can simply reprocude the denpendencies by npm install, and npm will read your package.json and reinstall packages stored in it.
As commented by #peteb (thanks again), while install packages via npm install [packages], npm will try to check whether your newly installed package is listed in package.json . If the file doesn't exist, then this warn message will be shown.
how to use nodejs package in meteor app.
i tried to install module in app directory it is showing error
npm install skimlinksjs
npm WARN package.json node#0.0.0 No description
npm WARN package.json node#0.0.0 No repository field.
npm http GET https://registry.npmjs.org/skimlinksjs
npm http 304 https://registry.npmjs.org/skimlinksjs
npm WARN engine skimlinksjs#0.0.1: wanted: {"node":"~0.6.15"} (current: {"node":"v0.10.24","npm":"1.3.21"})
skimlinksjs#0.0.1 ../../node_modules/skimlinksjs
What is this error and how to use it in the app?
Don't do that, and remove the node_modules directory. Most node modules will not work like that due to Meteor's file wrapping and ordering. They just won't load properly.
To use a node module:
Grab npm package via mrt add npm command.
Add packages.json file with the list of necessary packages, for example:
{
"candle": "0.4.0",
"oauth": "0.9.11"
}
Afterwards, you can require the package with Meteor.require('packagename');.
I installed coffee-script as per directions.
$ npm install http://github.com/jashkenas/coffee-script/tarball/master
npm http GET http://github.com/jashkenas/coffee-script/tarball/master
npm http 200 http://github.com/jashkenas/coffee-script/tarball/master
npm http GET https://registry.npmjs.org/mkdirp
npm http 200 https://registry.npmjs.org/mkdirp
npm WARN package.json cookie-signature#1.0.0 No repository field.
npm WARN package.json fresh#0.1.0 No repository field.
npm WARN package.json methods#0.0.1 No repository field.
npm WARN package.json range-parser#0.0.4 No repository field.
npm WARN package.json send#0.1.0 No repository field.
npm WARN package.json ms#0.1.0 No repository field.
npm WARN package.json pause#0.0.1 No repository field.
npm WARN package.json bytes#0.2.0 No repository field.
npm WARN package.json formidable#1.0.11 No repository field.
npm WARN package.json css#1.0.8 No repository field.
npm WARN package.json uglify-js#2.2.5 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json walk#2.2.1 No repository field.
npm WARN package.json css-parse#1.0.4 No repository field.
npm WARN package.json css-stringify#1.0.5 No repository field.
coffee-script#1.6.3 node_modules/coffee-script
└── mkdirp#0.3.5
yet when i execute 'coffee' command i get
$ coffee
-bash: coffee: command not found
What am i doing wrong?
PS: i am doing this on Mac Terminal
EDIT: -
Same problem is occurs when i install nodemon the npm install takes place similar to above. But when i input a nodemon command on $ prompt it says -bash: nodemon: command not found
I installed coffeescript on my mac yeasterday as a matter of fact. Here is how I did it:
First of all, go install NodeJS.
Then go in Terminal and type the following: sudo npm install -g coffee-script
That's it - If you type in coffee in Terminal, it should start without a problem
Anything you want to run as a command (nodemon, coffee, node-inspector) must be installed with npm install -g the-package-name. If you use npm install it just puts it into your local node_modules directory and won't create the symlink for command line execution.
If you find that you need to use sudo, you might want to read this blog post: http://howtonode.org/introduction-to-npm:
what, no sudo?
I strongly encourage you not to do package management
with sudo! Packages can run arbitrary scripts, which makes sudoing a
package manager command as safe as a chainsaw haircut. Sure, it's fast
and definitely going to cut through any obstacles, but you might
actually want that obstacle to stay there.
I recommend doing this once instead:
sudo chown -R $USER /usr/local
Hi i am getting the error below while trying to install soap module using npm.
Below is the error
npm WARN node-expat#2.0.0 package.json: bugs['name'] should probably be bugs['url']
Any help how to proceed further will be much helpful
As already stated in the message from NPM, that's not a error. It's a warning, that tells you the package you're trying to install has wrong data in the bugs field, which is only one of the various fields available in the package.json file.
An related question: npm WARN package.json: No repository field