Yesterday's Top Poster

Industry News

One of the main benefits of building with Next.js is the ease of leveraging APIs and components to quickly integrate with best-of-breed, backend technology. Today released our new notification system as a public beta, made possible with the help of our integration partner Knock, their powerful API, and robust component library. This post will cover how we chose and implemented Knock for our notification center, and how you can use Knock to build notifications into your own application. Read more Continue reading...
Last month, Vercel had the privilege of sponsoring AfroTech Conference 2022—the place for all things Black in tech and Web3. Our team was joined by the likes of Google, Meta, and Tesla in the expo hall—so we knew that we needed to find ways to stand out, engage with the community, and attract top talent. This was our approach. Read more Continue reading...
When teams can easily share and comment on work in progress, big ideas happen faster. Today, we’re bringing that capability to all teams on Vercel with the ability to comment on Preview Deployments. Now, collaborating on websites and applications is as seamless as working on a Google Doc or Figma file. Preview Deployments provide a shareable, production-quality URL for your website, while commenting enables real-time feedback in the context of the product you’re building. The result: dramatically faster iteration cycles and higher quality input from developers, designers, product managers, stakeholders, and more. Read more Continue reading...
Next.js lets developers iterate on their projects faster—but we want to iterate on Next.js itself faster, too. This year, Next.js surpassed 4 million npm downloads for the first time. With over 2,400+ contributors, the core team here at Vercel must craft a developer experience to keep up with such a vast community to develop, test, build, and publish Next.js. Next.js had another first this year: introducing Rust to its core. While adding Rust brings greatly improved performance for developers using Next.js, the tradeoff was an increase in CI time to publish new releases due to the prolonged process of building Rust binaries. Until implementing Turborepo Remote Caching dropped publish times by 80%. Read more Continue reading...
We held our biggest ever Next.js Conference on October 25, 2022 with over 110,000 registered developers, 55,000 online attendees, and hundreds attending in person in San Fransisco. We had photographers on site to capture the experience and we wanted to share the photos they took with the community. Instead of just sharing photos with a Google Drive link, we thought it’d be good idea to showcase these 350+ amazing photos in an image gallery that was fast, functional, and beautiful. We ended up building our own and open sourcing the code, making it easy for anyone to build their own image gallery. In this blog post, we’re going to share the techniques we used to build a performant image gallery site that can handle hundreds of large...
We believe the Web is an open platform for everyone, and strive to make Vercel accessible and available no matter how you choose to build for the Web. Today we’re introducing the Build Output API, a file-system-based specification that allows any framework to build for Vercel and take advantage of Vercel’s infrastructure building blocks like Edge Functions, Edge Middleware, Incremental Static Regeneration (ISR), Image Optimization, and more. Read more Continue reading...
Have you ever wondered what it takes to build your own web framework that also deploys to edge and serverless infrastructure? What features does a modern framework need to support, and how can we ensure that these features allow us to build a scalable, performant web application? Read more Continue reading...
Hashnode, a blogging platform for the developer community built using Next.js, was born from the fundamental idea that developers should own the content they publish. A key component of that ownership is publishing articles on a custom domain—a feature the Hashnode team spent hours monitoring and maintaining themselves. That’s when they turned to Vercel. Read more Continue reading...
We want to keep the Vercel Dashboard fast for every customer, especially as we add and improve features. Aiming to lift our Core Web Vitals, our Engineering Team took the Lighthouse score for our Dashboard from 51 to 94. We were able to confirm that our improvements had a real impact on our users over time using Vercel Analytics, noting that our Vercel Analytics scores went from 90 to 95 on average (desktop). Let’s review the techniques and strategies we used so you can make a data-driven impact on your application. Read more Continue reading...
Updated January 18, 2024. Interaction to Next Paint (INP) measures your site’s responsiveness to user interactions on the page. The faster your page responds to user input, the better. On March 12, 2024, INP will officially replace First Input Delay (FID) as the third Core Web Vital. This post will help you understand why INP is a better way to measure responsiveness than FID and how React and Next.js can improve INP. You'll be prepared for updates to Core Web Vitals, which impact search rankings, as INP moves from experimental to stable. We have a separate post on understanding the metric and further optimization of INP. Read more Continue reading...
We've been working to make it easier for every developer to build at the Edge, without complicated setup or changes to their workflow. Now, with support for WebAssembly in Vercel Edge Functions, we've made it possible to compile and run Vercel Edge Functions with languages like Rust, Go, C, and more. Read more Continue reading...
Running A/B tests is hard. We all know how important it is for our business–it helps us understand how users are interacting with our products in the real world. However, a lot of the A/B testing solutions are done on the client side, which introduces layout shift as variants are dynamically injected after the initial page load. This negatively impacts your websites performance and creates a subpar user experience. To get the best of both worlds, we built Edge Middleware: code that runs before serving requests from the edge cache. This enables developers to perform rewrites at the edge to show different variants of the same page to different users. Today, we'll take a look at a real-world example of how we used Edge Middleware to...
Back
Top