This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit b594029:

Thanks for adding this, @snaka!
We need to also add an integration test for this, as our CI didn't catch this issue being merged.

@kettanaito

I have a problem with that.
I don't know how to write or run Integration test.
Especially when I run integration test locally, I get the following error and all tests fail.

I ran yarn build before the test.
This is the situation on my current main branch.

My working environment is Windows (WSL2).
Is that the cause of the problem?

The tests run by GitHub Actions seemed to be using a virtual macOS, so I was wondering about that.

I followed the message and ran test:integration with the --detectOpenHandles option.

It seems that I am missing some libraries in my environment.

      Missing libraries we didn't find packages for:
          libexpat.so.1
          libgcc_s.so.1

I will install these libraries and give it a try.

Sorry.
It's still going to take a while to get Playwright to work on my Windows 10!
I will keep trying, but if you have any other suggestions, I would appreciate your advice.

Hey, @snaka. No worries. I know it can be challenging to run PW on other systems. I will checkout your branch and help you with the test when I have a minute.

Thanks @kettanaito . It is very helpful.

I've added the integration test for this fix 👍 Also found some shared state issue in the existing unit test, fixed that as well (I believe that one has been failing the CI).

I've found another issue that events.removeAllListeners() didn't actually remove the listeners. Fixed in https://github.com/open-draft/strict-event-emitter/releases/tag/v0.2.6.

Thank you for helping fix this, @snaka! Welcome to contributors.

Thank you @kettanaito for your support.
Glad to hear the problem was resolved quickly!

Released: v0.47.4 🎉

This has been released in v0.47.4!

• 📄 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.