react-reconciler failing when using react-konva
See original GitHub issueI’m trying to use react konva in one of my projects but unfortunately it fails with the following error in the development version.
react-reconciler.development.js?dbf7:497 Uncaught TypeError: Cannot set property 'getCurrentStack' of undefined
at Object.setCurrentFiber (react-reconciler.development.js?dbf7:497)
at performUnitOfWork (react-reconciler.development.js?dbf7:6007)
at workLoop (react-reconciler.development.js?dbf7:6074)
at HTMLUnknownElement.callCallback (react-reconciler.development.js?dbf7:1613)
at Object.invokeGuardedCallbackDev (react-reconciler.development.js?dbf7:1652)
at invokeGuardedCallback (react-reconciler.development.js?dbf7:1509)
at renderRoot (react-reconciler.development.js?dbf7:6152)
at performWorkOnRoot (react-reconciler.development.js?dbf7:6800)
at performWork (react-reconciler.development.js?dbf7:6753)
at requestWork (react-reconciler.development.js?dbf7:6664)
The easiest way to reproduce it for me was to: #1 install the react webpack typescript starter kit from https://github.com/vikpe/react-webpack-typescript-starter #2 Add the ColoredRect example from https://github.com/lavrton/react-konva into my app.tsx #3 Start the dev build. (npm run start-dev)
Some additional things:
- It works on the prod build (npm run start-prod)
- I did try it on React 15 & 16.2 & 16.3
- Konva rect version: 1.7.1
- Konva version: 2.0.2
Looking at the place it fails it seems that in the dev version of the react-reconciler resolved this call to undefined: var ReactDebugCurrentFrame = ReactInternals.ReactDebugCurrentFrame;
While this is failing in the react-reconciler, I’m still wondering if this is because of the usage of the react-reconciler library within Konva, as it works in the prod version.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top GitHub Comments
I’m having similar issues, even when upgrading
react
,react-dom
,konva
, andreact-konva
Probably we should add the more explicit warning because looks like npm warnings are not enough.