leerob

16 ms·

151.
by leerob 3y ago
Edit: Nevermind, wrong thread. Vercel does honor DCMA, of course, though.
152.
by leerob 3y ago
The next sentence in the posts says that I work at Vercel. Grasping for straws.
153.
by leerob 3y ago
> I don't see an explicit disclaimer here In the post: > I'm Lee. I work on Next.js. On the homepage: > I lead the community for Next.js
154.
by leerob 3y ago
Yeah, a large number of Next.js apps use the static export functionality and host on S3: https://nextjs.org/docs/app/building-your-application/deploy...
155.
by leerob 3y ago
There's a lot of misunderstanding of what "frontend" and "backend" are: https://www.industrialempathy.com/posts/frontend-backend/
156.
by leerob 3y ago
Sorry about your experience. > Whatever it sends to the browser is enough to eventually freeze the entire browser tab if you have the dev tools open. Is this with a fresh Next.js project of after you've added user code? If the forme
157.
by leerob 3y ago
This should be supported: https://github.com/vercel/next.js/discussions/44628#discussi...
158.
by leerob 3y ago
Middleware works when self hosting. It's runtime is a subset of Node.js, since it's potentially running in front of every request in your application. We're still evaluating options here: https://github.com/ve
159.
by leerob 3y ago
https://leerob.io/blog/using-nextjs
160.
Why I'm Using Next.js(leerob.io)
7 points by leerob 3y ago|0 comments
161.
by leerob 3y ago
I'll be posting a full response to this, which I think you'll find very interesting (from the opposite point of view). Stay tuned.
162.
by leerob 3y ago
I'm sorry that we haven't been able to respond fast enough. Hundreds of issues are opened every month, and the rate is increasing. We're working hard to try and triage as best as possible and hopefully hiring more folks to he
163.
by leerob 3y ago
You can continue to use the Pages Router until there's broader ecosystem support for the larger React changes like Server Components. You don't need to use a library to handle localization or i18n. i18n was part of the framework i
164.
by leerob 3y ago
I plan to look into the issues that you mentioned in your previous comment. I'm sorry that I can't get to it today, but I will follow up on those issues.
165.
by leerob 3y ago
Extremely appreciate this detailed response.
166.
by leerob 3y ago
> Next.js is still the only actual implementation of RSC Here's one https://github.com/dai-shi/waku . Also, Redwood is "all in on Server Components" https://tom.preston-werner.com/2023&
167.
by leerob 3y ago
Remix is like the Next.js Pages Router + a helper similar to Server Actions. It does not support Server Components (what the App Router uses) and they're exploring using RSC in the future. So definitely different. For example, `getServ
168.
by leerob 3y ago
Can you share a bit more about what you're trying to build? Is there a specific library you're wanting to have in Middleware versus putting it in a layout or page (which does support all of Node.js)?
169.
by leerob 3y ago
Which issue? There are certain issues that are non-issues in the App Router, and simply not possible in the Pages Router without a significant amount of foundational changes. Which, those changes are, the App Router. That’s why we’ve been f
170.
by leerob 3y ago
Can you be more specific on the issue? It’s possible there’s a reason why App Router was recommended in this case.
171.
by leerob 3y ago
Community Notes: Vercel did not acquire Gatsby.
172.
by leerob 3y ago
The reason we suggest upgrading is because it’s extremely common that issues are already fixed or they cannot reproduce when we ask them to upgrade. It helps with issue triage so we can properly prioritize and fix issues. If you can link th
173.
by leerob 3y ago
next/image optimization works by default when self-hosting. You can optionally use basically any image service you want through a “loader file”. https://nextjs.org/docs/app/api-reference/components/i
174.
by leerob 3y ago
I’m sorry you haven’t had a good experience. And if you more specifics if anyone on the Next team replied to you in that way, please let me know. I’ll be the first to say the launch of the App Router could have been smoother. Definitely not
175.
by leerob 3y ago
Yeah, best part for me is end to end type safety across the server and client. tRPC really led the way here.
176.
by leerob 3y ago
You can set cookies in Server Actions or Route Handlers. https://nextjs.org/docs/app#how-can-i-set-cookies
177.
by leerob 3y ago
Correct. Same price and limits. It’s just making integrating it into Vercel. So you can get Postgres/Redis/object storage and more with your frontend, in one bill.
178.
by leerob 3y ago
Which part of this release do you find more difficult? For applications that need those dynamic constraints, like auth and personalization, we’re working to make this even easier starting this this version. This version also includes stabil
179.
by leerob 3y ago
Correct, the Pages Router is very much still supported with new improvements being made. The performance improvements in this post apply there. The same APIs and features included in Next.js 1.0 still work today with the Pages Router.
180.
by leerob 3y ago
Yeah, it’s primarily for React right now, but it does generate HTML as well

More ›