-
Notifications
You must be signed in to change notification settings - Fork 122
-
Notifications
You must be signed in to change notification settings - Fork 122
esModule option is ignored #775
Comments
Yes it should work with the builder. What does your configuration look like? |
I made a minimal example here : https://github.com/nicolashenry/esmodule-systemjs-builder "index.html" display "ok" in console Maybe I'm doing something wrong here. |
Unless something has changed, module format meta config should look like this. meta: {
'@angular/core/*': {
format: 'esm'
}
} |
I don't understand, I use the "esModule" option and not the "format" option. |
My objective is to use a legacy module "bundles/core.umd.js" which use "named imports", "bundles/core.umd.js" is not an ecmascript module. |
Is the esModule flag working? React doesn't export __esModule right now and I would like to do |
@nicolashenry the bundled version still needs the configuration file to set the |
Is there somewhere else other than https://github.com/nicolashenry/esmodule-systemjs-builder/blob/master/systemjs.config.js#L26 where the meta should be set? |
@guybedford buildStatic is supposed to "To make a bundle that is independent of the SystemJS loader entirely" so I don't understand why and how I could add the |
Ahh, SFX support for the This can be added by enabling an System.register([..], function (require, exports, module) {
// this line is added by the flag:
Object.defineProperty(exports, '__esModule', { value: true });
}); If anyone is interested in working on this please let me know, otherwise I will try get to it when I can. |
I've included the updates here in for the coming release 802ab43. |
Released in 0.16.5. |
The systemjs esModule option (https://github.com/systemjs/systemjs/blob/master/docs/config-api.md) seems to be ignored with systemjs-builder, is it supposed to only work with systemjs alone ?
The text was updated successfully, but these errors were encountered: