Comments (5)
This is an issue with Jest. Most likely related to structuredClone()
and Jest using core-js
that doesn't implement structuredClone()
correctly and refuses you to give the correctly working global function from Node.js.
Here are a few references that I hope will prove helpful to you:
I'm closing this because I will not look into Jest/JSDOM-related issues (but anyone is welcome to dive into this, I don't mean to discourage you either!). No amount of time I invest into this will make those tools any less broken. If you can, migrate to Vitest. If you can't, raise this in the Jest repo. The more people raise these problems, the more likely Jest will fix them. Nothing we can or should do on MSW's side—it's using valid standard JavaScript.
from msw.
@kettanaito Thank you for your response, from one of the references you have provided in your response, I read that downgrading undici to v5 helped someone. I tried that and apparently I no longer see Axios network error and my test cases seem to be working.
from msw.
@schok-d, that's great news! So, it was the structuredClone()
issue. Downgrading Undici "helps" in this case because v5 doesn't rely on structuredClone()
.
from msw.
Smells a lot like the whatwg-fetch-esque style problem: using a non-spec compliant Response polyfill
more info about it here:
if you use the Response global from node >=18 in your test environment I think your issue will be resolved.
I’d be happy to verify if you could post your package.json dependencies and show your relevant test setup files/configuration
from msw.
Thanks for the response @akmjenkins. One important thing to note here, I generated this project using NX and its using @nx/jest plugin.
I fixed my test environment setup and added jest polyfills(mentioned below) which fixed above issue but now I am getting AxiosNetwork error.
message: 'Network Error',
name: 'AxiosError',
code: 'ERR_NETWORK',
config: {
transitional: {
silentJSONParsing: true,
forcedJSONParsing: true,
clarifyTimeoutError: false
},...
Polyfills
Object.defineProperties(globalThis, {
TextDecoder: { value: TextDecoder },
TextEncoder: { value: TextEncoder },
ReadableStream: { value: ReadableStream }
})
const { Blob, File } = require('node:buffer')
const { fetch, Headers, FormData, Request, Response } = require('undici')
Object.defineProperties(globalThis, {
fetch: { value: fetch, writable: true },
Blob: { value: Blob },
File: { value: File },
Headers: { value: Headers },
FormData: { value: FormData },
Request: { value: Request },
Response: { value: Response }
})
Everything works perfectly fine if I switched to [email protected].
from msw.
Related Issues (20)
- "InvalidStateError: The object is in invalid state" when mocking rest api
- Unable to use msw/node for testing solid-js due to `resolve.conditions` set to `browser` HOT 5
- drop CommonJS support HOT 2
- quiet: true should supress RESPONSE LISTENER logs HOT 4
- Narrowing the response body type in `HttpResponse.json` HOT 16
- Error: No known conditions for "./browser" specifier in "msw" package HOT 5
- "Cannot read properties of undefined (reading 'get')" when using generators/async generators as resolvers HOT 2
- `TypeError: crypto.randomUUID is not a function` with msw 2.2.12 HOT 3
- When running Cypress tests in Electron, MSW activation occurs after test completion, causing tests to fail
- Chrome unregisters MSW after 5 mins of inactivity / idle HOT 13
- First-class Server-Sent Events (SSE) API
- The currently registered Service Worker has been generated by a different version of MSW (undefined) HOT 1
- disable prettier as well HOT 1
- Issue with response resolver types after recent upgrade HOT 2
- Preserve the original request URL in "onUnhandledRequest" warnings HOT 3
- The cookies object recevied in the handlers varies depending on the placement of the handler within the `setupServer` function. HOT 5
- Calls to worker.use() remove handlers to same endpoint with different method HOT 1
- Unable to use HttpResponse.error() with TypeScript HOT 3
- How do I implement MSW in a NextJS backend?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from msw.