Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
In the next version of Bun
`Bun.FetchSession` gives you a `fetch` function with its own keepalive connection pool

ALT Dark slide with the Bun logo and a "new in Bun" badge. Large headline: "Bun.FetchSession". Subtitle: "fetch() with its own connection pool." Below it, a code sample: const api = new Bun.FetchSession({ proxy: "http://proxy:8080", tls: { ca }, keepAlive: { idleTimeout: 30 }, }); await api.fetch(url); new Octokit({ request: { fetch: api.fetch }, }); "api.fetch" is highlighted in both places. Three cards at the bottom read: "Own pool: isolated keep-alive", "Proxy + TLS: set once per session", "Drop-in: works in any SDK".
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
TanStack compromised. More and more evidence to use these tools to start writing cleanroom versions of big npm packages and use that instead.
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
New in Zod 4.6 — .validate()
Unlike .parse(), this method returns a boolean, aborts early when it encounters the first error, and instantiates no issue objects. It is 13-39x faster than `.safeParse().success` on invalid data.
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all.
There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message.
A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this.
On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting!
There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting.
I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first.
I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
github.com/TanStack/router/i…
Credit to the security researcher for responsible disclosure.
⚡️ Vite 8.0 is here!
The most significant architectural change since Vite 2.
⏬ Powered by Rolldown bringing faster production builds and more consistency
🛤️ New features such as tsconfig paths and emitDecoratorMetadata support
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
TypeScript 6.0 beta is now published!
This release brings
- inference improvements for functions
- updates to package.json 'imports'
- the Temporal APIs
- alignments for the upcoming TypeScript 7.0
- & more!
Try it today!
devblogs.microsoft.com/types…
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
GM!
Advent of slop (javascript) day 10. I find recursive solutions rather easy so I did that one pretty quickly. Despite not doing it after I woke up, still climbed up the tpot leaderboard (number 17 now)
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
When tsgo comes out this will end up being x214 times faster
Incredible stuff
We improved TypeScript types performance for Drizzle Relational Schema and Queries by ~x21.4 times
TS v5.8.3: 728.8k -> 34.1k
TS v5.9.2: 553.7k -> 25.4k
types instantiations for 3300 lines production drizzle schema + 990 lines relations
Turns out lower type instantiations are not always better, thus we played around with them to squeeze most real world performance and it is just instant now
Last but not least, you can now click to definitions in drizzle relations and db.query.table
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Override the default file download function with custom logic for authentication, retries, and caching.
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Node.js v22.19.0 is out now. ✨
Details: nodejs.org/en/blog/release/v…
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
A dev said they can’t live without public npm and I stand by whitelisting and knowing your fucking hashes.
Insecure interwebs is fucking a whore without a condom.
🚨 WARNING - 3.5M download npm package hijacked.
Attackers slipped malicious versions of Nx that stole GitHub + cloud creds, planted backdoors, and even weaponized AI tools like Claude & Gemini.
One of the first known supply chain hacks turning AI assistants into attack tools.
Here’s what devs need to know ↓ thehackernews.com/2025/08/ma…
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Reminder if you might have been affected, rotate all tokens IMMEDIATELY, especially the GitHub CLI Authorized OAuth, which isn't as straightforward. Our team is here to help via the community discord or [email protected].
🚨 If you think you might be effected by the nx compromise please revoke the GitHub CLI Authorized OAuth App: github.com/settings/connecti…
Notably, this is the only way to revoke/rotate the tokens made by/known to that app. The next time you `gh login` you can reauth.
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Node.js v24.7.0 is out 💚
Featuring:
- Post-Quantum Cryptography in node:crypto
- Modern Algorithms in Web Cryptography API
- Node.js execution argument support in single executable applications
And more details in our blog: nodejs.org/en/blog/release/v…
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Node.js can now execute TypeScript
nodejs.org/en/blog/release/v…
Official Node JS Teapot 🫖 (Bun, Deno, etc) retweeted
Node.js v24 is live, and 15 deprecations have reached end-of-life.
We want to hear from you: Which changes are causing the most issues for your projects during migration?👇
25%Removed modules
29%Deprecated APIs
32%Breaking changes
14%Other (tell us below!)
350 votes • Final results
































