Reposted by James SnellNico Kaiser @nico.kaiser.me · 6h📸 #NodeConfEU You know it's a real Italian conference when there's pineapple on the pizza. 🍍🍕🇮🇹 032
Reposted by James SnellNico Kaiser @nico.kaiser.me · 9h📸 #NodeConfEU @rafaelgss.dev & @aduh95.bsky.social: The New Node.js Release Model: Why Node 27 Changes Everything 0134
Reposted by James SnellNico Kaiser @nico.kaiser.me · 9h📸 #NodeConfEU @shogun-panda.bsky.social: FFI: Crossing the Native Boundary in Node.js 0133
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @addaleax.bsky.social: A Leak in the Shell — How Refactoring Autocomplete Broke Us and How We Fixed It 0101
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @jakob.jingleheimer.dev: What's the Tea? 0101
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @marcoippolito.dev: Rethinking HTTP in Node.js 082
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @bengl.dev: The Past, Present, and Future of Node.js Observability 1132
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU Mikola Lysenko: Delete all CVEs 081
James Snell @jasnell.me · 13hA Node.js API subset endorsed by WinterTC as being a minimal requirement for runtimes for interoperability. 000
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU Delicious Italian Lunch! 032
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @awad.dev: Tracing Without the Tax 0104
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU Lois Zhao: diagnostics_channel Deserves Better 0101
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @pipobscure.com: Ship the Tree 091
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @naugtur.pl: Getting ahead of supply-chain attacks in 2026 0172
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU Robert Nagy: NodeJS Performance Tips & Tricks 072
James Snell @jasnell.me · 29/09/2026If you're having some FOMO for @nodeconf.eu ... You can watch online! live.nodeconf.eulive.nodeconf.euNodeConf EU 2026 Live | Bologna, ItalyWatch NodeConf EU 2026 live from Bologna on 29-30 September. 275
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @jasnell.me: A common minimum Node.js subset for all runtimes 1131
Reposted by James SnellNico Kaiser @nico.kaiser.me · 29/09/2026📸 #NodeConfEU @nodeland.dev kicking off NodeConf EU 2026, Bologna, Italy. 0227
James Snell @jasnell.me · 26/09/2026In flight wifi is spotty so I'm writing code the old fashioned way. 2151
James Snell @jasnell.me · 26/09/2026If you're going to NodeConf.eu, drop me a message so I can get you added to the signal groupnodeconf.euNodeConf EU 2026 | Bologna, ItalyNodeConf EU 2026 returns to Bologna with tickets, venue info, and conference links in one fast single-page experience. 144
James Snell @jasnell.me · 26/09/2026This is the variation I'm gravitating towards... Especially witnessing bad behavior on all sides of the contribution pipeline. 1101
Reposted by James SnellSocket @socket.dev · 25/09/2026Maintainers spend countless hours keeping the open source projects we all rely on secure. Too often, that work is unpaid. Socket is proud to join @openjsf.org's new Security Stewardship Program to help fund the researchers and maintainers protecting Node.js. socket.dev/blog/openjs-...socket.devSocket Joins New OpenJS Program to Fund Node.js Security WorkSocket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases. 0237
James Snell @jasnell.me · 25/09/2026There's also a "Install to Home" app with the agenda available at nodeconf.eu/app You can get the live feed link there also.nodeconf.euNodeConf EU 2026 | Bologna, ItalyNodeConf EU 2026 returns to Bologna with tickets, venue info, and conference links in one fast single-page experience. 151
James Snell @jasnell.me · 25/09/2026If you're not able to join us in person at @nodeconf.eu in Bologna, Italy next week, please do try to join us remotely here live.nodeconf.eu ... every talk will be broadcast live with downloadable recordings available after.live.nodeconf.euNodeConf EU 2026 Live | Bologna, ItalyWatch NodeConf EU 2026 live from Bologna on 29-30 September. 0136
Reposted by James SnellNodeConf.eu @nodeconf.eu · 25/09/2026🥁 𝐒𝐩𝐞𝐚𝐤𝐞𝐫 𝐀𝐧𝐧𝐨𝐮𝐧𝐜𝐞𝐦𝐞𝐧𝐭🎙️ Thrilled to have @wunderacle.bsky.social on the #NodeConfEU 2026 stage! He'll be joining @brianmuenzenmeyer.com as a co-speaker to share the story behind "Replacing What Works: doc-kit and the Next 10 Years of Node.js Documentation." 🎟️https://www.nodeconf.eu 163
James Snell @jasnell.me · 25/09/2026The `why-is-node-running` (www.npmjs.com/package/why-...) module on npm is downloaded over 65.5 million times per week. It doesn't interrupt the process the way this does but it also isn't going to tell you about busy loops. Still, very surprising that it's 65.5 million times per week!npmjs.com 120
James Snell @jasnell.me · 25/09/2026Previously we would have to rely on OS-provided or external mechanism to shutdown the process which couldn't tell us why it was actually still open. 140
James Snell @jasnell.me · 25/09/2026Way overdue but Node.js is finally getting a `--process-timeout=N` cli flag that will force the process to exit with an explanation of why it was open. github.com/nodejs/node/... 2406
James Snell @jasnell.me · 25/09/2026@cloudflare.social "Birthday Week" is gonna have some really cool stuff. Can't wait. 180
Reposted by James SnellRemco Haszing @remcohaszing.nl · 24/09/2026LLMs are tools, not people. This means they are not authors either. They are not the author of your git commits, you are. It’s good to disclose if you used an LLM to make edits, but the commit author field is not the right place. That’s just a weird place to put an ad for the tool. 1275
James Snell @jasnell.me · 24/09/2026Random slides. Any topic. Pure nonsense. No preparation. Five minutes on the clock. 130
James Snell @jasnell.me · 24/09/2026For those attending @nodeconf.eu in person... Immediately following the social dinner the first night, we will be hosting a Slide Karaoke competition! Winner will be selected by the audience and will receive a prize. 1101
James Snell @jasnell.me · 24/09/2026There's also a mobile app view for the program you can install to your phone's home page. Provides offline access to the agenda. nodeconf.eu/app 010
James Snell @jasnell.me · 24/09/2026Less than a week away from @nodeconf.eu We hope you'll be able to join us in person in Bologna, but if you're just not able to make it, we will be streaming talks live throughout the two days. live.nodeconf.eu We also have a calendar you can subscribe to for the program: nodeconf.eu/program.icslive.nodeconf.euNodeConf EU 2026 Live | Bologna, ItalyWatch NodeConf EU 2026 live from Bologna on 29-30 September. 182
James Snell @jasnell.me · 22/09/2026The ability to calculate P90 threshholds, burn rates, detect regressions in-line while also providing more useful actionable data to APMs is powerful. Building it in makes it faster and less of a performance impact on the application itself. 000
James Snell @jasnell.me · 22/09/2026For those who may be watching... you may have noticed all the new performance analysis work I've been doing lately. This is really all intended to make zero-dependency perf analysis possible / more useful in general. Consider this example for instance: github.com/jasnell/fast...github.comGitHub - jasnell/fastify-sliding-health: An example using latest perf_hooks featuresAn example using latest perf_hooks features. Contribute to jasnell/fastify-sliding-health development by creating an account on GitHub. 181
James Snell @jasnell.me · 22/09/2026For cloud providers and electron, I can imagine a compile flag that omits it entirely. Electron is building node.js to embed anyway. That said, I think there's value in this for cloud providers also. Being able to surface more context in logs is useful. 010
James Snell @jasnell.me · 22/09/2026The key problem there is that man pages aren't supported on every OS that Node.js supports. Making it available for Linux/Unix users but leaving Windows users out seems wrong for something like this. 100
James Snell @jasnell.me · 22/09/2026Well put. DEI is essential, critical. We shouldn't have to defend it but unfortunately here we are. 0110
James Snell @jasnell.me · 22/09/2026... Not every error code has adequate documentation either. Examples of how they trigger, *good* explanations of what the error means, etc. The mechanism could also cover deprecation and warning codes 000
James Snell @jasnell.me · 22/09/2026I'm always happy to encourage others to contribute:-) There's some complexity here. The existing errors markdown doc would need to be refactored to avoid duplicating content and keep things in sync. The build would need to both compile in the descriptions and generate the doc... 100
James Snell @jasnell.me · 22/09/2026Several nice additions here. util.debounce(fn, ...) util.throttle(fn, ...) SlidingWindowHistogram More FFI, net, and vfs goodness nodejs.org/en/blog/rele...nodejs.orgNode.js — Node.js 26.10.0 (Current)Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. 1241
James Snell @jasnell.me · 21/09/2026Well, yes and no. The daemon process can bootstrap using preload `--require` modules, but once the fork happens each one is distinct and intentionally do not share the compile cache. 100
James Snell @jasnell.me · 21/09/2026So... back in 2017 we added error codes to Node.js. Today there are something like a couple hundred codes or so. They are all documented to some degree on the website but inconsistently. The question: should Node.js have a built in `node --explain ERR_CODE` that prints the detail similar to rustc? 7160
