Repository navigation
chore: remove files field from package.json - #78
Merged
Merged
Conversation
Tony133
force-pushed
the
chore/remove-files-field
branch
from
October 20, 2026 21:27
6ca31e3 to
11f0785
Compare
metcoder95
approved these changes
Oct 21, 2026
ilteoood
approved these changes
Oct 21, 2026
|
What's the benefit of including the pipeline config, benchmarks, tests, coverage config, eslint config and .gitattributes as part of the npm package? |
Member
Being able to recreate the package elsewhere if the repo gets removed from GitHub |
|
Okay, though its probably easier to just have a clone of the repo somewhere. (I was surprised when I saw the tiny changelog but then a huge actual diff when updating.) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposal:
This PR removes the
filesfield frompackage.json, aligning this repository with the other repositories in the org.Notes: