Add support for imported exports #100
Open
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
Adds support for
```
export * from 'module';
export { function } from 'module'
```
providedExports field appears to be around for all of Webpack 4. If prior webpacks are supported still, then will need a simple adapter layer.
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.
Adds support for
providedExportsfield appears to be around for all of Webpack 4. If prior webpacks are supported still, then will need a simple adapter layer.Approached this in additive fashion to reduce the risk of this PR. I do have a stash locally that replaces the custom traversal logic glad to include that in this PR if desired. Mostly deletes the custom parser hooks.
Fixes #15