fix(react-native): import "node:events" lazily

[kettanaito]

• Fixes Expo / React Native not having support for 'events' #1847

Changes

• Adds a context on the SetupServerApi class.
• Adds context.nodeEvents() getter that lazily imports node:events and returns undefined if the import failed (e.g. in React Native).
• Moves the AbortSignal max listeners handling from the request listener to a private method of the SetupServerApi class. Makes it fail-fast.

[kettanaito]

I think this Promise should only ever fire once. I'm not sure if I'm structuring this correctly but the intention is to try to import this module once so each outgoing request (request listener) doesn't pend on this import, increasing the response time).

[mattcosta7]

I think this makes sense, hopefully that helps work around the issues with this api in react-native like environments.

Re the import promise only being called once, I think it should resolve immediately since import calls are cached as far as I know, so that should be fine

[DogukanTansuk]

@mattcosta7 Can we release a beta version with this change? I could try and give feedback.

[kettanaito]

@DogukanTansuk, you can always install a package from a particular branch/commit. I believe all modern package managers support that (NPM, Yarn, PNPM). You can install it that way and let me know if this fixes the issue? Thanks!

[kettanaito]

I'm promoting this to a release candidate because the change is backward-compatible and has no effect on the existing msw/node integrations. Folks would have to give this a try for msw/native and report back whether the issue is fixed. That's the optimal course of action until we have an official React Native example we can run in the existing smoke tests pipeline.

[kettanaito]

Released: v2.0.7 🎉

This has been released in v2.0.7!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.