Explore tweets about #react.suspense on Twitter
#100DaysOfCode
Day 100:
- Personal Project2
- Worked on styling
- Learned about React.suspense & Lazy loading
- Searched about hosting options
100 days~ but I'll continue coding~ :)
0
4
4
This particular GitHub comment has some great updates on the React Suspense Saga.
If React winds up overly complex after this is all over, it’s nice to remember that there’s still Preact (spoiler - your bundle sizes will likely be smaller than even Svelte produces) https://t.co/xzZEwocG4j
@AdamRackis @RyanCarniato @VdeVentura @dan_abramov I think these couple comments from Dan in the "Releasing Suspense" thread answer the questions atm:
https://t.co/8qCJoLpXLm
2
0
12
Если «React Suspense» сам себя остановил на стадии эксперимента, то это можно считать успешным релизом? 🤔
2
0
18
⚛️ Is React Suspense Ready Yet?
Тред о том, чему можно поучиться у инженеров «FB», что закладывали Suspense-логику в реконсилер.
Ну... помимо того, что код можно ещё и релизить.
1
3
44
Really exciting news! React Suspense is on track for a 2027 release! https://t.co/IDd3gV4gs3
“We see the light at the end of the tunnel.”
0
0
2
#HoyAprendi React te proveé de herramientas de code-splitting muy simples para mejorar la performance de tu app. Así podés usar React.lazy() y React.Suspense para cargar componentes dinámicamente: https://t.co/8r4YcWm9nu
1
0
0
¿Se imaginan aprender React Suspense y SWR creando una Pokedex? 😮
Próximamente lo podrán hacer si compran mi libro 🙂 https://t.co/8hmmQkEd60
1
2
7
using react suspense as a loading boundary is honestly pretty damn useful, it's a shame the react team is so overly ambitious and professional that we will maybe never see it supported and endorsed in our favorite data fetching libraries
1
0
2
SWR — React Hooks library for data fetching
🔗 https://t.co/1m6LzX4dxS
🏷 #caching #fetch #link #react #suspense https://t.co/ePqE25LV1v
0
4
3
いつになったらReact、Suspenseの仕様が正式になるんだ・・・
Productionに入れていいのかなあ
1
0
0
リロードすると画面がチラつくな〜と思ってたけど
React.LazyとReact.Suspense使い方があかんかったんか！！！！！
なるほどなるほど。完全に理解した！
0
1
2
Fetch with React Suspense相当のフックを自作したら1日が終わった。
整合性のある並行更新がポイントだったから、昔勉強したトランザクション分離を思い出す感じだった。大域離脱無しかつシンプルなstateHookぽく作れたので満足
0
0
0
React Suspenseの目論見書を見て、宣言的とは何か再考してる。
「何か」を宣言 → 👍DX
だけじゃなくて、
「いつ・手段」を移譲・最適化 → 👍UX
も凄い強みなんだな。ReactDOMも確かにそうだ。data fetchもそうしようって思想に唸らされる、頭いい
0
0
0
I know I don't tweet much about web dev stuff anymore, but in case you're curious: I was today years old when I learned about React Suspense. Oh and I also want to drive frontend state using a GraphQL subscription of a huge union type.
tl;dr join TTC to stop me
1
0
2
What’s the best way to use React Suspense and SSR right now? I have some code that has a suspense boundary needed on the client, but will never fallback on the server. Should I just conditionally wrap in Suspense? E.g. render Suspense if typeof window !== ‘undefined’
0
0
1
