Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
leerob
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
27 ms
·
361.
▲
by
leerob
4y ago
https://twitter.com/sebmarkbage/status/1528858510754459648
362.
▲
by
leerob
4y ago
Thank you! We've added documentation[1] on the current layouts solutions, which is similar to Adam's post. It's a good workaround, but I'm very excited for improving the developer experience here. [1]: https://
363.
▲
by
leerob
4y ago
Open to any feedback you have – we've already started work on the implementation, and will adjust as necessary based on the RFC discussion.
364.
▲
by
leerob
4y ago
Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.
365.
▲
by
leerob
4y ago
If SSR + caching is already working well for you, you might not need ISR. And it likely also depends on the type of application you’re building. For example, if you need user auth on every request, generating static assets probably won’t wo
366.
▲
by
leerob
4y ago
Many people are still using Next.js with WordPress, but they’re using it “headless”. The difference here is that static assets can be served globally (versus a monolithic WP single region server) and cache purges can happen globally in abou
367.
▲
by
leerob
4y ago
You can customize which region you want your functions to run in that handle server-rendering. Currently running multi-region functions (lambdas) requires an enterprise plan, but using Edge Functions, they can be multi-region or global if y
368.
▲
by
leerob
4y ago
Vercel has built-in regional caching. When you use on-demand ISR to programatically invalidate the cache, purges propagate globally in about 300ms. https://on-demand-isr.vercel.app/
369.
▲
by
leerob
4y ago
Hey, Lee from Vercel. How many pages were you trying to build when you hit the 45 minute limit? We’ve recently revamped our build and deploy infrastructure, which should help builds complete faster with many static pages. https://
370.
▲
by
leerob
4y ago
By default, static pages and assets on Vercel are deployed to every region in our Edge Network. Happy to answer any other questions about Vercel!
371.
▲
by
leerob
4y ago
Thank you! Appreciate the kind words. If there's anything we can improve, you can always reach me at lee at vercel dot com.
372.
▲
by
leerob
4y ago
I've been using Axiom on my site (leerob.io) for a few months now, really enjoyed it. It was far easier to set up than other observability tools and I even created some custom alerts.
373.
▲
by
leerob
4y ago
What are you looking to do on server start and shutdown?
374.
▲
by
leerob
4y ago
Some good suggestions here! https://nextjs.org/docs/going-to-production
375.
▲
by
leerob
4y ago
Hey, Lee from Vercel. I lead the Next.js community. We do encourage folks to use monoliths, if they'd like! That's partially why we believe in Turborepo so much (happy to share more on that if you'd like). Are there specific
376.
▲
by
leerob
4y ago
Hey, Lee from Vercel – I lead the Next.js community and am focused on making sure Next.js works great self-hosted (e.g. Node.js server, Docker app, etc) with support for all features. I've written docs[1] about it as well as made video
377.
▲
by
leerob
4y ago
> The main problem with rendering in both the client and server environments using the same code is that you need to fetch data in two different places. `getStaticProps` and `getServerSideProps` _only_ run on the server – it's possi
378.
▲
by
leerob
4y ago
Lee from Vercel (Next.js) – could you share some of things you feel you're working against the framework for? Open to any feedback. It's indeed a tricky balance between having lots of options vs. having the one "paved road&qu
379.
▲
by
leerob
4y ago
Glad you're enjoying using Next.js! We're working on an improved routing system as well, stay tuned :)
380.
▲
by
leerob
5y ago
You can self-host your remote cache if you'd like. For example, with GitHub Actions. We're working on better docs for this. https://turborepo.org/docs/features/remote-caching#custom-re...
381.
▲
by
leerob
5y ago
Hey! Yeah, we recommend using pnpm. Excellent tool. You might be interested in this feature from 1.2: "You can enable Turborepo to sign artifacts with a secret key before uploading them to the Remote Cache. Turborepo uses HMAC-SHA256 s
382.
▲
by
leerob
5y ago
If I'm hearing you correctly, your pain is having to configure ESLint manually, correct? Are you wishing for ESLint to be included in Turborepo natively? My opinion is that giving folks the option on their linter of choice is a good th
383.
▲
by
leerob
5y ago
From what I've seen, Nix[1] is exciting and has some innovative ideas, some of which we're learning from with Turborepo. I believe Replit uses it[2]. [1]: https://nixos.org/ [2]: https://docs.replit.com
384.
▲
by
leerob
5y ago
We're discussing more native support for other languages. It would likely be a commitment to a small subset of popular languages (e.g. Rust, Go, C++, Python) while still maintaining our goal of nearly zero configuration. https:/&
385.
▲
by
leerob
5y ago
While we're initially focused on JavaScript and TypeScript codebases, you can already use Turborepo with any language as long as you define tasks through `package.json` scripts and use npm/pnpm/yarn workspaces. Turborepo is w
386.
▲
by
leerob
5y ago
Hey! In case you missed it, Turborepo launched 1.0 a few months ago[1]. This 1.2 release is important, as it includes --filter[2] (highly requested). You're able to much more easily filter tasks, instead of the previous --scope, --incl
387.
▲
Turborepo 1.2: High-performance build system for monorepos
(turborepo.org)
157 points
by
leerob
5y ago
|
54 comments
388.
▲
by
leerob
5y ago
We recently started sponsoring pnpm[1] as well as adding zero-config support for deployments and caching. I think pnpm is an incredible tool. Excited to see it grow further. [1]: https://vercel.com/changelog/projects-us
389.
▲
by
leerob
5y ago
> Next pushes towards serverless functions and API routes that I didn't really enjoy using for more than just a trivial endpoint. By default (through `next start`) Next.js uses a Node.js server. You don't need to use Next.js se
390.
▲
Show HN: Live Video Starter Kit (Open Source Hopin)
(demo.vercel.events)
15 points
by
leerob
5y ago
|
0 comments
More ›