feat: support typescript 4.9, drop support for typescript 4.2, 4.3

[wtchnm]

#1462

[codesandbox-ci]

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 80c021a:

Sandbox	Source
MSW React	Configuration

[kettanaito]

Do you happen to know how old TS 4.2/4.3 is? I wonder if it's safe to drop support for them.

[wtchnm]

TS 4.2 is 1 year and 9 months old, TS 4.3 is 1 year and 6 months old. According to the release notes, no breaking changes would block migration to TS 4.4.
See TS 4.3 breaking changes and TS 4.4 breaking changes.

[kettanaito]

Thanks for looking that up! That's lovely, let's drop their support and introduce 4.9.

[kettanaito]

This is great. Thanks for working on this, @wtchnm 👏

[wtchnm]

Sure, thanks for your amazing work on this lib!

[kettanaito]

Released: v0.49.0 🎉

This has been released in v0.49.0!

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

[andykenward]

@kettanaito Can you also do this for the msw@next 0.0.0-fetch.rc-1 ? I'm currently getting this npm error.

node : 16.18.1
npm: 8.19.2

$ npm install msw@next
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: msw@0.0.0-fetch.rc-1
npm ERR! Found: typescript@4.9.3
npm ERR! node_modules/typescript
npm ERR!   typescript@"4.9.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@">= 4.2.x <= 4.8.x" from msw@0.0.0-fetch.rc-1
npm ERR! node_modules/msw
npm ERR!   msw@"0.0.0-fetch.rc-1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.8.4
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@">= 4.2.x <= 4.8.x" from msw@0.0.0-fetch.rc-1
npm ERR!   node_modules/msw
npm ERR!     msw@"0.0.0-fetch.rc-1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[kettanaito]

Hey, @andykenward. Sure, will update that release as well when I have a minute.