mirror of
https://github.com/zebrajr/react.git
synced 2026-01-15 12:15:22 +00:00
e23673b511
* Remove react/unstable_cache We're probably going to make it available via the dispatcher. Let's remove this for now. * Add readContext() to the dispatcher On the server, it will be per-request. On the client, there will be some way to shadow it. For now, I provide it on the server, and throw on the client. * Use readContext() from react-fetch This makes it work on the server (but not on the client until we implement it there.) Updated the test to use Server Components. Now it passes. * Fixture: Add fetch from a Server Component * readCache -> getCacheForType<T> * Add React.unstable_getCacheForType * Add a feature flag * Fix Flow * Add react-suspense-test-utils and port tests * Remove extra Map lookup * Unroll async/await because build system * Add some error coverage and retry * Add unstable_getCacheForType to Flight entry
379 B
379 B
react-suspense-test-utils
This package is meant to be used alongside yet-to-be-released, experimental React features. It's unlikely to be useful in any other context.
Do not use in a real application. We're publishing this early for demonstration purposes.
Use it at your own risk.
No, Really, It Is Unstable
The API may will change wildly between versions.