Closed gvlekke closed 3 years ago
I faced a similar issue when I upgraded to version 10 of Angular, I had to roll back to version 3.0.1 of the library, it does throw a warning about bailing out when optimising, but so far it seems to work. I have submitted a PR (build-cleanup) which converted this library over to use the ng add schema and I'm waiting for @crisbeto to take it over the finishing line. This should then remove this error, I think this error is partly due the the build process and possibly commonJS issues but I'm not entirely sure about that.
These errors usually mean that ngcc
hasn't been run over the project's dependencies.
@crisbeto good temporary fix but would be great if this library is supporting that.
Hope @DuncanFaulkner pr fixes it soon, altho I don't see his PR
His changes are in the build-cleanup
branch, but there's still some more work to be done.
ah ok its still in the branch :) good luck and if you need some help testing give me a message.
@crisbeto if there is anything I can help with to get this over the line?
I'm really sorry that I didn't get to it, I had some time off the past couple of weeks but other things got in the way. What's holding it back is that I need to go through everything (production build, demo, GH pages deployment) and make sure that it works similarly to the current setup.
No problem, we all need time to recharge the batteries, if it helps the process, the production code hasn't changed just the location of it (I don't recall making any changes to the code, but of course it still needs validating).
The new part was the creation of the ng add schema which will need full testing, and there may very well be bugs in that part.
The demo is just a regular angular app pulling in the component from library, I wasn't sure (at the time) how you were deploying it to GH pages and there will probably be some work to do here.
If there is anything I can help with please let me know.
Version 5.0.1 has been release which includes the new packaging changes.
@crisbeto this is excellent news
Upgraded to Angular 9 I get this errors when I upgraded the angular-svg-round-progressbar to version 4.0.0
Is angular-svg-round-progressbar compatible with angular 9? and how can I solve this then?