angular
angular copied to clipboard
formio
Ivy
@travist I debugged the issue with Ivy today.
The auth, manager, grid, and resource modules are packed individually but contain references for each other, eg. manager imports auth. Ivy detects the modules as standalone packages and tries to manage async, but it reaches auth through manager as well, then throws an error since there is a lock file indicates it already processing it.
The solution would be re-structuring the lib to having only 1 entry point for each module for Ivy.
This item has been resourced. We will let you know once this has been resolved.
@merobal, thanks for reaching out. This item is on one of our developers list. We will let you know once this issue has been resolved.
Hello @chaixdev, This item is still on our developer's list. We will let you know once this issue has been resolved.
This maybe fixed with our latest upgrade @ @formio/angular repo. Have you tried that version @arjel?
@travist I tried on v4.11.0 and still had problems. I can try to update/reinstall and see if it's ok. Thank you!
Hey guys. Just found this issue. Just reporting that it is a major showstopper for us and a decision-maker or breaker when considering this library.
(Just mentioning because if I was maintaining then I'd like to know why people are using/non using my library)
Hey, Just tried to upgrade to Angular 12, and we're now forced to use Ivy.... How far is the implementation of Ivy support @travist ?
When building our project we receive errors like:
Error: Tried to write C:/**/node_modules/angular-formio/formio.config.d.ts.__ivy_ngcc_bak with an ngcc back up file but it already exists so not writing, nor backing up, C:/**/node_modules/angular-formio/formio.config.d.ts.
This error may be caused by one of the following:
* two or more entry-points overlap and ngcc has been asked to process some files more than once.
In this case, you should check other entry-points in this package
and set up a config to ignore any that you are not using.
* a previous run of ngcc was killed in the middle of processing, in a way that cannot be recovered.
In this case, you should try cleaning the node_modules directory and any dist directories that contain local libraries. Then try again.
Though the application builds and is able to run. Besides these errors we are experiencing problems with emitting updated data through the FormioBaseComponent.refresh event.
@JonasDev99 No. Are you receiving the above errors or just asking generally?
