Thomas Jaggi

Thomas Jaggi

@thomasjaggi.bsky.social

https://social.thomasjaggi.ch/@thomas

36 followers90 following23 posts

Thomas Jaggi reposted

Man why are all these well-loved tech companies so desperate to give their money to Mr Kill All Immigrants in exchange for his dotfiles

Thomas Jaggi reposted

Thomas Jaggi reposted

Thomas Jaggi reposted

its great seeing npmx as an output for a lot of the data and tools we have inside e18e visibility of these things goes a long way to helping the wider community improve their own projects very nice having a place to output this npmx 🤝 e18e💙

9romise@9romise.bsky.social

@e18e.dev's module-replacements in VS Code 👀 Powered by `vscode-npmx` — get modern package alternatives right in your editor. Try it out: 👉 marketplace.visualstudio.com/items?itemNa... Would love to hear your thoughts!

Thomas Jaggi reposted

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

React@react.dev

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.

Thomas Jaggi reposted

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

Thomas Jaggi reposted

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 🙏

Marco Ippolito@marcoippolito.dev

Type stripping is enabled by default 🔥🔥🔥🔥 You can just run `node file.ts` without `--experimental-strip-types` flag. This is a huge milestone

Thomas Jaggi reposted

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:

Thomas Jaggi reposted

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.

Rob Palmer@robpalmer.bsky.social

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...

You are up to date.