Closed nac0n closed 4 years ago
Hi, this should be fixed as soon as I merge my PR for upgrading ATC to ng9. In Angular 9 an additional compilation step needs to be done before ATC can be compiled completely. My PR addresses this, as well as refactoring some of the code structure for easier development in the long term. Stay tuned for the ATC 9 update, shouldn't be too much longer before you can enable Ivy!
Great! Could you please reply in here when the PR is merged so that we can try it?
Same problem for me too
Same here.. Great to know that there is PR in pipeline..
@Nick-Angel Looks like the PR is stale. Any progress or help needed?
FYI i manage to build my app using angular-tree-component and Angular 10. I'm using the following version :
Package Version
@angular-devkit/architect 0.1000.0 @angular-devkit/build-angular 0.1000.0 @angular-devkit/build-optimizer 0.1000.0 @angular-devkit/build-webpack 0.1000.0 @angular-devkit/core 10.0.0 @angular-devkit/schematics 10.0.0 @angular/cli 10.0.0 @ngtools/webpack 10.0.0 @schematics/angular 10.0.0 @schematics/update 0.1000.0 rxjs 6.5.4 typescript 3.9.5 webpack 4.43.0
I just had to add the following in angular.json (build/builder/options) :
"allowedCommonJsDependencies": [
"lodash/get",
"lodash/every",
"lodash/some",
"lodash/isFunction",
"lodash/isString",
"lodash/find",
"lodash/first",
"lodash/isNumber",
"lodash/omit",
"lodash/pick",
"lodash/includes",
"lodash/throttle",
"lodash/defaultsDeep",
]
in order to hide the warning that angular generate when use commonjs or amd dependencies
Closing this because now there is an Angular 9 version of the tree. Please use v9.0.2 (or newer if available).
Please note that the package name changed from angular-tree-component
to @circlon/angular-tree-component
. We tried to keep the old name but couldn't transfer the publishing rights. This requires some path changes after the update. Take a look at the changelog to see the changes.
Please open a new issue if the problem still exists.
There seems to be a problem for us to use angular-tree-component, with Ivy enabled, in Angular 9.
We're working on a project that was running on Angular 7, which recently we have been working on upgrading to Angular 9. Our main goal was to keep up with the breaking changes done after Angular 8 and such we decided to upgrade to Angular 9 and start using Ivy also. This however seems to be a problem as running the application fails with Ivy on. Disabling Ivy gives us no errors and is our temporary solution, but we'd rather be able to use Ivy.
When running
ng serve
, it gives us these errors, manually modified paths and names for a bit of project secrecy:Errors:
Package.json:
Browser: Chrome
subsystem.module.ts:
Removing
.forRoot()
when importing TreeModule makes the application start with no errors ( the application doens't work though, but we do not get the errors on startup shown above). So my shot in the dark is that this error has something to do with how Ivy handles the package.