-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load transpiler to transpile .../d3-ng2-service/index.js #14
Comments
I got the same error with @sdeuvarow |
The current version of the service exposes two entry points: So in either case the module loader has to be able to understand ES2015 module structure (e.g. Webpack2 now has native support for loading with ES2015 module structure. This is what angular-cli uses under the hood.) As your above code references |
In the case of systemJS there is also the SystemJS Babel plugin. I used SystemJs with Angular 1.x, but have since moved away from it alongside the move angular-cli made. I contemplated earlier to provide a UMD entry point, but ran into some issues with the combined Rollup of the d3 modules and the bundle/service parts of this library. |
Finally I decided to update my app to use webpack of angular-cli. So, as u told, I don't have the issue using webpack. Thanks! |
That's the other way to go... 😄 |
When using systemjs to load the app, I'm getting the following issue:
This is the content of the d3-ng2-service/index.js HTTP response:
In the live-example there is no loader, so it doesn't show how to configure a loader to use the d3-ng2-service. Do you have an example of that? I'd like to see the lib working with a loader to check what am I doing wrong.
This is my systemjs config:
thanks!
The text was updated successfully, but these errors were encountered: