Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency msw to v1 #164

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency msw to v1 #164

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
msw (source) 0.39.2 -> 1.3.4 age adoption passing confidence

Release Notes

mswjs/msw (msw)

v1.3.4

Compare Source

v1.3.4 (2024-09-07)

Bug Fixes

v1.3.3

Compare Source

v1.3.3 (2024-03-15)

Bug Fixes

v1.3.2

Compare Source

v1.3.2 (2023-10-01)

Bug Fixes

v1.3.1

Compare Source

v1.3.1 (2023-09-13)

Bug Fixes

v1.3.0

Compare Source

v1.3.0 (2023-09-03)

Features

v1.2.5

Compare Source

v1.2.5 (2023-08-28)

Bug Fixes

v1.2.4

Compare Source

v1.2.4 (2023-08-25)

Bug Fixes

v1.2.3

Compare Source

v1.2.3 (2023-07-20)

Bug Fixes

v1.2.2

Compare Source

v1.2.2 (2023-06-09)

Bug Fixes

v1.2.1

Compare Source

v1.2.1 (2023-03-24)

Bug Fixes

v1.2.0

Compare Source

v1.2.0 (2023-03-22)

Features

v1.1.1

Compare Source

v1.1.1 (2023-03-20)

Bug Fixes

v1.1.0

Compare Source

v1.1.0 (2023-02-24)
Features
Bug Fixes

v1.0.1

Compare Source

v1.0.1 (2023-02-10)

Bug Fixes

v1.0.0

Compare Source

v1.0.0 (2023-01-25)

⚠️ BREAKING CHANGES
Features

v0.49.3

Compare Source

v0.49.3 (2023-01-19)

Bug Fixes

v0.49.2

Compare Source

v0.49.2 (2022-12-13)
Bug Fixes

v0.49.1

Compare Source

v0.49.1 (2022-11-28)

Bug Fixes

v0.49.0

Compare Source

v0.49.0 (2022-11-19)

Features

v0.48.3

Compare Source

v0.48.3 (2022-11-15)

Bug Fixes

v0.48.2

Compare Source

v0.48.2 (2022-11-13)

Bug Fixes

v0.48.1

Compare Source

v0.48.1 (2022-11-10)

Bug Fixes

v0.48.0

Compare Source

v0.48.0 (2022-11-08)

Features

v0.47.4

Compare Source

v0.47.4 (2022-10-04)

Bug Fixes

v0.47.3

Compare Source

v0.47.3 (2022-09-15)

Bug Fixes

v0.47.2

Compare Source

v0.47.2 (2022-09-13)

Bug Fixes

v0.47.1

Compare Source

v0.47.1 (2022-09-10)

Bug Fixes

v0.47.0

Compare Source

v0.47.0 (2022-09-04)

Features

v0.46.1

Compare Source

v0.46.1 (2022-09-01)

Bug Fixes

v0.46.0

Compare Source

v0.46.0 (2022-08-31)

Features
server.listHandlers()
worker.listHandlers()

v0.45.0

Compare Source

v0.45.0 (2022-08-22)

