Comments (6)
Hi kettanaito; sorry for the absence; yep I think it's the way to go as well.
It would have been nice to have the same setup/import for both jest and rn, but the user can likely get there using jest module aliases.
If there's anything that worry me here is that both the node and the native package should expose the same api interface, as the user will use it interchangeably ( between jest and rn ) and expect the same behaviour. But it's probably okay.
from interceptors.
That should be fine. In RN development you should use msw/native
, while in tests msw/node
. I find that quite straightforward, even if they promise the same API.
With the latest version (0.5.0
) that should work already, but I haven't tested that yet.
from interceptors.
Hey, @Federkun. Thanks for following up on this 👍
from interceptors.
Hey 👋 How is your investigation going? Anything I can help with?
from interceptors.
I believe this can be solved by #48. What do you think?
from interceptors.
I'm closing this, as the latest release should already cover jest runtime in React Native. Feel free to comment if you find out any unexpected behaviors. Thanks.
from interceptors.
Related Issues (20)
- ReadableStream cannot be properly polyfilled in this engine HOT 5
- Error using BatchInterceptor with browserInterceptors in browser environment. HOT 7
- `Response.type` throws in miniflare-like environments HOT 1
- Support "CONNECT" requests (in proxies) HOT 11
- Support HTTP2 HOT 3
- Intercepted fetch results in the the process never exiting / hangs Mocha tests
- error listener get called twice on mocked error with sync handler HOT 2
- Use "urlToHttpOptions" from "node:url"
- Header keys for requests are being converted to lowercase
- ReferenceError: TextEncoder is not defined when running (jest) tests HOT 4
- Treat exceptions as 500 responses instead of a "Failed to fetch" error HOT 7
- XMLHttpRequestController creates bad URL when location exists but href not set HOT 4
- Support aborting intercepted requests HOT 6
- WebSocket: Outgoing client events have the wrong "currentTarget" HOT 2
- WebSocket: Decide how to handle actual server errors
- Flaky: `modules/http/response/readable-stream.test.ts`
- ClientRequestInterceptor incorrectly encodes basic authentication header HOT 15
- Abstract request emitting logic HOT 1
- Await all "response" listeners to finish HOT 6
- Protocol "https:" not supported. Expected "http:" when using "proxy-agent" HOT 1
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 interceptors.