add manual support for ESM in NodeJS #55
Merged
Conversation
This file contains 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
…for ESM and NodeJS support
|
Awesome, thanks for the PR 👍 |
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.
resolves #48
modulefield in package.json to point to a non empty file (dist/websocialshare/websocialshare.esm.js)Question:
Although these fields are all community driven / not NodeJS "speced", wondering what do about them in package.json, since they were also all pointing at the same empty file?
"es2015""es2017""jsnext:main"Ultimately it's up to tooling authors to support them, but from my experience, I think I've only really seen
modulecatch on so far, otherwise I think export maps are the way to go (and so hopefully Stencil will support this too 🤞 )