The intention of this repo is to develop the initial setup for the reactools library and to showcase a working prototype of the concept.
Currently, the react app and the express server are not integrated properly. Running npm run server or yarn server
will build the react app and start the express server.
$ yarn server
Then open localhost:3000 and click on the BEGIN button. This will
- Trigger a fetch call
- Bring some data from the backend
- Update the fetch status (first "in-progress", and then "success")
- Set the data to the redux store
- Do a redirection to /someNewPage
All without any code(after the initial setup is done). Only need to set some metadata. Since there is no code, no need to test anything. No need to mock anything.
The expected outcomes of this project are 5 fold,
- Implement a scalable data fetching approach upon redux with all the goodies
- All in one solution for SSR, Code-splitting, React Router and Redux
- Make the SSR middleware in a customizable/modular manner
- Hide webpack to share configs across repos
- Encourage Domain Driven Design for the frontend
While trying to achieve the above goal,
- Don't force a lock in: users can opt in/out anytime, piece by piece
- Should support Create React App out of the box
- Agnostic about the backend (Planning to support express and koa initially. And even they are optional for the frontend library to work)
- Support connected react router
- Integrate the frontend app with the express server (build setup with hot reloading and stuff)
- Strip out reactools and reactools-express as npm packages
- Write tests for the reactools library modules
- Write end user documentation (specially for the metadata format)
- Expose a test method to validate users metadata using Json Schema