History

Nick Babcock 5629223407 Update examples to use React 17 (#26133 ) [With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples need to be updated, so the following snippet updated all the examples to a compatible react version. ```bash cd examples/ fd -g 'package.json' \| xargs sed -r -i 's/"react": "."/"react": "^17.0.2"/ fd -g 'package.json' \| xargs sed -r -i 's/"react-dom": "."/"react-dom": "^17.0.2"/' # exclude experimental react version git checkout with-reason-relay/package.json ```		2021-06-16 16:43:26 +00:00
..
pages	Add example for proxying upstream with custom routes (#14374 )	2020-06-22 00:44:04 +00:00
.gitignore	Added .gitignore to examples that are deployed to vercel (#15127 )	2020-07-16 10:52:23 -04:00
next.config.js	Update custom-routes-proxying to use fallback rewrites (#23610 )	2021-04-01 16:48:49 +00:00
package.json	Update examples to use React 17 (#26133 )	2021-06-16 16:43:26 +00:00
README.md	docs: add 'Open in StackBlitz' buttons to various examples (#25853 )	2021-06-08 20:45:02 +00:00

README.md

Custom Routes Proxying Example

This example shows the most basic example using Next.js' new custom routes feature to proxy requests to an upstream server. We have 3 pages: pages/index.js, pages/about.js, and pages/hello/[slug].js. All of these pages will be matched against Next.js and any other path will be proxied to the upstream server.

This approach is very helpful when you are trying to incrementally migrate your application to Next.js but still need to fallback to an existing application. You can add pages to your Next.js application one-by-one and then for non-migrated pages Next.js can proxy to the existing application until they are able to be migrated.

Preview

Preview the example live on StackBlitz:

How to use

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

npx create-next-app --example custom-routes-proxying custom-routes-proxying-app
# or
yarn create next-app --example custom-routes-proxying custom-routes-proxying-app

Step 4. Run Next.js in development mode

npm install
npm run dev

# or

yarn install
yarn dev

Test out visiting one of the Next.js pages https://localhost:3000/ and then a non-Next.js page like http://localhost:3000/legacy-first.html or http://localhost:3000/another-legacy.html which will be proxied to the upstream server since it doesn't match any pages/assets in Next.js.

Deploy it to the cloud with Vercel (Documentation). Note: to deploy this example you will need to configure an existing upstream server.