Curious if there's a good pattern for having open source projects that are dependencies of applications to automatically include skills for agents that could be symlinked from the node_modules directory. Seems interesting to provide context for agents for a release of the installed dependency.
Been using handy.computer for dictation using Parakeet (v3) for a few weeks now. Enabling the post processing step to make corrections to the transcribed text has been a game changer.
Now if I make a mistake while speaking, I don't have to restart, I can just make the correction in flow!
Just ported my personal site over to @astro.build with a custom @bun.sh adapter I wrote 🚀
👋 I'm currently looking for my next role, so if you're hiring, reach out!
- Astro + Bun for blazing fast SSR
- Supports ISR and SWR
- Hosted behind @cloudflare.social
github.com/wyattjoh/ast...
Gifting another one out because people need to be reading this
www.theverge.com/policy/86741...
Made a little tool with Ink that lets you manage your Claude Code Skills, MCPs, and Slash Commands in a neat TUI
github.com/wyattjoh/cla...
Ever wondered how much Plex you've watched? I made a thing!
wrapped.wyattjoh.dev
I felt really inspired watching your talk. In the age of AI and how it’s making people think about new UX loops that they never even considered before. Really excited to see what the next era is going to look like.
These AI generated "wrapped" are getting out of hand 🤣, very cool one from @incident.io
This is so freaking cool. I’m hoping for a future where all the Peter F Hamilton books become a reality with the device in your pocket alone
Reminds me of the GitHub 3D model files they released that one year, I went and sent it off to get printed and keep it on my desk
How'd you generate that 👀
An aside, been using httpie instead of curl for the past few years, reading curl commands now makes me feel like I'm reading a foreign language 😅
Such a cool article!! Love seeing these types of projects in the crypto space, they're so cool!
My @reactadvanced.gitnation.org talk is up!! In it I discuss some changes to the segment API's that we introduced in Cache Components in Next.js and explain how the new mental modal is designed to give feedback during development to enhance the navigation experience.
gitnation.com/contents/fro...
I loveddd that talk too. Such a refreshing take actually focusing on the meat of UX problems that are interesting.
Depends! Next.js includes a lot of data in the cache keys for different responses so it's important that those responses respect the `?_rsc=` hash which may be high cardinality.
What's the intended state of your deployed application wrt CDN cache behaviour?
There is no revalidation phase that occurs for any of the caches that is independent of the static render for the static shell. When the static shell needs to revalidate, all caches for the render are treated as expired and not fetched. This is the interplay between the Cache Boundaries and ISR
The same rules apply here. If you're using replicas here, you should likely change that value to zero to ensure that the memory cache is not used and instead prefer the shared FS based cache.
I'm not sure what specifically you're showing in the video (I see that you're refreshing, but not sure what the desired state should look like), but it's also important to know that when the cache life value is too low, it's treated as dynamic.
If you're using a custom cache handler in a distributed mode, you'll need to set `cacheMaxMemorySize` to `0` in your Next.js config file to disable the built-in memory cache. It'll then only rely on the filesystem and the custom cache handlers.
When Next.js is running locally, it's saved in a file in the `.next` directory as a file ending with `.html`. On Vercel, that file is stored by the Vercel Infrastructure which responds to requests with either a complete static shell (no dynamic) or a partial one (some dynamic).
For that user that made that request, they will be served the stale copy of the static shell, while the framework would be triggering a static render out-of-band to replace the stale content. Once the expiry time has been reached, it will refuse to serve the stale shell and instead should block.
As the intermediate caches present on a page all contributes to the static shell itself, it also inherits it's cache life. When a request is made after the revalidation time but before the expiry time, the cache handler should return `undefined` to indicate that it's no longer fresh.
If the cache entry has expired in the cache handler, as the docs indicate, it should return `undefined`. Revalidation is a process that will run the "work function" of the cache entry again, followed by a call to `set` to update the entry. Which part of background revalidation are you curious about?
Private is indeed not persisted, it’s only used as an escape hatch for those that can’t adopt the other cache directives. Only used to improve the prefetching and client router cache.
Next.js 16
• Cache Components
• Turbopack enabled by default
• Turbopack file system caching (beta)
• Optimized navigations and prefetching
• Improved caching APIs
• Build Adapters API (alpha)
• React 19.2
nextjs.org/blog/next-16
Next.js 16 (beta)
• Turbopack enabled by default
• Turbopack file system caching (beta)
• Optimized navigations and prefetching
• Improved caching APIs
• Build Adapters API (alpha)
• React 19.2
nextjs.org/blog/next-1...
As an exercise to learn Rust this holiday, I took time to rewrite a CLI tool I wrote initially in Deno into Rust using Claude Code. Had it annotate any Rust-isms in the code so it's easier to read and understand, learned a lot!
Looking forward to the strict by default!
