Next.js adding to project

[happylolonly]

Next.js is good framework we may add, here are pros and cons to see:

Pros:

• code splitting
• static html prebuild
• seo
• good folder structure (by pages)
• configs (like webback) hidden
• typescript
• popularity (for new devs)

Cons:

• large refactoring
• may be problems for large project?

Something more?

[mastercyb]

I am vouching for pages feature :-)
To make a decision it is good to understand what size of refactoring we are talking about?
anyway we have to migrate code for typescript... Is it possible to split refactoring to smaller pieces?

[happylolonly]

For refactoring at least change folder structure, and replace react-router things with next ones.
If we decided go without server, we can disable SSR, it will make things easier.

Not sure about small steps, seems whole refactoring should be done...
I can try to start from MVP, and we will see how it is going, what problems.

Also need to decide about this, no idea for now. similar for IPFS

[dasein108]

By my opinion we should achieve 2 things:

1. Pre-generate static folders for relative structure like /portal, /robot, /warp, - than can be recognized by react as route, not root.
2. Get rid of bootloader, instead of that show page with hydration in the background.

[dasein108]

Just found interesting thing
https://ogzhanolguncu.com/blog/react-ssr-ssg-from-scratch
Need to do research this way too

[happylolonly]

https://www.gatsbyjs.org is another popular framework for react, but looks it fit less