5dd4999b64
Strategized with @balazsorban44 to open one larger PR, with changes to individual examples as separate commits. For each example, I researched how multiple realworld codebases use the featured technology with TypeScript, to thoughtfully convert them by hand - nothing automated whatsoever. ## Documentation / Examples - [X] Make sure the linting passes by running `pnpm lint` - [X] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
36 lines
754 B
JavaScript
36 lines
754 B
JavaScript
// @ts-check
|
|
|
|
/**
|
|
* @type {import('next').NextConfig}
|
|
**/
|
|
const nextConfig = {
|
|
async rewrites() {
|
|
return [
|
|
{
|
|
source: '/team',
|
|
destination: '/about',
|
|
},
|
|
{
|
|
source: '/about-us',
|
|
destination: '/about',
|
|
},
|
|
// Path Matching - will match `/post/a` but not `/post/a/b`
|
|
{
|
|
source: '/post/:slug',
|
|
destination: '/news/:slug',
|
|
},
|
|
// Wildcard Path Matching - will match `/blog/a` and `/blog/a/b`
|
|
{
|
|
source: '/blog/:slug*',
|
|
destination: '/news/:slug*',
|
|
},
|
|
// Rewriting to an external URL
|
|
{
|
|
source: '/docs/:slug',
|
|
destination: 'http://example.com/docs/:slug',
|
|
},
|
|
]
|
|
},
|
|
}
|
|
|
|
module.exports = nextConfig
|