Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not compatible with new version of React (15.4.0)

See original GitHub issue

Latest React (15.4.0) doesn’t expose internals through react/lib anymore:

modulesModuleNotFoundError: Module not found: Error: Cannot resolve module 'react/lib/ReactInstanceMap'

From React blog:

However, there is a possibility that you imported private APIs from react/lib/*, or that a package you rely on might use them. We would like to remind you that this was never supported, and that your apps should not rely on internal APIs. The React internals will keep changing as we work to make React better.

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

lavrtoncommented, Jun 13, 2017

@Guria react-konva will be updated to work with react 16.

Currently, I don’t have any plans to update the lib until react v16 official publish.

0reactions

twobitcommented, Jul 27, 2017

There’s a new thread about the React 16 beta:

There is no react/lib/* and react-dom/lib/* anymore. Even in CommonJS environments, React and ReactDOM are precompiled to single files (“flat bundles”). If you previously relied on undocumented React internals, and they don’t work anymore, let us know about your specific case in this issue, and we’ll try to figure out a migration strategy for you.

Maybe somebody over there has ideas on how to migrate to a non react/lib approach.