Angular-tree-component: Angular new Ivy render engine compatibility

[matte00]

Hi mate,

if i enable ivy engine i get this error when try to compile.

ERROR in There is no typings path for TreeNodeWrapperComponent in C:/Users/.../node_modules/angular-tree-component/dist/components/tree-node-wrapper.component.d.ts.
We need to add an export for this class to a .d.ts typings file because Angular compiler needs to be able to reference this class in compiled code, such as templates.
The simplest fix for this is to ensure that this class is exported from the package's entry-point.

I'm using last angular-tree-component release

[adamkleingit]

Writing a comment someone sent me in PM: "for your lib I advice you to use https://github.com/ng-packagr/ng-packagr/blob/master/README.md to package 3th party lib to angular format"

[Gillardo]

Any news on this??? Really want to use Ivy

[HPS-Worldwide]

Same here, and event after applying a workaround, there's still this error :
ERROR in Value at position 11 in the NgModule.declarationss of TreeModule is not a reference: [object Object]

This is due to Ivy as well

[petebacondarwin]

This should be fixed in Angular ngcc via https://github.com/angular/angular/pull/31411

[matte00]

This should be fixed in Angular ngcc via angular/angular#31411

@petebacondarwin Don't work for me. I still have the error:

ERROR in There is no typings path for TreeNodeWrapperComponent in xxxxxxxxxxx/node_modules/angular-tree-component/dist/components/tree-node-wrapper.component.js.
We need to add an export for this class to a .d.ts typings file because Angular compiler needs to be able to reference this class in compiled code, such as templates.
The simplest fix for this is to ensure that this class is exported from the package's entry-point.

[LanderBeeuwsaert]

Just adding my experience here, that in Angular 8.1.3, this is still giving an error for me.

[petebacondarwin]

@LanderBeeuwsaert - you must use next versions of Angular to test ivy. For example, at the time of writing:

yarn info @angular/compiler-cli dist-tags

{ latest:
   '8.2.0',
  'v4-lts':
   '4.4.7',
  'v5-lts':
   '5.2.11',
  next:
   '9.0.0-next.0' }

The next version is currently 9.0.0-next.0.

[LanderBeeuwsaert]

Aha, thanks!
I had 3 libraries that had the issue mentioned above and seems that it's resolved for all of them.
(this issue anyway, I have some other issues cropping up, I will report them in angular github)

[tobiasengelhardt]

Closing this issue due to inactivity. Please open a new issue if the problem still exists.