⚛ Your Suspense Cache likely already has a Context (. Don't put the Context inside another Context for no reason! (eg if no mutation needed). *react-cache is very extremely unstable so dont use now but this is likely a useful insight

@mikhail_osher @ryanflorence React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED. 🤣.

@takepepe 汎用のcacheはここっぽい. 引数1つ1つについてMap(プリミティブ型の引数)/WeakMap(オブジェクトな引数)を入れ子にして辿ってるんですね.ちょっと富豪的な気がしたけどリクエスト単位ですぐに消えるからいいのか.

react/cache in use #Web #Development #openmovement #PHP

📢 ¡Nuevo Post! @_ivanrodri_. nos enseña React data-fetching con Suspense👨🏻‍💻🕵 #react #suspense #fetch #reactcache #javascript 🌍🔥 aprende a cargar datos asíncronos de una forma totalmente declarativa ⚛ @javascriptd @JavaScriptDaily @reactdaily @reactDOM.

@nkSaraf98 @react @dan_abramov @sebmarkbage I've never used `cache` on server. Maybe we can't? Server is stateless which means dispatcher is not preserved?

React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED 😆

최초 렌더에 포함되는 캐시 바운더리에서는 모두 하나의 저장소를 재사용됨. 이후 렌더에서 새 캐시 바운더리가 마운트되거나 useCacheRefresh 가 명시적으로 호출된 바운더리에서는 새 저장소가 생성되고 사용됨.

@sebmarkbage @ryanflorence @dan_abramov @samselikoff @jhooks Data fetching was a bad example, I meat something like ReactCache.push("users", createNewUser()).

@JSTechLead @passle_ flow uses the .js extension, but it's a superset of JS, similar to typescript. example: note the magic "@ flow" comment at the top, the `type` declarations, the generic type params (`<T>`) in function definitions. function params are also type-annotated.

@mjackson I got a good chuckle when I saw this in the React codebase:

react-cache 구현을 지금 봤는데, cache 함수 인자들을 serialization해서 비교하는게 아니라 WeakMap으로 레퍼런스 비교하네. 이러면 react-query처럼 무지성 캐시키 쓰면 안되겠다.

@Swizec Thanks! I found this implementation for wrapping promises.

Play with spinners and network to better understand React Suspense.🏷 #React #Suspense #ReachRouter #ReactLazy #ReactCache.🔍 Demo:

Second, a WeakMap-based approach. I _directly_ copied this out of the source for React's experimental cache: . It creates a nested tree of "cache nodes" based on argument references. I just got this working a few minutes ago, so haven't tested extensively.

Ok, easier approach to learn React source code might be reading through the test specs #HardcoreReact.

@Akash940 Yes, if you don't patch the global.fetch, which you shouldnt, it's just a PoC, you can do LRU cache per resource like react-cache does

The implementation of the `cache` API is interesting. 👀 .