undici
Nock
Our great sponsors
undici | Nock | |
---|---|---|
18 | 21 | |
5,728 | 12,519 | |
2.7% | 0.4% | |
9.8 | 8.3 | |
5 days ago | 6 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
undici
-
When LIMIT 9 works but LIMIT 10 hangs: A short debugging story
Yeah: interestingly, they had a test for the biggest category of frame, but not for the two other categories: https://github.com/nodejs/undici/blob/main/test/websocket/se...
The test I contributed is very specific to the frame fix I made, but I should probably go back and contribute more tests in send.js that test other lengths too.
-
Is native fetch in v18 faster than dedicated libraries?
The native fetch in Node.js 18 is based on undici.
-
Quickest/fastest http package
Sadly, Undici's slow. Reference issue.
-
Are all fetch API's for Nodejs inefficient in terms of latency ? Cant go lower than 4ms on localhost
Did you try just using the http lib, or even axios/node-fetch? The fetch API in node is very new and looks like there have been concerns about its performance: https://github.com/nodejs/undici/issues/1203
-
I made an Express-like framework for IPC communication
A library that can be handy is Undici - a great HTTP/1.1 client, see here where they apparently added unix:// support: https://github.com/nodejs/undici/pull/226
-
Pull Congressional Data via SMS with the Congress API and JavaScript
Afterwards, create your new project and install our lone requirement [undici](https://github.com/nodejs/undici) to make HTTP requests in Node.js by running:
-
Node JS 18.12.0 goes LTS
Test coverage currently sits at 89%, hopefully will be stable soon.
-
Animal Crossing Simulator Discord Bot
undici
-
Fetch API has finally landed Node v18.0
We implemented fetch API operation with Node without the need for any library imports. The thing to note that under the hood that the fetch implementation is done based on another HTTP client, undici, which is actually a HTTP client written specifically for Node.js. It is an HTTP 1.1 only client.
-
Deno 1.20
> ...enough insights of how much better/faster Deno is
We moved our Deno project to Node because of lack of lower-level APIs on their Conn interfaces [0][1], but otherwise for our use-case (lots of tiny HTTPS connections) Deno absolutely blew Node out-of-the-water. Even at p50 (100tps) Deno (v1.18) was 10x faster than Node (v17.x) [2]
RAM wise, I found Deno (v1.18+) use 10M or so higher for the same code-base.
[0] https://github.com/denoland/deno/issues/13636
[1] https://github.com/denoland/deno/issues/9109
[2] https://github.com/nodejs/undici/issues/1203#issuecomment-10...
Nock
-
Contract Testing?
So, why would you want a REAL server to mock request/reponses? You have a lot of intercepts today that sit on the network layer and you can define things like "If you send request to that endpoint, with that json, please return that Status" (for NodeJS example, Nock - https://github.com/nock/nock)
-
I made wirepig, a simple way to mock HTTP and TCP dependencies in tests.
That said, folks seem to like "recording" features in these sorts of tools (Ruby's VCR, nock, etc), so maybe there's a future where I add something similar. I've always just found the ergonomics of those features awkward to deal with, especially having to flip back and forth between tests and fixtures files to figure out what's wired to what, but maybe there's a clean solution... perhaps a "live request" mode that just prints mock code snippets of request/response pairs passing through your app.
-
Is there a better way to mock an axios call?
While not mocking per say I usually use nock for http calls. You can use nock.recorder.rec() to capture the http call to play back during test, That way you are always using "live" code but not making real calls to servers.
- How do you practice with React without setting up your own backend?
-
OSD600 - Telescope - Testing for feed URLs
I looked at the service which is used to get the feed URLs from a blog URL and noticed it takes the html response of the blog URL and gets the links ( tags) by checking the type attribute value against a list of valid feed values. So, I decided to use a similar approach by getting the html response for a provided URL and checking the Content-Type header against a list of valid MIME types for a feed. I ended up updating the logic to test if a URL is a feed URL, returning it if true. If the URL is found to not be a feed URL, it would try to get the feed URLs assuming the URL is a blog URL. I tested and confirmed that the new logic worked for both blog and feed URLs. Then, I added some tests for the new function I added to test for a feed URL. Testing this ended up being simpler than I expected as all I had to do was mock the response of a test url (using nock), and then check if the function returned the correct boolean value for a url. I created a PR and noticed that some of the tests in another file were now failing. While I was investigating this, I got a review on my PR, requesting me to add another test to the file which had the failing tests. That file tested the API service as a whole. I found out that nock only mocks a URL's response for one request by default. And since I was now checking for a feed URL as well, the function which returned the feed URLs from a blog URL was throwing an error since the nock for that was used up. To fix this, I had to specify in the nock statement to mock the URL response for two requests:
- What features would you consider missing/nice to haves for backend web development in Rust?
-
Axios shipped a buggy version and it broke many productions apps. Let this be a lesson to pin your dependencies!
There are libraries like https://github.com/nock/nock to prevent mocking the whole axios.
-
How to test an endpoint that depends on external API?
Use nock: https://github.com/nock/nock
-
How to mock a useQuery in jest?
Going based off the documentation I sent you in my last reply, there is an example that uses nock to emulate api responses. I haven't used nock myself, but the example seems pretty simple to use. You just need to take the example and change the response object to be the shape of what your getStuffFromDatabase function returns. That way your useCategory function runs as close to normally as possible, while providing a mock response value instead of hitting the database.
-
Is it acceptable to use mock servers, like Postman, for testing in Android?
If youโre willing to venture into nodejs territory, then nock is a fantastic and simple to set up http mock server. https://github.com/nock/nock
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
msw - Seamless REST/GraphQL API mocking library for browser and Node.js.
node-fetch - A light-weight module that brings the Fetch API to Node.js
http-proxy - A full-featured http proxy for node.js
got - ๐ Human-friendly and powerful HTTP request library for Node.js
request - ๐๐พ Simplified HTTP request client.
undici-fetch - A WHATWG Fetch implementation based on @nodejs/undici
superagent - Ajax for Node.js and browsers (JS HTTP client). Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
fastify-http-proxy - Proxy your http requests to another server, with hooks.
miragejs - A client-side server to build, test and share your JavaScript app