leerob.com
Building @vercel.com and teaching about @nextjs.org.
338 posts
10,795 followers
114 following
Active Commenter
comment in response to
post
1. Browsers handle title/metdata outside of <head> just fine
2. We haven't seen any SEO impact (this is the same pattern sites like Amazon use, it's not novel)
3. It's not Vercel specific (this is standard `next start` behavior)
4. This was a community requested feature
comment in response to
post
The post is FUD. I don't have the energy to write up a long response on why yet, but it's simply not accurate.
comment in response to
post
We can't 😭 It's a GitHub limitation
comment in response to
post
Glad to hear it! Yeah the new stateless protocol is much better.
comment in response to
post
Yeah but the story is even easier. You can run compute, either before or after the cache. That’s p much it
comment in response to
post
Still cooking in this PR github.com/vercel/next....
comment in response to
post
Writing has been on the wall for a while, just finally starting to slowly roll out example updates, followed by actually deprecating the product soon (and change management)
We moved forward with Fluid compute instead
comment in response to
post
`dynamic` can be the entire route. Make your `page.tsx` file render the `<Route>` component and use `dynamic`.
comment in response to
post
nextjs.org/docs/app/gui...
comment in response to
post
Can you share what issues you saw so we can fix?
comment in response to
post
What docs are you referring to? I don't believe we show this anywhere
comment in response to
post
Vercel for the backend is Vercel 😁
Can deploy APIs, connect to databases/queues with first-party integrations, built-in logging/observability.
And can also bring & use your backend frameworks (e.g. Express, Hono, etc)
comment in response to
post
You can also have v0 generate vanilla HTML if you don’t want React stuff. Also can ask it for Svelte.
comment in response to
post
Andrew has made some massive improvements to prefetching, including fetching segments. It's under an experimental flag `clientSegmentCache`.
x.com/acdlite/stat...
comment in response to
post
Myth: you can fetch data with "use server"
Taking your RPC explanation further, could talk about how you can think of it like a POST, and the broader umbrella of Server Functions as maybe where you could have a GET.
comment in response to
post
Myth: RSC requires dynamic rendering
You've covered it already in previous posts, but linking back to your longer explanations would be nice.
comment in response to
post
Myth: RSC doesn't work with CSS-in-JS
It would probably be helpful to talk about runtime CSS-in-JS versus zero runtime variants.
comment in response to
post
It's running on the same Vercel infrastructure as everyone else. It's a pretty simple site, although we do have some overly heavy SVGs on the homepage I'd like to replace.
comment in response to
post
I got in touch with the TikTok creator. They took down the video. Unfortunately they got scammed by a job posting on Indeed claiming to be from Vercel.
comment in response to
post
This was false. The TikTok poster took down the video.
They unfortunately got scammed by a got posting on Indeed claiming to be Vercel.
comment in response to
post
It's not. Appears to be some kind of skit.
comment in response to
post
Hot
comment in response to
post
That's like saying solar companies invented LED lights to leave lights on longer.
The whole point is to use fewer resources.
The default behavior of Next.js is to prerender. And with PPR we're trying to prerender to static as much as possible. You're only using compute when it's necessary.
comment in response to
post
Yes, Vercel employs me. Yes, I want Next.js to be great when self-hosting or not on Vercel. Will I recommend Vercel first if someone asks me? Also yes, or I wouldn't work here if I didn't believe in the product.
comment in response to
post
That's not necessarily true. Yes, you can have unconscious bias, but part of my job is confronting bias and being pretty open about it.
comment in response to
post
This argument gets confusing to me because Vercel also supports SPAs who want the PR previews as well. From a Vercel perspective, we want to support *all* frameworks and types of apps.
comment in response to
post
There's a bunch exploring RSC:
• parcel: parceljs.org/recipes/rsc
• waku: waku.gg
• redwood: redwoodjs.com/blog/rsc-now...
• mfng: github.com/unstubbable/...
• kotekan: github.com/bndkt/kotekan
• tangle: github.com/lubieowoce/t...
• twofold: github.com/twofold-rsc/...
comment in response to
post
If you figure out a good way to get this through, please let me know. I've tried and it hasn't really landed, probably cause everyone assumes my bias.
comment in response to
post
This isn't the same thing, though.
- Agree we want to (and will continue to) invest in React
- We also invest in other frameworks and libraries
- RSC is not tied to Vercel, so it's not vertically integrated
comment in response to
post
Been there, absolute nightmare material 😱
comment in response to
post
Agreed. Made a PR.
github.com/vercel/next....
comment in response to
post
Yeah I think something like this is closer, maybe too verbose
comment in response to
post
To clarify, are you advocating for not showing inline "use server" usage, or just this specific example?
comment in response to
post
IMO "use cache" is similar to all of the upcoming Next.js changes (dynamicIO, PPR). If we could have known from the start, we'd short circuit there.
But the only way to arrive at these APIs is to put something out there, watch and listen, and iterate. Unsatisfying but seems to be true.
comment in response to
post
I hear you, but this would be a pretty big breaking change, so likely not something we would do soon. Longer term, I'd like to move away from dotenv entirely, personally.
comment in response to
post
I have a plan to re-do the entire page, but it will take a bit longer to get right. We'll probably keep templates to get started but that marketing-speak needs to go.
comment in response to
post
github.com/vercel/next....
comment in response to
post
You can click on the team name in the top left of the navigation bar to switch between other teams.
comment in response to
post
Next.js *prerenders* by default. Caching is more nuanced, it depends what we're referencing. We stopped caching many things by default in Next.js 15.
x.com/leerob/statu...
comment in response to
post
For example, when I go to my "leerob" team, that value is persisted and if I go directly to vercel .com, it redirects me to the last team I used.
comment in response to
post
I'm still a bit confused. Using GitHub as your OAuth provider doesn't automatically assume anything on the Vercel side - it is just forwarding an email over. Then, on Vercel, you went to your hobby team. Was that not the last team you were using?
comment in response to
post
Did you already look at the Observability tab? There's a specific section for Image Optimization. We also have some docs here for ways to optimize.
vercel.com/docs/image-o...
comment in response to
post
It should remember the last team selection you made and persist that if you navigate to the Vercel dashboard directly versus the team URL.
Maybe you can DM me a video so I can see what you're seeing?
comment in response to
post
Are you saying it is defaulting to your Vercel team connected to your personal GitHub, versus the Vercel team connected to your work GitHub?
comment in response to
post
Thanks for sharing, this is painful. Will have our team look into this 🙏
comment in response to
post
Ah, it seems you pushed a fix – didn't see your other reply.
comment in response to
post
You can think about OG images similar to other pages:
• /app/opengraph-image.tsx → /opengraph-image
• /app/test/page.tsx → /test
This allows the OG to be dynamically created (or updated). If you want a static file (with extension), you would do:
• /app/opengraph-image.png → /opengraph-image.png