Broken with 16.8.0-alpha.0
See original GitHub issueHi!
As is expected for us bleeding edge-riders, react@16.8.0-alpha.0
breaks this package. I think it has something to do with react-cache
, maybe updating it to 2.0.0-alpha.1
would help?
barebones repro: https://codesandbox.io/s/oqy12yrk65
Img https://oqy12yrk65.codesandbox.io/node_modules/the-platform/Img.js:26:15
__EDIT: Yeah this is a react / react cache problem. They’ve updated the react-cache repo, but haven’t released the package. see https://github.com/facebook/react/issues/14558__
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:15
Top Results From Across the Web
Could not resolve dependency error peer react@"^16.8.0
this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. // package.json
Read more >React v16.8: The One With Hooks
Hooks have no breaking changes, and we have no plans to remove ... Note that to enable Hooks, all React packages need to...
Read more >Heads up: react@16.8.0-alpha.0 and react-dom@16.8.0 ... - Reddit
Heads up: react@16.8.0-alpha.0 and react-dom@16.8.0-alpha.0 are out - Dan's Tweet ... It will break stuff, have bugs, don't use in production, etc, etc....
Read more >дэн on Twitter: "Heads up: react@16.8.0-alpha.0 and react ...
Heads up: react@16.8.0-alpha.0 and react-dom@16.8.0-alpha.0 are out — for people who want the latest build with Hooks enabled.
Read more >react-hooks-helper - npm
Requirement ⚠️. To use react-hooks-helper , you must use react@16.8.0-alpha.0 . React Hooks is ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
the master branch already contains the fix. @jaredpalmer can we have an npm release plz?
figured things out finally: since react-cache does not have a published package compatible with react 16.8+ you have to build it from master and vendor it. this is exactly what was done in
the-platform
so you can just grab it from https://github.com/palmerhq/the-platform/tree/c1d20b31a49ab5df01f21448e2e6129ffd51a57e/example/vendor/react-cache