Repository navigation
Migrate to Next.js #25
Description
There are two key advantages for us that Next.js has over CRA:
- Built in server side rendering
- Better optimization
Due to them I think it makes sense to run an experiment and see if we can build our framework on top of Next.js that covers our needs.
Progress
-
dreact app-
start(plusbuild)- Delegates to next.js
- Adds Pug
- Supports our file structure
- more
- Supporting polyfills
-
-
dreact env-sync -
dreact test -
dreact lint-
js -
styles
-
-
dreact book-
start(plusbuild)- more
-
Useful new features
- Make sure
.gitignorecontains necessary files - Handle Routes inside dreact (this is important because Nextjs requires some efforts to maintain routes and in most cases will ask you to use third-party solutions such as next-routes)
Reacted by Radion Chernyakov
Reacted by Radion Chernyakov
Activity
ezhlobo commentedon Feb 11, 2020
Next.js relies on react and react-dom packages in Node scripts. It's possible to mock them and point to necessary files, however it seems like they are run in
jest-workerand it can be quite tricky to achieve and override the references.radion-chernyakov commentedon Feb 14, 2020
@ezhlobo hey, do you need help with it?
ezhlobo commentedon Feb 17, 2020
@nixololo my main issue is that I don't know how to hide
nextdependency behind react.Ideally I don't want to expose what is used under the hood and provide own framework, so it's important.
ezhlobo commentedon Feb 17, 2020
I attached working branch. I successfully ran nextjs behind
dreact app. However I stuck on a task when I need to sync server side router and local router.I want to get a router that can be transformed into something that gives the possibility to implement steps mentioned above.
Also it seems like we need to invent new commands. I'm thinking about something like this:
dreact app devdreact app ssr-builddreact app ssrdreact app static-builddreact app dynamic-buildPS. Even though my main focus is to implement local development and dynamic app, I need to be careful and pay attention on all the constraints we have from SSR and Static app.
vladoganov commentedon Feb 28, 2020
@ezhlobo when you're talking about "Dynamic app" do you mean implementing of client side routing?
Like we receive an html with one script tag, and then receive a bundle of the whole app. Then we use routing to navigate to other routes directly in a browser
ezhlobo commentedon Mar 2, 2020
@viscoze yes, "Dynamic apps" are those that understand what to output in runtime, not on server or via pre-building all pages.