Thomas Jaggi
@thomasjaggi.bsky.social
Reposted by Thomas Jaggi
i know a lot of the javascript community thinks that people who complain about frontend complexity are just being cynical but it turns out that caking on layer upon layer of abstractions can have real-world consequences
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week.
These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
December 11, 2025 at 10:51 PM
i know a lot of the javascript community thinks that people who complain about frontend complexity are just being cynical but it turns out that caking on layer upon layer of abstractions can have real-world consequences
Reposted by Thomas Jaggi
terrific post, to which i'll add a couple of related thoughts. first: a lot of developers, especially juniors, tend to assume that other people's code is better than theirs, and so using a dependency (rather than a snippet) makes their codebase better
this is very much not the case
this is very much not the case
some thoughts about the bloat introduced by edge-case first libraries
The bloat of edge-case first libraries
How building edge-case first led to bloated, overly-granular libraries and what we can do about it
43081j.com
September 9, 2025 at 5:52 PM
terrific post, to which i'll add a couple of related thoughts. first: a lot of developers, especially juniors, tend to assume that other people's code is better than theirs, and so using a dependency (rather than a snippet) makes their codebase better
this is very much not the case
this is very much not the case
Reposted by Thomas Jaggi
Actually, Frankenstein is a doctor success at the Venice film festival
August 31, 2025 at 12:07 PM
Actually, Frankenstein is a doctor success at the Venice film festival
Reposted by Thomas Jaggi
Node excitement 😉
Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉
This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍
Many folk contributed 🙏
Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉
This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍
Many folk contributed 🙏
Type stripping is enabled by default 🔥🔥🔥🔥
You can just run `node file.ts` without `--experimental-strip-types` flag.
This is a huge milestone
You can just run `node file.ts` without `--experimental-strip-types` flag.
This is a huge milestone
Node.js 22.18.0 is out and enables type stripping by default – that’s right, Node.js LTS can now run TypeScript files. Shout out to @marcoippolito.dev for championing that effort! Download links and full changelog available at nodejs.org/en/blog/rele...
August 1, 2025 at 5:34 AM
Node excitement 😉
Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉
This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍
Many folk contributed 🙏
Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉
This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍
Many folk contributed 🙏
Reposted by Thomas Jaggi
This thread is incredible.
Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk)
.@Replit goes rogue during a code freeze and shutdown and deletes our entire database
xcancel.com
July 20, 2025 at 3:01 PM
This thread is incredible.
Reposted by Thomas Jaggi
Node.js can do more than you think.
Next week, it’s time to explore its multi-threaded power.
Together, at our @ZurichJS workshop.
June 18, 2025, 18:30 @ ORBIZ Josef, Josefstrasse 214a, 8005 Zürich 🇨🇭
We'll cover:
Next week, it’s time to explore its multi-threaded power.
Together, at our @ZurichJS workshop.
June 18, 2025, 18:30 @ ORBIZ Josef, Josefstrasse 214a, 8005 Zürich 🇨🇭
We'll cover:
June 15, 2025 at 3:18 PM
Node.js can do more than you think.
Next week, it’s time to explore its multi-threaded power.
Together, at our @ZurichJS workshop.
June 18, 2025, 18:30 @ ORBIZ Josef, Josefstrasse 214a, 8005 Zürich 🇨🇭
We'll cover:
Next week, it’s time to explore its multi-threaded power.
Together, at our @ZurichJS workshop.
June 18, 2025, 18:30 @ ORBIZ Josef, Josefstrasse 214a, 8005 Zürich 🇨🇭
We'll cover:
Reposted by Thomas Jaggi
I'm happy because this change means TypeScript defaults and Node defaults are converging 👍
Node does not support Import Elision which means it's important to enable "verbatimModuleSyntax"
vMS means the developer knows if an import statement/binding will be deleted - all via the `type` keyword.
Node does not support Import Elision which means it's important to enable "verbatimModuleSyntax"
vMS means the developer knows if an import statement/binding will be deleted - all via the `type` keyword.
TypeScript excitement 😉
Congrats to @searyanc.dev on landing big updates to the default tsconfig settings used by `tsc --init` 🎉
Defaults matter - and in TS 5.9 they embrace simplicity 💙
🔷 ESM (was CommonJS)
🔷 No down-leveling (was ES2016)
🔷 verbatimModuleSyntax: true
github.com/microsoft/Ty...
Congrats to @searyanc.dev on landing big updates to the default tsconfig settings used by `tsc --init` 🎉
Defaults matter - and in TS 5.9 they embrace simplicity 💙
🔷 ESM (was CommonJS)
🔷 No down-leveling (was ES2016)
🔷 verbatimModuleSyntax: true
github.com/microsoft/Ty...
tsc --init update by RyanCavanaugh · Pull Request #61813 · microsoft/TypeScript
Fixes #58420
Sample outputs
tsc --init
{
// Visit https://aka.ms/tsconfig to read more about this file
"compilerOptions": {
// File Layout
// "rootDir": "./sr...
github.com
June 7, 2025 at 10:44 AM
I'm happy because this change means TypeScript defaults and Node defaults are converging 👍
Node does not support Import Elision which means it's important to enable "verbatimModuleSyntax"
vMS means the developer knows if an import statement/binding will be deleted - all via the `type` keyword.
Node does not support Import Elision which means it's important to enable "verbatimModuleSyntax"
vMS means the developer knows if an import statement/binding will be deleted - all via the `type` keyword.