Whitelist files to include in npm package#199
Conversation
|
I started including everything after substack nuked his github as a hedge against myself doing the same thing, but I don't think I care that much anymore. |
|
Will review with the next major release that we are sitting on. |
ah, I see, you include everything in the package so that if the repo is removed, people can continue working of the package contents. I understand the intent, commendable. My reasoning for keeping packages as small as possible is both for bandwidth/storage preservation and, regretfully, related to attack vectors in supply chain attacks. Bad actors including malware in test files that are unexpectly still run is something that requires attention unfortunately. Smaller packages lead to a smaller effort required to verify code and less places where things can be hidden. It's a shame that these goals are mutually exclusive. I wish smaller dependency trees and vendoring were more commonplace in the JS ecosystem. Fighting against supply chain attacks in the JavaScript world takes substantially more effort compared to Go for example. |
|
Yeah maybe github or npm-v2 can fix this someday. I’ll review and make sure this works and include in the next major before end of year. |
npm-run-all2@8.0.4currently contains the following files:Quite a few of these files are not necessary. This PR excplicitly whitelists all the files that will be included in the npm package.
README.mdandLICENSEare included by default. Test usingnpm pack.Output of `npm pack` after this change