12e22edd74
This change allows the Turbopack's node router to serve `_next/static/development/_devMiddlewareManifest.json` file, which is just the matchers for middleware routes. This is usually handled by the node dev server anyways, but we were filtering out the route so that Turbopack could handle it. But, Turbopack doesn't implement the route matching logic at all, it's all handled by our node router. So Turbopack can't know what the middleware matchers are. Having the router just handle this like the normal dev server is both easy and efficient (I don't want to spin up _another_ node instance just to transform the matchers into the expected format). Fixes WEB-979 --------- Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
|---|---|---|
| .. | ||
| crates | ||
| native | ||
| package.json | ||
| README.md | ||
@next/swc
This package is responsible for swc compilation customized for next.js
Development
Run tests
cargo test
# Update snapshots and fixtures for tests
UPDATE=1 cargo test
Format code before submitting code
cargo fmt
Build the binary to integrate with next.js
pnpm build-native