Closed seanlandsman closed 7 years ago
More information:
This seems related to bluebird.js
type versions. The errors listed above also occur in ag-grid v8.1.1, after having upgraded my @types/bluebird
npm package.
Here is the version listing of what I had tried:
Package Current Wanted Latest Location
@types/bluebird 3.0.37 3.5.2 3.5.2 blueline-grid-gridcommand
When I use @types/bluebird 3.0.37
, with ag-grid 8.1.1
the application works fine.
When I use @types/bluebird 3.5.2
, with ag-grid 8.1.1
the application does not load at run-time.
When I use either @types/bluebird 3.0.37
or @types/bluebird 3.5.2
with ag-grid 8.2.0
the application does not load at run-time.
Thanks, Don
Closing due to inactivity - please feel free to open a new issue and I'll take a look
Moved from: https://github.com/ceolter/ag-grid/issues/1554
I'm submitting a ... (check one with "x")
Current behavior
After upgrading ag-grid and ag-grid-aurelia from v8.1.1 to v8.2.0, I see the errors below at run-time in the browser JavaScript console.
Although there is not a clear pointer to the ag-grid source code in the error output, I have verified this is caused by the ag-grid upgrade, because reverting back to the previously-installed 8.1.X version eliminates these errors.
The error is fatal, in that it looks like they are occurring during the dependency-resolution phase and they prevent loading/bootstrapping of the Aurelia application.
Expected behavior
The ag-grid components should not throw run-time errors, and should not interfere with loading of the application.
Minimal reproduction of the problem with instructions
Use any Aurelia skeleton application, include ag-grid, and compare behavior of v8.1.1 vs v8.2.0.
What is the motivation / use case for changing the behavior? See above.
Please tell us about your environment: Mac OS
ag-Grid version: 8.1.1/8.2.0
Browser: All
Language: TypeScript 2