You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/migrate-v1-to-v2.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,9 +57,25 @@ The minimum supported Node.js version is now `^20.19.0 || >=22.12.0`.
57
57
58
58
> Refer to the [http-proxy-middleware v3 migration guide](https://github.com/chimurai/http-proxy-middleware/blob/master/MIGRATION.md) for details.
59
59
60
-
### Upgraded Express to v5
60
+
### Default app now uses `connect`
61
61
62
-
`express` has been updated to v5, see [Introducing Express v5: A New Era for the Node.js Framework](https://expressjs.com/2024/10/15/v5-release.html) for details.
62
+
When `devServer.app` is omitted, `@rspack/dev-server` now creates a
63
+
`connect` app instead of an Express app.
64
+
65
+
The dev server only needs a minimal middleware pipeline. Connect provides the same `(req, res, next)` interface as Express while being significantly smaller and having fewer dependencies, making it a better fit for this use case.
66
+
67
+
If you relied on Express-only APIs on `devServer.app`, such as `app.get()`,
68
+
`app.post()`, or `res.send()`, provide your own Express app explicitly:
0 commit comments