Features
  • make GraphQL a peer dependency, support GraphQL v15.0 (#​1356) (ca0e2e0)

v0.44.2

Compare Source

v0.44.2 (2022-07-19)

Bug Fixes
  • transfer mocked response as ArrayBuffer to the worker (#​1337) (95be5f8)

v0.44.1

Compare Source

v0.44.1 (2022-07-14)

Bug Fixes

v0.44.0

Compare Source

v0.44.0 (2022-07-13)

Breaking changes
  • req.destination default value is now "" (empty string), previously "document".
  • req.redirect default value is now ""follow", previously "manual".
  • The library no longer exports the parseIsomorphicRequest() function (#​1316). Please use MockedRequest class instead.
Features
Deprecations
  • req.body is deprecated. Please use explicit request body reading methods: req.text(), req.json(), req.arrayBuffer() (other methods, like req.formData() are currently not supported).
rest.post('/user', async (req, res, ctx) => {
  const newUser = await req.json()
})

req.body is still present for compatibility reasons but will be removed in the next releases.

v0.43.1

Compare Source

v0.43.1 (2022-07-07)

Bug Fixes
  • support multiple response cookies using "ctx.cookie()" (#​1311) (66c3ad8)

v0.43.0

Compare Source

v0.43.0 (2022-07-04)

Features
  • send mocked response body as ReadableStream to the worker (#​1288) (78c7d7e)

v0.42.3

Compare Source

v0.42.3 (2022-06-22)

Bug Fixes

v0.42.2

Compare Source

v0.42.2 (2022-06-22)

Bug Fixes
  • setupServer: reference interceptors to support fast refresh (#​1299) (72f0b25)

v0.42.1

Compare Source

v0.42.1 (2022-06-07)

Bug Fixes

v0.42.0

Compare Source

v0.42.0 (2022-05-30)

Features
Bug Fixes

v0.41.1

Compare Source

v0.41.1 (2022-05-27)

Bug Fixes

v0.41.0

Compare Source

v0.41.0 (2022-05-22)

Features

v0.40.2

Compare Source

v0.40.2 (2022-05-20)

Bug Fixes

v0.40.1

Compare Source

v0.40.1 (2022-05-19)

Bug Fixes

v0.40.0

Compare Source

v0.40.0 (2022-05-17)

Breaking changes
  • Returning undefined, or early returns, from response resolvers, now does not perform request as-is, and is instead treated as a handler that didn't do anything. Please return req.passthrough() if you wish to bypass a request.
rest.get('/resource', (req, res, ctx) => {
// I want to perform this intercepted request as-is.
-  return
+  return req.passthrough()
})
Features
Bug Fixes
  • setupWorker: warn on multiple "worker.start" and "worker.stop" calls (#​1238) (cfe0709)
  • remove console.log from "setRequestCookies" (6f7ed98)
  • set "credentials" to "same-origin" for "ClientRequest" (#​1159) (c3cd80a)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Mar 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
azure-auth-api-test ❌ Failed (Inspect) Sep 10, 2024 4:56pm

@renovate
Copy link
Contributor Author

renovate bot commented Jul 20, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vtfk/react-msal@2.0.3
npm ERR! Found: react@18.1.0
npm ERR! node_modules/react
npm ERR!   react@"18.1.0" from the root project
npm ERR!   peer react@"^16.14.0 || ^17.0.0 || ^17.0.1 || ^17.0.1 || ^17.0.1 || ^18.0.0" from @vtfk/components@0.8.1
npm ERR!   node_modules/@vtfk/components
npm ERR!     @vtfk/components@"0.8.1" from the root project
npm ERR!   7 more (react-dom, react-popper, react-router, react-router-dom, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.0.0 || ^17.0.0" from @vtfk/react-msal@2.0.3
npm ERR! node_modules/@vtfk/react-msal
npm ERR!   @vtfk/react-msal@"2.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR!   peer react@"^16.0.0 || ^17.0.0" from @vtfk/react-msal@2.0.3
npm ERR!   node_modules/@vtfk/react-msal
npm ERR!     @vtfk/react-msal@"2.0.3" 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.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-18T13_33_31_176Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-18T13_33_31_176Z-debug-0.log

Dependency update (patch) :)
Copy link
Contributor Author

renovate bot commented Sep 10, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vtfk/react-msal@2.0.3
npm error Found: react@18.1.0
npm error node_modules/react
npm error   react@"18.1.0" from the root project
npm error   peer react@"^16.14.0 || ^17.0.0 || ^17.0.1 || ^17.0.1 || ^17.0.1 || ^18.0.0" from @vtfk/components@0.8.1
npm error   node_modules/@vtfk/components
npm error     @vtfk/components@"0.8.1" from the root project
npm error   7 more (react-dom, react-popper, react-router, react-router-dom, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.0.0 || ^17.0.0" from @vtfk/react-msal@2.0.3
npm error node_modules/@vtfk/react-msal
npm error   @vtfk/react-msal@"2.0.3" from the root project
npm error
npm error Conflicting peer dependency: react@17.0.2
npm error node_modules/react
npm error   peer react@"^16.0.0 || ^17.0.0" from @vtfk/react-msal@2.0.3
npm error   node_modules/@vtfk/react-msal
npm error     @vtfk/react-msal@"2.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-10T16_55_54_025Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-10T16_55_54_025Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Dependency updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants