We provide a Jest Example to show how to test components in your Next.js applications. Regarding testing full-pages, this is best accomplished by booting your Next.js application via next start and running tests against your application—you shouldn't try stubbing out server functionality. Here's an example of how we test Next.js apps in our monorepo (with Jest): https://github.com/zeit/next.js/blob/canary/test/integration/hydration/test/index.test.js The above test boots Next.js via next start , then runs webdriver ( puppeteer would work too) to verify the application is working as expected.

I'm currently most excited about the Incremental Static Generation RFC , particularly with its fallback behavior. Besides the feature giving you a fully incrementally generated static site (powered by any source, including headless CMS or direct database calls), the fallback behavior helps this scale to millions of pages. With the fallback: true behavior, you can tell Next.js to only statically generate your most popular product pages for example. Then, at runtime, Next.js will lazily statically generate the remaining product pages when the first request comes in—that lazily generated page will then be used for successive requests. This allows you to keep build times low, and still allows for incremental rebuilds once deployed. I'm also excited about the new Environment Variables support , which should greatly simplify env handling in Next.js apps. If you want to know how direct database work in Next.js' SSG support, checkout this cool tool we built to see how Next.js bundles code for the client-side .

Hello! First off, I'd like to clarify: Next.js is free, open-source software. All of its features are available without using ZEIT as your deployment solution (however, ZEIT is the best place to host Next.js applications!). Regarding the new pricing for our ZEIT Now platform, this decision was rooted in two major things: We see the major value we deliver as best in class developer experience and developer productivity, not (just) hosting. This pricing aligns costs with where we see our value. We’re all about making life easier for front-end developers: this means eliminating the need to worry about unexpected bills due to traffic spikes or application bugs—that isn't productive. You can learn more about these changes in our blog post .

Echoing Tim Neutkens , the entire Next.js team (and ZEIT team) is remote, so it has been business as usual! ZEIT (the company behind Next.js) has been really supportive during quarantine and has started offering bi-weekly guided meditation and weekly all-hands meetings to socialize (no work talk!). These actions have really helped keep productivity and motivation up for me personally.

Hello! Our recently announced RFC for Incremental Static Generation in Next.js covers this exact use case. This RFC allows you to specify an interval on which the page is rebuilt, and is paused when no users are visiting the page (to reduce API calls to your CMS). This is an eager approach (compared to an event-driven approach) which we argue is a better foundation to start from. We'll absolutely be looking at allowing you to rebuild pages on-demand via a webhook , but we think of this more as an optimization for the future.