Skip to content

Conversation

kpdecker
Copy link

Expands on/supersedes #100. Removing the parser logic simplifies the webpack API integration and number of points that break as a result of webpack 5 changes.

Note that karma-webpack would not play nicely when I installed webpack 5, so while this appears to compile correctly, it has not been tested at runtime with Webpack 5.

Possible fix for #77

kpdecker added 3 commits June 20, 2020 22:45
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.
@Deevian
Copy link

Deevian commented Oct 14, 2020

Any possibility of moving this forward?

@transcranial transcranial mentioned this pull request Nov 4, 2020
throw new Error('Attempted to load a worker implemented in CommonJS');
}

let exports = entries[0].entryModule.buildMeta.providedExports;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that as per webpack/webpack#8576 (landed on Webpack 5.0), buildMeta.providedExports is no longer there

To retrieve the provided exports like in webpack 4, we would need to call compilation.moduleGraph.getProvidedExports, i.e. let providedExports = compilation.moduleGraph.getProvidedExports(entries[0].entryModule);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants