angular-froala-wysiwyg
angular-froala-wysiwyg copied to clipboard
Angular 8 w/Ivy build: ERROR in Failed to find exported name of node (function FroalaEditorModule() {})
I am trying to compile an Angular 8 project with Ivy enabled that uses angular-froala-wysiwyg. Here is the error that I get:
ERROR in Failed to find exported name of node (function FroalaEditorModule() {
}) in '/Users/orunov/dev/mango/callisto/node_modules/angular-froala-wysiwyg/editor/editor.module.js'.
ng --version:
angular-cli: 1.0.0-beta.28.3 node: 11.15.0 os: darwin x64 @angular/animations: 8.0.0 @angular/cdk: 8.0.0 @angular/common: 8.0.0 @angular/compiler: 8.0.0 @angular/core: 8.0.0 @angular/flex-layout: 7.0.0-beta.23 @angular/forms: 8.0.0 @angular/material: 8.0.0 @angular/material-moment-adapter: 7.2.2 @angular/platform-browser: 8.0.0 @angular/platform-browser-dynamic: 8.0.0 @angular/router: 8.0.0 @angular/cli: 8.0.1 @angular/compiler-cli: 8.1.0-next.1 @angular/language-service: 8.0.0
it looks like you have a very old CLI @runov001. Have you tried upgrading it first and what are you trying to achieve?
I have the same problem with all new versions of angular (and cli). Only happens with the new Ivy renderer.
the same here: all angular versions in ivy rendering mode - would be nice if we get this fixed
Angular recommends ng-packagr to make angular library. But it seems angular-froala-wysiwyg use ngm-cli
to build.
Angular team consider ng-packagr based library to compatible with ivy compiler.
I can try to fix it with using ng-packagr.
I am getting the error without using the Ivy renderer. I'm using angular version 8.2.3.
@mgm87 Angular 8.2.3 supports differential loading in cli build process (Differential loading requires ES5, ES2015, UMD build artifacts). But angular-froala-wysiwyg only have umd build artifacts now.
https://docs.google.com/document/d/1Dije0AsJ0PxL3NaeNPxpYDeapj30b_QC0xfeIvIIzgg/preview# As this official document said, angular-froala-wysiwyg should use 'Angular Package Format' to build library.
Hi. This is a significant issue for us too. We have turned on Ivy by updating Angular and now builds are failing completely. I think this is about to become urgent for more users.
Please fix it!
These failures should now be fixed. This seems like the pending one https://github.com/froala/angular-froala-wysiwyg/issues/347.
Please fix it!
Please fix it quickly, we have a paid subscription and getting same error.
Please fix it quickly, I getting this error while I want to use lvy.
ERROR in Failed to find the exported name of the node (class BsDatepickerDayDecoratorComponent { })
The same error with FroalaEditorModule and ivy. Froala, fix it pls.
Please fix, same error using Ivy
Please, any answer the team?
Can someone at Froala please fix this as a critical priority, I need Ivy enabled in my project and this is the only dependency preventing me from being able to enable Ivy.
It would be great if we could get a status from the Froala team here, we're also stuck with this build error.
We are also stuck on the same issue
@StickNitro , did you experience any problems with the version by @leo6104 from https://github.com/froala/angular-froala-wysiwyg/pull/329 ?
@earshinov Yes, that does work fine with Ivy
For anyone interested in why there is still no reply from Froala team, I've recently contacted them on the topic of license renewal and asked why they don't reply to issues reported to GitHub. Here is the answer (hopefully it is legal to share it):
As far as support on the Github channel is concerned, in most cases, it is community support. Therefore, I kindly recommend that you contact us via Support Channel in the future.
I am leaving it up to you to decide whether you want to have anything to do with this project. But perhaps it can help you make the right decision if you look through the first couple of pages of https://github.com/froala/wysiwyg-editor/issues paying attention to the number of replies.
By the way, angular-froala-wysiwyg 3.2.2 builds and works fine under Ivy (but seems to no longer build without Ivy).
See also https://github.com/angular/ngcc-validation/issues/57#issuecomment-657745488