-
Notifications
You must be signed in to change notification settings - Fork 47k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react-cache alphas don't work with 16.8+ #14780
Comments
Running into this error with react@16.8.1:
|
This can be closed. We are building react-cache from master and using a vendor folder in the example of the-platform. Previously it was improperly included as dependency instead of a peer dependency in the-platform. |
Yeah I think for now our recommendation is that you can copy paste its source but then you're on your own. The caching strategy is very unclear now and the whole thing will likely change a lot. We don't want any reusable libraries to start depending on it. We could plausibly add a big red warning on its import and then publish another alpha. If someone sends a PR seems ok to do it. |
I'd like to try to add a warning on import, it would however be my first contribution. |
How are we able to experiment with react-cache and Concurrent Mode at the moment? Since I am running into this issue with the versions below 😅
|
@bitttttten This is Suspense demo run in react "16.8" version. You can try suspense demo in the branch use-suepense. Hope help you. |
If you want to experiment you should be able to build from source. :-) |
Seems like building it from source is the only way for now. |
The current solution is indeed building from source, but if people want to streamline the process, you can try adding this to your package.json:
credit goes to this stackoverflow answer It would be awesome if react took advantage of the npm's "prepare" script and npm allowed installing from directories in git repos, but thats not likely going to change any time soon. For now, this solution is fine |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
Originally posted by @jaredpalmer in jaredpalmer/the-platform#70 (comment)
The text was updated successfully, but these errors were encountered: