Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, this morning I was checking Renovate PRs and noticed that 16.4.6 mistakenly included a bunch of extra files, as I happened to click the package diff from Renovate to skim the readme change that was called out. Needless to say, the files in
.tap
folder stood out like as sore thumb. It seems to be for test results, code coverage and debug data from the last local run and that alone causes 16.4.6 to be 456% the size of 16.4.5, jumping up from 79.1 kB to 361 kB according to NPM. I'm assuming this was caused in 949b0eb as that commit was updating thetap
package and added.tap
to.gitignore
.One could make the argument that it does not matter due to being a small absolute increase in size, but one could also say that with 40 million downloads weekly, the extra 24 kB in tarball size is an extra 915 GB of bandwidth per week with piles of wasted space when bundled into production copies of things. Myself? I just like clean diffs to see what changed.