Remove Changelog from npm package
See original GitHub issueWhile looking for some larger files in node_modules
, I’d noticed that the CHANGELOG is getting bundled:
268K ./node_modules/eslint/CHANGELOG.md
This appears to be happening on 3.18.0
Thanks for your time in reading!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Changelog - npm Docs
The purpose of this release is to drop support for old node versions and to remove support for require('npm') . There are no...
Read more >Changelog - npm Docs
Documentation for the npm registry, website, and command-line interface.
Read more >npm-unpublish
This removes a package version from the registry, deleting its entry and removing the tarball. The npm registry will return an error if...
Read more >Changelog - npm Docs
Documentation for the npm registry, website, and command-line interface.
Read more >Changelog - npm Docs
e4455409f #281 delete ps1 files on package removal (@NoDocCat); cd14d4701 #279 update supported node list to remove v6.0, v6.1, v9.0 - v9.2 (@ljharb) ......
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
@baweaver As noted in @not-an-aardvark’s link, npm will always include the changelog even if we try to tell npm to ignore it. Thus, the only way we could get it out of the package is to remove it from GitHub, which means nobody could read it.
I suppose theoretically, we could remove older release notes from CHANGELOG and put it in some sort of archive that doesn’t get included in the package, but why should we do that really? Just seems like an extra maintenance burden for not a lot of gain.
I think the changelog is an important part of our documentation, so it makes sense to include it in the package. This is also why npm always includes changelogs in the package.