leerob

19 ms·

241.
by leerob 4y ago
If you'd like to see the full details, I posted an update here ( https://news.ycombinator.com/item?id=35508529 ).
242.
by leerob 4y ago
[Lee from Vercel] Max reached out to me today (Sunday) after this experience, and I worked with him this evening get to a resolution for his site on the Vercel free tier. I'm really sorry we weren't able to get to a resolution fas
243.
Next.js 13.3(nextjs.org)
9 points by leerob 4y ago|1 comments
244.
Vercel Edge Config: Global, low-latency storage(vercel.com)
1 points by leerob 4y ago|0 comments
245.
by leerob 4y ago
Shouldn't be (I'm on the team). All Next.js features work out of the box when using `next start`, either when deployed self-hosted (like a Node.js server or a Dockerfile), or when deploying to a platform like Vercel. We have docum
246.
by leerob 4y ago
https://news.ycombinator.com/item?id=35282577
247.
by leerob 4y ago
Thank you, glad to hear the docs worked well! Let me know if you have any feedback.
248.
by leerob 4y ago
The core of Next.js is static/CSR. There's a one line configuration option to set your application in this mode—if you don't want to use the server, you don't have to.
249.
by leerob 4y ago
ELI5: Helps you make websites. Next level (no pun intended): Makes working with React easy. And another: Next.js provides tools for web developers (rendering UI components, fetching data from APIs, optimizing and displaying images and fonts
250.
by leerob 4y ago
You can still do client-only routing (it was mentioned in the tweet linked above). It can be deployed anywhere that takes HTML/CSS/JS files.
251.
by leerob 4y ago
Yeah, of course. It's a set of HTML/CSS/JS files, so you can do really anything with it!
252.
by leerob 4y ago
Folks have been using Next.js this way for many years, and it has been documented, but not as clearly as we could have been. So the answer is, yes! There are no plans to ever deprecate client-side usage. We believe it's important to
253.
by leerob 4y ago
(I'm on the Next.js team) Something we haven't done a great job of, so far, is talking about how you can use Next.js for SPAs or client-only React sites. You can start with basic HTML/CSS/JS, deploy and host anywhere, an
254.
Remix Without Limits: Streaming SSR with Vercel Edge Functions(vercel.com)
7 points by leerob 4y ago|0 comments
255.
by leerob 4y ago
We've made quite a few improvements to the static export with the new App Router, including support Server Components, Route Handlers, i18n routes, and more. Definitely still being invested in. My comment about documentation debt is th
256.
by leerob 4y ago
You can use Next.js in SPA mode – you don't have to use SSR. Here are the current docs ( https://nextjs.org/docs/advanced-features/static-html-export ) and we're working on an improved version for the new
257.
by leerob 4y ago
New docs are a work-in-progress here: https://beta.nextjs.org/docs/configuring/static-export
258.
by leerob 4y ago
There are similarities to PHP – and I think that's a great thing! I like to think of Next.js as the best parts of PHP / Rails with the powerful UI engine of React. Especially with the new App Router, where you can fetch code insid
259.
by leerob 4y ago
If you roll your own with a bundler, you will also need to integrate a router. Next.js is providing a routing layer for you. If you want to stick with a static/SPA the entire time, that's fine. You don't have to use SSR unles
260.
by leerob 4y ago
I'd say this is documentation organization "debt" – there's a bunch of "advanced" features that aren't that advanced. We're aware and fixing with the new docs -> https://beta.nextjs.org&
261.
by leerob 4y ago
Your understanding is correct – Next.js can do static sites, SPAs, SSR – all of them. We (just today) updated the Next.js docs linked based on feedback around this to make it more clear. Hopefully this helps, let me know if you have other f
262.
by leerob 4y ago
One of the key design choices of Next.js was to enable granularity on the runtime (Node.js or Edge[1]) and the rendering method (static or dynamic[2]) on a per-route basis. If you want a full SSR site, that's okay. If you want a full s
263.
by leerob 4y ago
IMO, this post doesn't discuss the tradeoff of removing the build step. What a “build” is has been obfuscated. When you deploy an app, you now need to convert TypeScript into JS, and then the JS needs to be turned into an optimal repre
264.
by leerob 4y ago
Hey! Thanks for sharing. Author of the post here, happy to answer questions.
265.
Next.js 13.2: Statically typed links, Turbopack improvements, Next.js Cache(nextjs.org)
10 points by leerob 4y ago|0 comments
266.
Vercel Cron Jobs(vercel.com)
8 points by leerob 4y ago|0 comments
267.
by leerob 4y ago
I’m always looking to see how we can improve things. Appreciate your feedback! Let me know if you have any other questions in the future.
268.
by leerob 4y ago
Wanted to clarify some of the points raised about Next.js: > I’ve been using Next.js for a while and hosting the apps built with it on AWS with custom express servers. One day I’ve noticed that my servers are getting red-hot while doing
269.
by leerob 4y ago
Hey, Lee from Vercel here. This happened on January 30th, and our support team and various folks reached out to the author to help get things resolved. We unblocked the free hobby account after helping them get moved to a paid plan on the s
270.
by leerob 4y ago
Turbopack is currently only supported for the local dev server (`next dev`) but we plan to solve `next build` after.

More ›