You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading Next JS to 9.4.2 i'm having issues with Ag Grid tables. The issue seems to be with the fact that @ag-grid-community/core is 'implicitly' available but i'm required to include it in package.json as i'm using Yarn PnP.
Typescript gives me this error:
import("/Users/nodeworks/Documents/Projects/crimson/node_modules/@ag-grid-enterprise/all-modules/node_modules/@ag-grid-community/core/dist/cjs/interfaces/iModule").Module[]'
is not assignable to parameter of type
'import("/Users/nodeworks/Documents/Projects/crimson/node_modules/@ag-grid-community/core/dist/cjs/interfaces/iModule").Module[]'
So it's trying to load a package as a sub-package of ag-grid-enterprise....which i'm guessing would work if I didn't have to include ag-grid-community/core in my package.json since it's trying to load from that? But I can't not have it there since PnP complains.
I realize this is most likely an issue that needs to be fully resolved on the ag-grid side of things, but i'm wondering if there is a way I can hack it for now in next.config.js where I can alter the webpack config to resolve the package automatically?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
After upgrading Next JS to 9.4.2 i'm having issues with Ag Grid tables. The issue seems to be with the fact that @ag-grid-community/core is 'implicitly' available but i'm required to include it in package.json as i'm using Yarn PnP.
Typescript gives me this error:
So it's trying to load a package as a sub-package of ag-grid-enterprise....which i'm guessing would work if I didn't have to include ag-grid-community/core in my package.json since it's trying to load from that? But I can't not have it there since PnP complains.
I realize this is most likely an issue that needs to be fully resolved on the ag-grid side of things, but i'm wondering if there is a way I can hack it for now in next.config.js where I can alter the webpack config to resolve the package automatically?
Beta Was this translation helpful? Give feedback.
All reactions