-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error with AoT compilation #8
Comments
https://medium.com/@isaacplmann/getting-your-angular-2-library-ready-for-aot-90d1347bcad Something along those lines needs to happen I suppose? |
That sounds about right I think, at least the error matches. Just in case someone wants a quick temporary fix, I got this to work with AoT with a workaround by copying the components to my own project instead of using the module. |
I was giving it a shot earlier today but I couldn't get Maybe I'll try again once I get some free time. Until then, this library is sort of unusable in conjunction with Angular CLI. Any workarounds? |
Copy all four files from /src/angular2-nvd3 into your own project and replace the "ngOnChanges()" methods with "ngOnChanges(changes?)". Then you can just import the module into your app.module.ts and the component where you want to use the selector, works with AoT.
Of course you also still need to include the separately downloadable nv.d3.css in your project for the styles to be right. |
@ekuusi I had some success in getting this package ready for AOT by changing the This requires that you install |
I close this issue, since I accept Ready for AOT #10 |
I'm hitting an error when doing AoT compilation with angular2-nvd3 in my project:
The module works perfectly with just in time compilation and is a great improvement to ng2-nvd3 which I've used so far, but I really need the AoT compilation to work to use this in production. Can you replicate this issue? Any ideas how to fix this?
ng2-nvd3 has worked just fine with AoT compilation, but I would love to get rid of the bugs it has that angular2-nvd3 fixes.
The text was updated successfully, but these errors were encountered: