Sebastian Markbåge
@sebmarkbage.calyptus.eu
React · Next.js · Vercel
Then click the little green Node.js logo in the Chrome DevTools to open the server.
January 15, 2025 at 4:31 PM
Then click the little green Node.js logo in the Chrome DevTools to open the server.
Now that the dust has settled on the funny naming of the experimental Taint APIs. Have you tried them? Did you find them useful? Did they help protect against any mistakes?
react.dev/reference/re...
react.dev/reference/re...
en.wikipedia.org/wiki/Taint_c...
react.dev/reference/re...
react.dev/reference/re...
en.wikipedia.org/wiki/Taint_c...
December 13, 2024 at 5:51 PM
Now that the dust has settled on the funny naming of the experimental Taint APIs. Have you tried them? Did you find them useful? Did they help protect against any mistakes?
react.dev/reference/re...
react.dev/reference/re...
en.wikipedia.org/wiki/Taint_c...
react.dev/reference/re...
react.dev/reference/re...
en.wikipedia.org/wiki/Taint_c...
Inspecting Server Components in React DevTools also works in development mode.
December 12, 2024 at 4:25 AM
Inspecting Server Components in React DevTools also works in development mode.
I'm working on built-in profiling of both Client and Server Components in Chrome DevTools Performance tab. Thanks to the new performance.measure() extensions. h/t Andrés Olivares
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
December 12, 2024 at 4:25 AM
I'm working on built-in profiling of both Client and Server Components in Chrome DevTools Performance tab. Thanks to the new performance.measure() extensions. h/t Andrés Olivares
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
Catch the gotcha?
This cache entry is specific to only a specific user because it uses the current user to compute its output. It means the current user must be part of the cache key otherwise this cache entry could leak between users.
"use cache" handles this automatically for closures.
This cache entry is specific to only a specific user because it uses the current user to compute its output. It means the current user must be part of the cache key otherwise this cache entry could leak between users.
"use cache" handles this automatically for closures.
November 1, 2024 at 2:57 PM
Catch the gotcha?
This cache entry is specific to only a specific user because it uses the current user to compute its output. It means the current user must be part of the cache key otherwise this cache entry could leak between users.
"use cache" handles this automatically for closures.
This cache entry is specific to only a specific user because it uses the current user to compute its output. It means the current user must be part of the cache key otherwise this cache entry could leak between users.
"use cache" handles this automatically for closures.
Don't sleep on this.
While we do have some static parameterization for storage location. We don't actually want dynamic parameterization in the cache directive. That would be too early. It should be able to parameterize it using the content of the function and only that.
nextjs.org/blog/our-jou...
While we do have some static parameterization for storage location. We don't actually want dynamic parameterization in the cache directive. That would be too early. It should be able to parameterize it using the content of the function and only that.
nextjs.org/blog/our-jou...
November 1, 2024 at 2:41 PM
Don't sleep on this.
While we do have some static parameterization for storage location. We don't actually want dynamic parameterization in the cache directive. That would be too early. It should be able to parameterize it using the content of the function and only that.
nextjs.org/blog/our-jou...
While we do have some static parameterization for storage location. We don't actually want dynamic parameterization in the cache directive. That would be too early. It should be able to parameterize it using the content of the function and only that.
nextjs.org/blog/our-jou...