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.
Whitelist published files with a
package.json
files
field.It's much more robust to whitelist what gets published, instead of attempting to remember to blacklist via
.npmignore
file which is now deleted.This change prevents 7 unnecessary files from being published (you can verify what gets published by running
npm pack
):Prevent dev tool config from being published in
package.json
. It's best practice to keep dev tool config out of thepackage.json
to reduce the published size of the package, in turn reducing the installed size of the package in user’snode_modules
.Prevent Husky config from being published in
package.json
.Prevent Jest config from being published in
package.json
.The Jest config is in a
.js
file as it doesn't automatically respect a.jestrc.json
file without having to use a--config
CLI argument, but at least the Jest config can now be type checked.Also, a forward slash in a regex in the Jest config is now correctly escaped.
There is still a
package.json
workspaces
field that looks sketchy, but I figured messing around with Yarn and stuff might be too contentious for this PR.