Fix file extensions in package.json #156
Merged
Conversation
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
After recent renaming of dist/* files, some file names were not updated
in package.json. This causes issues, specifically in node.js when you do
`import { JSONPath } from 'jsonpath-plus'`, you'll get an error because
it tries to access a non-existent file based on package.json `main` field.
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.
PR description
After recent renaming of dist/* files, some file names were not updated
in package.json. This causes issues, specifically in node.js when you do
import { JSONPath } from 'jsonpath-plus', you'll get an error becauseit tries to access a non-existent file based on package.json
mainfield.Checklist
npm test, ensuring linting passes