JJ Kasper c2d0887b94 [next][routing-utils] Add missing matcher support (#8874) ...

### Related Issues

This adds handling to ensure we pass through the `missing` route field
correctly for custom routes and middleware matchers. Tests are also
added in the complimentary Next.js PR for this, example deployment can
be seen here
https://vtest314-e2e-tests-jj4-vtest314-next-e2e-tests.vercel.app/

x-ref: [slack
thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1667935428788529?thread_ts=1667850697.542269&cid=C03S8ED1DKM)
x-ref: https://github.com/vercel/next.js/pull/42660

### 📋 Checklist

<!--
  Please keep your PR as a Draft until the checklist is complete
-->

#### Tests

- [ ] The code changed/added as part of this PR has been covered with
tests
- [ ] All tests pass locally with `yarn test-unit`

#### Code Review

- [ ] This PR has a concise title and thorough description useful to a
reviewer
- [ ] Issue from task tracker has a link to this PR

2022-11-08 16:17:34 -08:00

..

append.spec.ts

[routing-utils] Allow to appendRoutes add null phase (#8814)

2022-11-01 11:17:50 -04:00

index.spec.ts

[routing-utils] MAJOR refactor getTransformedRoutes and types (#8155)

2022-07-15 14:05:08 -04:00

merge.spec.ts

[routing-utils] Convert tests to TypeScript (#7959)

2022-06-13 23:29:00 -07:00

superstatic.spec.ts

[next][routing-utils] Add missing matcher support (#8874)

2022-11-08 16:17:34 -08:00