arahansen / with-zones

next.js repro of zones dynamic routing issue

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Using multiple zones

With Next.js you can use multiple apps as a single app using it's multi-zones feature. This is an example showing how to use it.

  • All pages should be unique across zones. For example, the home app should not have a pages/blog/index.js page.
  • The blog app sets assetPrefix so that generated JS bundles are within the /blog subfolder.
    • To also support the plain next dev scenario, assetPrefix is set dynamically based on the BUILDING_FOR_NOW environment variable, see now.json and blog/next.config.js.
    • Images and other /static assets have to be prefixed manually, e.g., <img src={`${process.env.ASSET_PREFIX}/static/image.png`} />, see blog/pages/blog/index.js.

Deploy your own

Deploy the example using Vercel:

Deploy with Vercel

How to use

Using create-next-app

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

npm init next-app --example with-zones with-zones-app
# or
yarn create next-app --example with-zones with-zones-app

Download manually

Download the example:

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

For every app, install dependencies and run the dev server:

npm install
npm run dev
# or
yarn
yarn dev

The home app will start in the default port (http://localhost:3000), and blog will start on http://localhost:4000.

Deploy it to the cloud with Vercel (Documentation).

About

next.js repro of zones dynamic routing issue


Languages

Language:JavaScript 100.0%