In v2, not v1, package.json uses deprecated form of license {}
See original GitHub issueReference: https://docs.npmjs.com/cli/v7/configuring-npm/package-json
Some old packages used license objects or a “licenses” property … Those styles are now deprecated.
In v2, package.json, you have:
"license": { "type": "MIT", "url": "http://github.com/kriskowal/q/raw/master/LICENSE" },
Better to stick with what you have in v1:
"license": "MIT",
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
package.json - npm Docs
json are the name and version fields as they will be required. The name and version together form an identifier that is assumed...
Read more >How to have yarn not issue a warning for the license field?
Just make sure you are in the directory that contains the package.json file, then just yarn or npm install then serve it as...
Read more >Can not install appcenter cli · Issue #1934 - GitHub
I tried to install via yarn. There is an error: $yarn global add appcenter-cli yarn global v1.22.18 warning package.json: No license field error...
Read more >Specifics of npm's package.json handling - manpages.ubuntu!
Some old packages used license objects or a "licenses" property containing an array of license objects: // Not valid metadata { "license" :...
Read more >Go Modules Reference - The Go Programming Language
Introduction. Modules are how Go manages dependencies. This document is a detailed reference manual for Go's module system. For an introduction to creating ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Q v2, never released officially, forever in beta, is downloaded 500K times every week as a dependency and no one noticed. This is pretty funny.
500 thousand installations every week - not a single bug report ^^ (except this one about the license). We’re living in amazing times.
Uh, oh. I suppose if it’s working for them, it’s working, even though it never switched to being
latest
.A PR for the license block change would be welcome. It would also be good to put a
publishConfig
block intopackage.json
to make sure thev2
train doesn’t get promoted tolatest
just in the process of updating thepackage.json
.