Member of Devographics (State of JS/CSS/HTML/React surveys).
✨ https://www.ericburel.tech/
@cursor.com.web.brid.gy
@cursor.com.web.brid.gy
Look at this
Look at this
Agents > models even fine-tuned
Agents > models even fine-tuned
Don't forget to take #StateOfJS 2024! 📊
survey.devographics.com/survey/state...
Don't forget to take #StateOfJS 2024! 📊
survey.devographics.com/survey/state...
I thought I was being smart pushing the thing as far as I could and that it would break and here's the result
The model only tripped on forgetting a default export (kind of mistake I would do lol)
The image export does work
This is just insane
I thought I was being smart pushing the thing as far as I could and that it would break and here's the result
The model only tripped on forgetting a default export (kind of mistake I would do lol)
The image export does work
This is just insane
#NextJS #ReactJS #JavaScript #JustAlignYourVersionsAtThisPoint
#NextJS #ReactJS #JavaScript #JustAlignYourVersionsAtThisPoint
I am using it to generate demo apps for my Astro.js training, it's the perfect use case for app generation with AI
I am using it to generate demo apps for my Astro.js training, it's the perfect use case for app generation with AI
But it seems that Copilot already knows better!!
But it seems that Copilot already knows better!!
"Using React Context in Astro - with Nanostores"
astropatterns-git-drafts-lbke.vercel.app/p/react-love...
#react #nextjs
"Using React Context in Astro - with Nanostores"
astropatterns-git-drafts-lbke.vercel.app/p/react-love...
#react #nextjs
- the first spike is the right way, using streams
- the second spike is the wrong way, copying the file in memory and then streaming it
Want to learn the right solution? Read NextPatterns
⬇️
nextpatterns.dev/p/gems/route...
- the first spike is the right way, using streams
- the second spike is the wrong way, copying the file in memory and then streaming it
Want to learn the right solution? Read NextPatterns
⬇️
nextpatterns.dev/p/gems/route...
It's not that easy!
It's not that easy!
However, I don't think there is an equivalent to React "cache" function, which is scoped to the current user request.
So keep in mind this pattern works for shared values: theme, i18n tokens, sitemap, but not for user-specific values.
However, I don't think there is an equivalent to React "cache" function, which is scoped to the current user request.
So keep in mind this pattern works for shared values: theme, i18n tokens, sitemap, but not for user-specific values.
In Next.js, this is roughly equivalent to using "unstable_cache", that is shared across requests
In Next.js, this is roughly equivalent to using "unstable_cache", that is shared across requests
This way, I can keep this shared value in memory, and get it from components that are rendered by this page, without needing to use props
This way, I can keep this shared value in memory, and get it from components that are rendered by this page, without needing to use props
This sitemap file is actually an array, each value corresponds to a specific page
So, for the page "/tshirt", I'd like to get the corresponding configuration
This sitemap file is actually an array, each value corresponds to a specific page
So, for the page "/tshirt", I'd like to get the corresponding configuration
I am trying to figure how to simplify this syntax even more
I am trying to figure how to simplify this syntax even more