e8c71ed2ea
### What? This adds to the docs a guide for migrating a Vite application to Next.js. It also contains a section that lists the reasons why one would want to switch from Vite to Next.js. ### Why? This guide is helpful for developers that want to switch to Next.js but don't know how difficult that would be and how to do it. The "Why?" list is also helpful to developers who haven't yet been convinced to switch or need help formulating the reasons to switch to decision-makers. This guide was [first published on the Inngest blog](https://www.inngest.com/blog/migrating-from-vite-to-nextjs). To our own surprise, we were able to [migrate from Vite to Next.js](https://github.com/inngest/inngest/pull/479) our [Dev Server app](https://github.com/inngest/inngest/tree/main#the-inngest-dev-server) in less than a day, which motivated us to share our learnings with the community. ### How? The guide aims to have the minimum number of steps to get a working Next.js application so that the reader can then adopt Next.js features incrementally. This means the migration of the router isn't part of this guide. However, this would be something valuable to document at a later time so that the reader can also learn how to migrate to the App Router and get all the Next.js benefits. |
||
|---|---|---|
| .. | ||
| 01-getting-started | ||
| 02-app | ||
| 03-pages | ||
| 04-architecture | ||
| 05-community | ||
| index.mdx | ||