undici
fastify-http-proxy
Our great sponsors
undici | fastify-http-proxy | |
---|---|---|
18 | 1 | |
5,664 | 314 | |
3.3% | 2.5% | |
9.8 | 7.2 | |
3 days ago | 9 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.
-
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
-
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:
-
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...
-
Fetch API has landed into Node.js
https://github.com/nodejs/undici/blob/2dd3437e20c5a3cc466226...
I've argued with the authors of the fetch spec about this before, and ultimately settled on using https://www.npmjs.com/package/set-cookie-parser#user-content... to work around this flaw. (For clarity, I published the package, but chrusart wrote that method - https://github.com/nfriedly/set-cookie-parser/pull/19)
In undici this will fail with res.status 0, as per spec. You aren't allowed to see the content of a redirect, like in a browser.
Is that URL incorrect? Should it be https://github.com/nodejs/undici ?
The commit adds undici (another Node.js project at https://github.com/nodejs/undici ) as a dependency and exposes its `fetch` - the code changes you see are probably just adding a flag :)
> I just wonder how come features like this that kind of seems obvious to include in the ecosystem takes quite some time to land?
I answered that below (check it out) but note how expensive adding a bad API is vs. asking people for one more `npm install` :) There is more discussion in https://github.com/nodejs/node/issues/19393 and in https://docs.google.com/document/d/1tn_-0S_FG_sla81wFohi8Sc8... a discussion from 2018 we had on it
-
NodeSecure - The future
Rewriting SlimIO/npm-registry from zero in the org (with undici as http client).
fastify-http-proxy
-
How to securely call an authenticated API from your front end
fastify-http-proxy accepts a replyOptions object which it passes through to fastify-reply-from. These options give us full control to modify requests and responses as they pass through our proxy server.
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
node-fetch - A light-weight module that brings the Fetch API to 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
Nock - HTTP server mocking and expectations library for Node.js
example-nodejs-api-proxy-server - Example Node.js API proxy server built with @fastify/fastify-http-proxy
fastify-reply-from - fastify plugin to forward the current http request to another server
download - Download and extract files
set-cookie-parser - Parse HTTP set-cookie headers in JavaScript
http-proxy - A full-featured http proxy for node.js