feat!: 3.0

[kettanaito]

• Fixes Support intercepting navigate requests #1594
• Fixes My app hooks in beforeunload with a confirmation message and then MSW stops working #1105

BREAKING CHANGES

• Deprecate support for Node.js v18 and v20 (feat: drop support for Node.js 18, 20 #2729). The minimal supported Node.js version if v22.
• Deprecate support for TypeScript 5.1 and 5.2 (chore: use Headers.getSetCookie #2730)

Features

• Support TypeScript 5.9.
• Support intercepting page navigations and form submissions (feat: support navigate requests #2721).
• Migrate from path-to-regexp to @msw/url (feat!: migrate to @msw/url #2678).
• worker.stop() returns a Promise (fix: await in-flight requests from closing clients #2724). Awaiting it is relevant only in in-flight critical scenarios.

Bug fixes

• Fix an issue where preventing a page closure via the beforeunload listener would unregister the MSW worker (My app hooks in beforeunload with a confirmation message and then MSW stops working #1105).
• Fix an issue that caused intermittent test failures in Vitest Browser Mode and Firefox if using maxWorkers: 1 (Firefox & Vitest Browser Mode Timing Problems (CI) #2726).
• Fix an issue where in-flight requests were incorrectly passthrough when performed before calling worker.stop() (fix: await in-flight requests from closing clients #2724, MSW sometimes still handles requests after worker is stopped #2597).

---

Todos

• Document the changes.
• Write the migration guidelines.
• Stress-test the features.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 18a6019e-4471-4bf9-829d-fa7afa2c1823

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/3.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/msw@2692

commit: 6ada87e

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​msw/​url@​0.1.1
	@​mswjs/​interceptors@​0.41.3 ⏵ 0.41.9	+5		+1	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @mswjs/interceptors is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/@mswjs/interceptors@0.41.9 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@mswjs/interceptors@0.41.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dsonet]

Hey @kettanaito, thanks a lot for your great work!

Is it possible to include this feature? Here’s the link: #2357
It would be nice if it could cross the finish line.

[kettanaito]

@dsonet GraphQL subscriptions will likely make it either to 3.0 or even to 2.0. They aren't as tedious to implement with the new architecture now. I've introduced the concept of handlers merging in the recent changes to 2.0 and that was the missing piece for the subscriptions.

As always, if your company needs that support in MSW, please consider becoming a sponsor! Thank you.