Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check if CHANGELOG can be skipped in published package #33

Open
trivikr opened this issue Sep 23, 2021 · 1 comment
Open

Check if CHANGELOG can be skipped in published package #33

trivikr opened this issue Sep 23, 2021 · 1 comment

Comments

@trivikr
Copy link
Owner

trivikr commented Sep 23, 2021

Is your feature request related to a problem? Please describe.

The CHANGELOG is shipped in npm package, which occupies 76KB on disk for client-s3

$ yarn why @trivikr-test/client-s3
...
=> Found "@trivikr-test/[email protected]"
...

$ ls -l node_modules/@trivikr-test/client-s3/*.md
-rw-r--r--  1 trivikr  staff  76805 Sep 23 08:03 node_modules/@trivikr-test/client-s3/CHANGELOG.md
-rw-r--r--  1 trivikr  staff   5734 Sep 23 08:03 node_modules/@trivikr-test/client-s3/README.md

Describe the solution you'd like

The CHANGELOG is not present in list of "always included" in files property of package.json.
Check if CHANGELOG can be explicitly removed from published npm package, and what's the impact.

@trivikr
Copy link
Owner Author

trivikr commented Oct 6, 2021

Npm always publishes CHANGELOG and it's variants.
Blog post: https://blog.npmjs.org/post/165769683050/publishing-what-you-mean-to-publish.html#npm-publish

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant