chore(deps-dev): bump msw from 2.1.5 to 2.3.1

[dependabot]

Bumps msw from 2.1.5 to 2.3.1.

Release notes

Sourced from msw's releases.

v2.3.1 (2024-06-01)

Bug Fixes

• preserve trailing optional path parameters (#2169) (e69bbd6fda7c7997b523457b644440889e68d994) @​kettanaito @​KaiSpencer

v2.3.0 (2024-05-08)

[!WARNING] This release changes how MSW treats unhandled exceptions in response resolvers. Previously, they were treated as request errors. Starting with this release, unhandled resolver exceptions will be coerced to 500 Unhandled Exception mocked error responses produced by the library. Please note that you must not intentionally throw errors in your resolvers. Please use Response.error() to mock request/network errors. Unhandled exceptions are considered unintended and will be treated as if they happen on the actual server.

Features

• treat unhandled exceptions in handlers as 500 error responses (#2135) (519139924639a0135169210a0d9c5cd0a0d3e994) @​kettanaito
• prioritize the node export when importing msw/node (#2134, transitively through @​mswjs/interceptors).
• add a new unhandledException event (#2135, docs).

server.events.on('unhandledException', ({ request, error }) => {
  console.log('%s %s errored! See details below.', request.method, request.url)
  console.error(error)
})

Bug Fixes

• Disposable: make the ".dispose()" method synchronous (#2144) (686d3d668f7b76cbf26f75c990fded5e4fd298da) @​kettanaito

v2.2.14 (2024-04-17)

Bug Fixes

• preserve search params in "onUnhandledRequest" messages (#2128) (64bcae7c27dfd36a35723a323c29cf0f5138a81c) @​nagadevkrishna @​kettanaito
• give node export condition higher priority (#2134) (f948d13d2df85efa8d276396e1e60da235523a0e) @​phryneas

v2.2.13 (2024-03-27)

Bug Fixes

• use createRequestId() instead of crypto.randomUUID() (#2113) (8f2be77627b94318e6c2e6d6eee38fc49558c6d9) @​kettanaito

v2.2.12 (2024-03-27)

Bug Fixes

• do not mutate user-defined "X-Request-Id" request header (#2110) (64b6ba516123d655e82d164e8ed1bb1f75b8cff8) @​kettanaito

v2.2.11 (2024-03-26)

Bug Fixes

... (truncated)

Commits

• bed402c chore(release): v2.3.1
• e69bbd6 fix: preserve trailing optional path parameters (#2169)
• 540e0ac docs: fix readme badges underline (#2152)
• d97a528 docs(CONTRIBUTING): update test name and pnpm install link (#2149)
• ec70ba9 test: add .use() replacement regression tests (#2145)
• 7cf34c1 chore(release): v2.3.0
• 686d3d6 fix(Disposable): make the ".dispose()" method synchronous (#2144)
• 5191399 feat: treat unhandled exceptions in handlers as 500 error responses (#2135)
• 43a163b chore(release): v2.2.14
• 64bcae7 fix: preserve search params in "onUnhandledRequest" messages (#2128)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/eslint-plugin-no-only-tests@3.1.0	None	0	9.54 kB	levibuzolic
npm/execa@8.0.1	environment Transitive: filesystem, shell	+16	301 kB	ehmicky
npm/object-path@0.11.8	None	0	60.9 kB	mariocasciaro

🚮 Removed packages: npm/@fission-codes/channel@0.0.2, npm/@fission-codes/client@0.0.1, npm/@fission-codes/eslint-config@0.1.1, npm/@fission-codes/homestar-wit@0.0.3, npm/@fission-codes/homestar@2.4.0, npm/@fission-codes/ucan@0.3.0, npm/depcheck@1.4.7, npm/lint-staged@15.2.2, npm/simple-git-hooks@2.11.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Install scripts	npm/simple-git-hooks@2.11.0	Install script: postinstall Source: node ./postinstall.js

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/simple-git-hooks@2.11.0