I'm getting the following error when trying to import the ag grid module in an Angular 8 app using Ivy.
ERROR in There is no format with import statements in 'path_to_node_modules/node_modules/ag-grid-angular' entry-point.
The error goes away if i disable Ivy. Does anyone know a workaround?
Packages versions:
"ag-grid-angular": "^21.0.0",
"ag-grid-community": "^21.0.0",
"ag-grid-enterprise": "^21.0.0",
This is actually an issue on the Angular CLI side - see this issue comment here: https://github.com/angular/angular/issues/29564#issuecomment-486957461
In the meantime I believe you'll be able to get Ivy to work with ag-Grid (and other similar libraries) by using #angular/compiler-cli#next, instead of the latest Angular 8 release.
Related
I am using AG Grid in my Angular application and since upgrading from v27 to v28 I get the following error in my app.
Error: src/app/app.module.ts:18:18 - error TS2339: Property 'withComponents' does not exist on type 'typeof AgGridModule'.
I thought this was required when providing your own custom components to AG grid?
Since v28 the AgGridModule no longer needs the .withComponents() method as all user applications will now be using Ivy. The method used to handle registering custom components as EntryComponents but that is no longer required with Ivy and was deprecated by Angular.
So to fix this error make the follow change and your custom components will still work.
- AgGridModule.withComponents([CustomComp]);
+ AgGridModule
See the AG Grid Docs on Angular Compatibility for more details.
I am trying to control a servo using JetsonNano and a PCA9685 board. I am on Jetpack 4.3 and using python3. After a recent update I started to end up with the following error.
"NotImplementedError: pwmio not supported for this board"
from adafruit_servokit import ServoKit
kit=ServoKit(channels=16)
kit.servo[0].angle=90 ## Horizontal motion
kit.servo[1].angle=0 ## Vertical Motion
I've got the same issue at JetPack 4.6.
On JetPack 4.5.1 everything ok. I think something wrong with L4T 32.6.1...
Here is the issue
error TS2416: Property 'supportsDOMEvents' in type 'ɵangular_packages_platform_browser_p
latform_browser_o' is not assignable to the same property in base type 'ɵDomAdapter'.
As #DrTeeth already mentioned, it's hard to help w/o any further infos.
But I've had a similar problem and want to share what had helped for me: This was a simple inconsistency of my dependencies. I', using a 3rd party Angular Component Library which was incompatible with the newer (Ivy-enabled) version, after I updated Angular itself. For me, the error message had some details about the package in question and after updating it, too, everything worked fine.
I'm updating my angular project to use angular 9. In angular 8 I was using ng5-bootstrap-modal, but now I'm getting error:
ERROR in node_modules/ng5-bootstrap-modal/dist/bootstrap-modal.module.d.ts:4:22
error NG6002: Appears in the NgModule.imports of SharedModule, but could not be resolved to an NgModule class.
This likely means that the library (ng5-bootstrap-modal) which
declares BootstrapModalModule has not been processed correctly by
ngcc, or is not compatible with Angular Ivy. Check if a newer version
of the library is available, and update if so. Also consider checking
with the library's authors to see if the library is expected to be
compatible with Ivy.
Did anyone face the same issue?
I have a question about ract-router 2.0 migration in my React app.
I removed every mixin and calls to this.props.history, like explained in the migration guide, but I still have warnings about it in the console :
Warning: [react-router] props.history and context.history are deprecated. Please use context.router
Actually, I found out in the debugger there is one warning for each nested component on the current page : RouterContext, App, and Posts
Any idea where it could come from ?
There's a bug with RC4 and the React DevTools that come from the dev tools attempting to inspect all the props and context. This will be fixed in the new RC.
You can disable this warning by going to /node_modules/react-router/lib/RouterUtils.js and commenting out lines 28-30.