Skip emitting sourcemaps when publishing to npm #569
Merged
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.
I considered two ways to do this:
files
array to:["lib/**/*.js", "lib/**/*.d.ts"]
.I went with the second choice to avoid having to update the
files
array if there was every anything else inlib/
that needed to be included in the future. This also seems to more directly target the issue: don't publish the sourcemaps.Also updated the package version in the
package-lock.json
which was surprising that it was not in-sync with thepackage.json
value. 🤷♂️Not addressed in this PR: The module structure has not changed, so
fp-ts/lib/Foo
is still the way to import sub-modules.The output of
npm pack --dry-run
: