Hacker GitHub

← All repos

nodejs/node

View on GitHub ↗ ★ 123,195 JavaScript

Node.js JavaScript runtime ✨🐢🚀✨

482 mentions on Hacker News by 376 people: 171 stories, 311 comments · first 2014-11-28 · latest 2026-11-01

Mentions per year 482 mentions · busiest year 2015 (96)
20082026
  1. …Here's someone trying to build steam parsing on Node and finding that it's too slow to be useful: https://github.com/nodejs/node/issues/31979 The solution is stream iterators. They are sync when they can be and async when they must be:…
    comment by conartist6 · 2026-11-01 · in The AI cost of JavaScript frameworks
  2. Other certificate verifiers are doing the same: Node: https://github.com/nodejs/node/pull/66871 rustls/webpki: https://github.com/rustls/webpki/pull/546 Electron: https://github.com/electron/electron/pull/55126 This is very serious and you…
  3. node is doing the same: https://github.com/nodejs/node/pull/66871
  4. …seem to have just merged in support for Web Workers though, which I've been following for a while: https://github.com/nodejs/node/issues/43583 So I don't think they're opposed to standardising, but it's trickier when you have some past…
  5. Node.js is virtually the only platform not supporting the Fetchable convention: https://github.com/nodejs/node/issues/63096 https://fetchable.org/
    comment by franciscop · 2026-08-19 · in Bun 1.4 Rust rewrite is not looking good?
  6. …compatible even in minor releases, and its compiler settings aren't portable for packages. [1]: https://github.com/nodejs/node/blob/main/doc/api/typescript.... [2]: https://www.assemblyscript.org/
  7. …bug with an almost identical fix: https://github.com/spaceraccoon/vulnerability-spoiler-alert/... https://github.com/nodejs/node/commit/53bcd114b10021c4a883b0... But now the interesting question, how does the code look like in Rust?…
  8. …that is distributed non-compiled (without dist/) and is supposed to run in both browser and Node. https://github.com/nodejs/node/issues/46006 https://github.com/microsoft/TypeScript/issues/16577
    comment by ivanjermakov · 2026-07-02 · in Vite+ Beta
  9. node randomly broke production for us last week https://github.com/nodejs/node/issues/63989 not sure it can be considered "stable and won't break things like this between minor releases"
    comment by Recursing · 2026-06-25 · in Deno 2.9
  10. …going to mention Node's `--experimental-transform-types`, but that was completely removed in v26: https://github.com/nodejs/node/pull/61803
    comment by Timon3 · 2026-06-22 · in Deno Desktop
  11. …Test 262: https://github.com/tc39/test262 For node that's its unit tests which are mostly JS: https://github.com/nodejs/node/tree/main/test Node also runs the web platform tests too: https://web-platform-tests.org/ Bun has a similar large…
  12. Node refuses to support TypeScript within node_modules, see https://github.com/nodejs/node/issues/58429 this means you can't do "Typescript-only npm packages". They made that intentionally at the beginning: > Currently there is consensus…
    comment by Ciantic · 2026-05-22 · in Deno 2.8
  13. …version, in v25.7.0 from February. Release notes: https://nodejs.org/en/blog/release/v25.7.0 Issue: https://github.com/nodejs/node/pull/61262
    comment by dieulot · 2026-05-21 · in Node.js 26.0.0 (Now with Temporal)
  14. Wait till you hear about https://github.com/nodejs/node/pull/61478
    comment by szmarczak · 2026-05-14 · in Rewrite Bun in Rust has been merged
  15. …drum roll please... node:Ffi! Really cool stuff. https://github.com/anomalyco/opentui/pull/939 https://github.com/nodejs/node/pull/62762 Also worth noting that opentui is... Zig! Very unclear what it's going to take to get this reviewed…
  16. …we might see older typescript features like enums slowly getting phased out. [0] https://github.com/nodejs/node/pull/61803
    comment by wartijn_ · 2026-05-05 · in Node.js 26 Released
  17. In Node 26 it will be removed https://github.com/nodejs/node/pull/61803
    comment by wartijn_ · 2026-05-05 · in I am worried about Bun
  18. …that approach that v8 takes and we've been able to deal with that just fine. Update on QUIC , https://github.com/nodejs/node/issues/57281 (2025).
    comment by ignoramous · 2026-04-14 · in OpenSSL 4.0.0
  19. …and likely modified code generated by an AI, you generated the code and hold the copyright. https://github.com/nodejs/node/pull/61478 https://blog.platformatic.dev/why-nodejs-needs-a-virtual-fil...
  20. Considering the many hundreds of technical comments over at the PR ( https://github.com/nodejs/node/pull/61478 ), the 8 reviewers thanked by name in the article, and the stellar reputations of those involved, seems likely.
    comment by joshkel · 2026-03-17 · in Node.js needs a virtual file system
  21. …is fine with the DCO on AI-assisted contributions. We’ll work on getting this documented. [1]: https://github.com/nodejs/node/pull/61478#issuecomment-40772...
    comment by syrusakbary · 2026-03-17 · in Node.js needs a virtual file system
  22. The submitted code must adhere to either of (a), (b), (c), and separately a (d) clause of: https://github.com/nodejs/node/blob/main/CONTRIBUTING.md#dev... If submitter picks (a) they assert that they wrote the code themselves and have…
    comment by indutny · 2026-03-17 · in Node.js needs a virtual file system
  23. yarn pnp is currently broken on Node v25.7+; - https://github.com/yarnpkg/berry/issues/7065 - https://github.com/nodejs/node/issues/62012 This is because yarn patches fs in order to introduce virtual file path resolution of modules in the…
    comment by Normal_gaussian · 2026-03-17 · in Node.js needs a virtual file system
  24. This reminded me to check, and now I'm happy to see Argon2 has finally made it into Node.js core! https://github.com/nodejs/node/issues/34452
  25. To be fair, nodejs has 36 open, 474 closed: https://github.com/nodejs/node/issues?q=Segfault
    comment by latchkey · 2025-09-20 · in Is Zig's new writer unsafe?
  26. https://github.com/nodejs/node/issues/57215 Not supporting type stripping in node_modules is unfortunate
  27. ljharb has commit rights (edit: maybe? maybe not. not sure) to nodejs itself https://github.com/nodejs/node/issues/55918 so.. I don't know. if he wanted to bad he would already
    comment by karel-3d · 2025-08-08 · in Cursed Knowledge
  28. There is a PR open since June. It's currently blocked by a MacOS CI issue. https://github.com/nodejs/node/pull/58491
  29. https://github.com/nodejs/node/pull/58517 - I think the `semver-major` and the timing mean that it might not be available until v25, around October
    comment by tchetwin · 2025-08-04 · in Modern Node.js Patterns
  30. …require some transpilation as well [1]: https://nodejs.org/en/learn/typescript/run-natively [2]: https://github.com/nodejs/node/pull/58643
  31. …lacks something like `assert.any()` to match object in `deepEqual`. So I still need to use vitest. https://github.com/nodejs/node/issues/55319
    comment by Aldipower · 2025-07-11 · in Modern Node.js Patterns for 2025
  32. …to do quic, ignoring input. But that's finally starting to move. https://github.com/hyperium/h3 https://github.com/nodejs/node/issues/57281 Muxio was able to define itself & an inpl pretty fast, and performance & usability are probably…
    comment by jauntywundrkind · 2025-07-01 · in Muxio: Rust layered stream and RPC toolkit
  33. There's a fair bit of work to do if we want to retire some of these C programs: https://github.com/nodejs/node https://github.com/mozilla-firefox/firefox https://github.com/torvalds/linux https://github.com/python/cpython
  34. …so much of this work has been done for Node & there's just no straightforward path forwards. https://github.com/nodejs/node/issues/57281
    comment by jauntywundrkind · 2025-03-17 · in HTTP/3 is everywhere but nowhere
  35. …things, but even on a LTS release of node they released a [build where utf+8 strings were broken]( https://github.com/nodejs/node/issues/54543 ) and our builds were failing silently.
  36. …Go https://github.com/golang/go/blob/master/src/runtime/Makefil... NodeJS https://github.com/nodejs/node/blob/main/Makefile OCaml https://github.com/ocaml/ocaml/blob/trunk/Makefile Python https://github.com/python/cpython/blob/main/
    comment by dumah · 2025-01-31 · in A better build system for OCaml
  37. …it ...BUT on the other hand, node.js for example has released support for it already in June 2024: https://github.com/nodejs/node/issues/51562
  38. …valid to conclude a real world performance increase? one possible confounder is the version of V8. https://github.com/nodejs/node/blob/v18.x/deps/v8/include/v8... https://github.com/nodejs/node/blob/v20.x/deps/v8/include/v8... ideally,…
    comment by Cicero22 · 2024-12-24 · in Parsing millions of URLs per Second (2023)
  39. …mocking as of today. I switched to Vitest because Jest was giving me flaky coverage results: https://github.com/nodejs/node/issues/51251 And while Vitest' coverage is stable, I had to add an indirection layer to change how I mock out calls…
    comment by OptionOfT · 2024-11-26 · in Vitest vs. Jest
  40. …would've used it (perhaps using `y.finally()`) which would have solved the memory leak. [1] https://github.com/nodejs/node/issues/17469#issuecomment-349...
    comment by throwitaway1123 · 2024-11-23 · in Playground Wisdom: Threads Beat Async/Await
  41. …like to see TC39 standardize this [3]. [1] https://issues.chromium.org/issues/42213031#comment5 [2] https://github.com/nodejs/node/issues/17469#issuecomment-349... [3] https://github.com/cefn/watchable/tree/main/packages/unpromi...
    comment by throwitaway1123 · 2024-11-23 · in Playground Wisdom: Threads Beat Async/Await
  42. …if a promise never gets resolved, it will stick around forever. It's braindead, but it's the spec: https://github.com/nodejs/node/issues/17469
  43. …practically requires a 3rd party HTTP client. Or Java that doesn't even have JSON support. [1] https://github.com/nodejs/node/tree/main/lib
    comment by paulddraper · 2024-11-22 · in The tragedy of running an old Node project
  44. …wrong. It absolutely is a thing and it has been in your browser and Node for longer than a year. https://github.com/nodejs/node/pull/48518 https://github.com/tc39/proposal-explicit-resource-managemen...
    comment by sureIy · 2024-11-18 · in Web Locks API
  45. …418 status code from different languages and implementations because it wasn't technically correct. https://github.com/nodejs/node/issues/14644 https://github.com/golang/go/issues/21326 And someone even ended up making a website…
    comment by 0x00cl · 2024-10-28 · in 418 I’m a teapot
  46. …work to get everybody on the same page (About my previous example, it's not well engaged by example https://github.com/nodejs/node/issues/55419 ), but when done and right done, it's a huge win for developers. PHP PSR, RFC & co are the way.
  47. …Which tells me literally nothing about this "notable change", unless I go to the pull request: https://github.com/nodejs/node/pull/52535 > module: implement NODE_COMPILE_CACHE for automatic on-disk code caching #52535 Which still doesn't…
    comment by shortrounddev2 · 2024-10-16 · in Node.js – v23.0.0
  48. …`select` statement. Turns out that in JS it is actually useless because it LEAKS MEMORY BY DESIGN: https://github.com/nodejs/node/issues/17469 Back to the article. It uses pre-generics Go. In more modern Go, you can use something like Conc…
    comment by cyberax · 2024-10-04 · in Go Concurrency vs. RxJS
  49. At least Node.js has added experimental support that seems to do that: https://github.com/nodejs/node/pull/53725 But this is just an on-the-fly transpile(natively supported). It would be much better if JavaScript would go the Python route.…
  50. …Kubernetes when Node 20 had enabled it by default. They scrambled and turned it off by default in https://github.com/nodejs/node/commit/686da19abb
    comment by watt · 2024-09-24 · in What Is Io_uring?