Add migration guide from vanilla React

[leerob]

Feature request

As a user of [x] framework/language, I'd love to see an easy path towards migrating to Next.js

Describe the solution you'd like

Documentation around common providers and how exactly you can switch to Next.js from them.

Additional context

Let's start with a few of the most popular and see what others in the community would get value from.

• Create React App (Add migration guide from Create React App #17454)
• Gatsby (Add migration guide from Gatsby #17453)
• Vanilla React

[Maxgit3]

I would be interested in helping with a migration guide for Vanilla React. Would it be a comparison of building an app in React vs Next js or a comparison of the features? I have been working with React and Next js. I am new to open source contribution. I am willing to help anyway I can.

[leerob]

Hey @Maxgit3! Thanks for offering to help. I just removed "good first issue" because I don't want to lead you down the wrong path. The scope of what I have in mind for this will involve advanced React/Next knowledge.

• If I've ejected Create React App (or have hand-rolled my own React setup with Webpack / Babel), how can I understand the differences in my custom setup versus what Next provides by default? Link to docs for Webpack and Babel overrides for Next.
• Try to find the most common reasons people eject Create React App and what those configurations are. Then, if possible, show how they can be accomplished with Next.
• There's probably an index.html file that needs to be converted into the Next way of doing things
• Link to the "Migrating from Create React App" documentation when it's finished to include how to transform using React Router to Next's file-system based routing
• If you have custom file loaders set up for CSS/Sass/assets, explain how that's all built into Next and show how to convert.
• Talk about new features that are added by default in Next that you can probably remove if you had them added manually (optional chaining, polyfilling fetch, etc)
• If you had custom code splitting, you can remove that
• Probably wouldn't hurt to mention how env variables are handled with next (specifically thinking how you prefix with NEXT_PUBLIC_ to have it exposed client side)

[Maxgit3]

Thanks for the update

[gfortaine]

Gradual Migration Strategies For Next.js

[samcx]

Moving this to discussions since this is a feature request!