History

Shu Uesugi 6804039e94 Make example READMEs more consistent (#10124 ) * npx create → npm init * Fix inconsistent instructions * Update amp-first * Update with-graphql-react * with-firebase-cloud-messaging * Update with-higher-order-component * change create-next-app url * Update create-next-app instruction * Update instructions to use npm instead of npx * Move "the idea behind the example" to top * Rename * Rename * Update contributing.md with a README template		2020-01-16 23:23:56 +01:00
..
components	Improve linting rules to catch more errors (#9374 )	2019-11-10 19:24:53 -08:00
pages	Update about.js	2016-12-20 12:37:38 -08:00
package.json	Test updater script on examples folder (#5993 )	2019-01-05 12:19:27 +01:00
README.md	Make example READMEs more consistent (#10124 )	2020-01-16 23:23:56 +01:00

Example app using shared modules

This example features:

An app with two pages which has a common Counter component
That Counter component maintain the counter inside its module. This is used primarily to illustrate that modules get initialized once and their state variables persist in runtime

Deploy your own

Deploy the example using ZEIT Now:

Execute create-next-app with npm or Yarn to bootstrap the example:

npm init next-app --example shared-modules shared-modules-app
# or
yarn create next-app --example shared-modules shared-modules-app

Download the example:

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

Install it and run:

npm install
npm run dev
# or
yarn
yarn dev

Deploy it to the cloud with now (download):

now