@rokuyondev.bsky.social
Would this still be the same with data attributes?
data-loading-bg={loading}
className=“bg-green-500 data-[loading-bg]:bg-yellow-500”
data-loading-bg={loading}
className=“bg-green-500 data-[loading-bg]:bg-yellow-500”
November 17, 2025 at 1:17 AM
Would this still be the same with data attributes?
data-loading-bg={loading}
className=“bg-green-500 data-[loading-bg]:bg-yellow-500”
data-loading-bg={loading}
className=“bg-green-500 data-[loading-bg]:bg-yellow-500”
When does the open House end?
September 30, 2025 at 2:07 PM
When does the open House end?
Would be super interesting to read tho.
September 20, 2025 at 7:56 AM
Would be super interesting to read tho.
A breakdown of stuff like this would be cool to read
September 13, 2025 at 6:43 AM
A breakdown of stuff like this would be cool to read
Thanks for taking the time to explain it! Will read the article as well. Thank you!
August 26, 2025 at 4:53 AM
Thanks for taking the time to explain it! Will read the article as well. Thank you!
Excuse my ignorance. What is bidirectional conversion and what’s the purpose? Especially in nuqs. Super interested but don’t quite get it 😅
August 25, 2025 at 2:43 PM
Excuse my ignorance. What is bidirectional conversion and what’s the purpose? Especially in nuqs. Super interested but don’t quite get it 😅
Not sure passing props would be possible since ServerComp would just be the result from `fetchRSC`...
May 4, 2025 at 6:51 AM
Not sure passing props would be possible since ServerComp would just be the result from `fetchRSC`...
The use case is to create a tiny React widget that users could load and that widget would fetch the static RSC payload file and render it, so in this case I wouldn't control the HTML.
Would it also be possible to pass props to the server component like <ServerComp title={<Header/>}/>?
Would it also be possible to pass props to the server component like <ServerComp title={<Header/>}/>?
May 4, 2025 at 6:51 AM
The use case is to create a tiny React widget that users could load and that widget would fetch the static RSC payload file and render it, so in this case I wouldn't control the HTML.
Would it also be possible to pass props to the server component like <ServerComp title={<Header/>}/>?
Would it also be possible to pass props to the server component like <ServerComp title={<Header/>}/>?
2/ I read this post from @daishikato.com blog.axlight.com/posts/though... and was interested in how to generate the RSC payload and serve it as a static asset, but couldn't figure out how to approach it as the generated fetchRSC threw an error.
May 4, 2025 at 6:45 AM
2/ I read this post from @daishikato.com blog.axlight.com/posts/though... and was interested in how to generate the RSC payload and serve it as a static asset, but couldn't figure out how to approach it as the generated fetchRSC threw an error.
1/ @devongovett.bsky.social Not sure if my question makes sense, but is there a way with parcel to generate the RSC payload during build or with a script and then put the RSC payload in a file and serve it as a static asset? We could then fetch the static asset with fetchRSC and render it.
May 4, 2025 at 6:43 AM
1/ @devongovett.bsky.social Not sure if my question makes sense, but is there a way with parcel to generate the RSC payload during build or with a script and then put the RSC payload in a file and serve it as a static asset? We could then fetch the static asset with fetchRSC and render it.