Comments (8)
Hi, @vishal-vc. Please submit a reproduction repository for this issue. We have an extensive test suite that doesn't replicate your issue. Clearly, something is specific to your setup.
Happy to iterate on this once you post a repo. Until then, closed.
from msw.
@vishal-vc did you find a specific fix for this issue? I am experiencing it.
Using React Native, ^0.68.7, and MSW latest with axios.
FYI,
http.post('/something', () => {
return new Response({test:true}, {
status: 200,
headers: {
'Content-Type': 'application/json',
'Content-Length': 1270,
'Last-Modified': 'Mon, 13 Jul 2020 15:00:00 GMT',
},
});
})
The headers and repsonse status is set correctly, however the response is still ''
from msw.
hey @mayfairr-plt take a look at #2026 I think it's the same issue. I'm not sure where the fix is necessarily going to be applied though (here, or RN, or Axios etc.)
from msw.
@mayfairr-plt, it looks you are using the Response
class incorrectly. You have to stringify the body:
-return new Response({test:true}, {
+return new Response(JSON.stringify({test:true}), {
Once you do, the response body will be the JSON you expect.
Alternatively, use the Response.json()
static method or HttpResponse.json()
, where the stringifying isn't necessary:
+import { HttpResponse } from 'msw'
http.post('/something', () => {
- return new Response({test:true}, {
+ return HttpResponse.json({test:true}, {
status: 200,
headers: {
- 'Content-Type': 'application/json',
- 'Content-Length': 1270,
'Last-Modified': 'Mon, 13 Jul 2020 15:00:00 GMT',
},
});
})
from msw.
Also experiencing this. I'm in a repo with significant legacy dependencies/jest setup. It's hard to pinpoint the issue but I'm consistently getting an empty string for data
from axios even though the content-length of the response accurately describes the content I'm returning from the endpoint.
Sorry, I don't have a repo (I tried a vitest stackblitz only to find out it worked without my legacy cruft), but just wanted to add a commiserative "me too"
Using the latest axios and latest msw
from msw.
@akmjenkins, see if there aren't any errors during the request. Those may not surface apparently all the time. Otherwise, I cannot help much without a reproduction case for this.
from msw.
@kettanaito here you go:
https://stackblitz.com/edit/stackblitz-starters-prcm96
It looks like it has to do with whatwg-fetch which is a common polyfill in react/react-native projects
When you use the fetch Request/Response classes from the node environment it works.
I haven't gone any further, though.
Likely the same underlying issue as #2026
from msw.
Tried doing what you suggested @akmjenkins didn't work from the get go and couldn't invest enough time trying to get it to work. Ended up using v1 msw, and it worked without any issues 🚀
from msw.
Related Issues (20)
- 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
- "TypeError: response.body.getReader is not a function" for HTTPResponse of JSON type HOT 5
- 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 2
- Unable to use HttpResponse.error() with TypeScript HOT 3
- How do I implement MSW in a NextJS backend?
- Missing `await` in the getting started example section for fetch call HOT 4
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.