1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
next.js/examples/with-freactal
2017-12-06 18:12:42 -08:00
..
components Example: with Freactal (#2955) 2017-09-17 23:16:19 +02:00
pages Example: with Freactal (#2955) 2017-09-17 23:16:19 +02:00
githubApi.js Dropped isomorphic-fetch in examples in favor of isomorphic-unfetch. (#3230) 2017-11-04 15:05:16 +01:00
package.json Dropped isomorphic-fetch in examples in favor of isomorphic-unfetch. (#3230) 2017-11-04 15:05:16 +01:00
provideState.js Example: with Freactal (#2955) 2017-09-17 23:16:19 +02:00
README.md Use canary for all example downloads (#3411) 2017-12-06 18:12:42 -08:00

Deploy to now

Freactal example

How to use

Using create-next-app

Download create-next-app to bootstrap the example:

npm i -g create-next-app
create-next-app --example with-freactal with-freactal-app

Download manually

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-freactal
cd with-freactal

Install it and run:

npm install
npm run dev

Deploy it to the cloud with now (download)

now

The idea behind the example

When it comes to state management of the React webapp, Redux is the most popular solution. However it brings lots of boilerplate code and fiddling aroud multiple files when tracing even simplest state change.

Freactal is a state management library that put this disadvantages away. With very little setup code your components' props are enhanced with two key ingredients: state and effects. Another benefit of Freactal is that you don't need to place state at some special place (global store). You can even have multiple state roots and compose them together - just like your components (this is true also for effects).

example app

In this example the index page renders list of public repos on Github for selected username. It fetches list of repos from public gihub api. First page of this list is rendered by SSR. serverState is then hydrated into the Index page. Button at the end of the list allows to load next page of repos list from the API on the client.

For simplicity the last page is not handled.