Jan Martin

Files that use JavaScript import syntax but only work by compiling them to CommonJS or bundling them are called...

Vite+ is a unified CLI for JS for workflows like build, test, lint, format, deploy, etc. The news today is that (unlike previous plans) it's MIT and free 🎉 So how can it be sustainable? void.cloud will be a revenue-generating hosting service built on Cloudflare.

To everyone in my mentions like yOu NeEd tO UsE SkiLlS Suck on this vercel.com/blog/agents-md…

@eddie_oai @DavidKPiano @SumitM_X As shown, there are no interactions and the list is fully static. In which case there *is* nothing wrong with an index key. You can change the scenario and then it’s terrible of course. But static scenarios do exist.

@DavidKPiano @SumitM_X I really hope senior devs aren’t saying nothing! Indexes like this are terrible in practice especially if you have to interact with anything in that list, like for example deleting something.

Common React Interview question. What is the problem in this code ? export default function App() { const items = ["Apple", "Bat", "Cat"]; return ( <ul> {items.map((item, index) => ( <li key={index}>{item}</li> ))} </ul> ); }

Are there solutions for server-side enforcement of trusted types in React? Especially in the age of RSCs, that feels like a weird gap.

ECMAScript excitement 😉 Congrats to @guybedford on advancing Import Sync to Stage 2 at @TC39 today 🎉 const mod = import.sync(<specifier>); Like Node's require(<specifier>), it synchronously loads a module. It throws if sync loading is not possible.

ECMAScript excitement 😉 🚨🚨🚨 IT'S ABOUT TIME! 🚨🚨🚨 Congrats to @ManishEarth on shipping the Temporal API in Chrome 144 Stable today 🎉 #temporal" target="_blank" rel="nofollow noopener">developer.chrome.com/blog/new-in-ch… Temporal is the replacement for the Date API.

@ChristoPy_ @DavidKPiano If you happen to know every single combination of elements that will ever be on the same page, now and in the future, sure..? Otherwise, it’s generally a good habit to use identifiers that are definitely unique and not just “hopefully unique enough”.

@DavidKPiano Use static ids. Thank me later

react devs reinventing the wheel when what they need is to use DOM APIs that has been there longer than their age

I love that Google is helping save Tailwind. LLMs are trained on open-source projects. OSS gave the world so much. Hope more big tech companies do this.

I wonder if there’s a fun API for computation in adding ArrayBufferView-like Matrix and Vector types to JS that support mathematical operators. I’m 90% sure this wouldn’t fly in committee though. ^^

In node or anywhere else, really. Even in a larger web app it’s a risky foundation to build on.

@abiryanii @matteocollina @nodejs E.g. routes ending in specific suffixes may take precedent if they appear in specific positions in the list. So in the general case, you can’t use sub routers to “solve” the poor performance of a router based on list-of-regex.

@abiryanii @matteocollina @nodejs If you do that, you aren’t *really* using the API though. You’re describing something close to a trie router and that’s a great choice. But it’s not a transparent replacement because a typical URLPattern router is order-dependent and fundamentally ambiguous.

Quick remind to not use URLPattern in @nodejs, it would be painfully slow. adventures.nodeland.dev/archive/you-sh…

Holiday success: First iOS/tvOS game that kind of works. Vibe coded mess but I now get to read it and figure out how to make it slightly less jank.

Thank you @discord for supporting open source! Discord amazingly donated boosts and verified status to @nodejs @webpack and @electronjs. Super grateful for the Discord team for supporting us at @openjsf!

There’s some curious overlap between MCP Apps and RSCs. I think there’s a potentially nice DX in leveraging those parallels.

It’s happening! It’s not shiny but Trusted Types have a very real potential to be a game changer for the security of the web. Hopefully the beginning of a smoother story around actually using them. 🤞

@getifyX Thanks for the nudge! 🙌

I am literally in shock that a throw away comment I made on the end of a years long dead thread revived this and it lightning quick landed. This is almost unbelievable in a very good way. amazing!

PSA: There is a flag to disable the Function constructor vector entirely (`--disallow-code-generation-from-strings`). If you’re running nodejs in prod against untrusted inputs, it’s not a bad idea to set it. You can absolutely run real apps with that flag. #React2Shell

@justfly1984 @robpalmer2 If you’re happily using TS paths, none of this should break you. I would expect both the “bundler” and a future “node2Y” resolution mode in TS to support it, based on what happened in the past.

@robpalmer2 @hybristdev How about typescript Support? What if all my projects already using typescript paths?

Node excitement 😉 Congrats to @hybristdev on landing support for Package Imports that start with #/ 🎉 Previously this prefix was special-cased and would error. It's convenient to use it as an internal absolute path to the package root. import foo from "#/src/file.ts"

@colinhacks @KhafraDev @getifyX It’s certainly hit or miss but node can move fast when the stars align! It’s often worth to try, especially if you’re willing to step back when the effort/value ratio starts slipping.

@colinhacks @KhafraDev The PR shows pretty much all the process that went into it. The inciting incident was @getifyX reviving an old issue thread (#issuecomment-3564851409" target="_blank" rel="nofollow noopener">github.com/nodejs/node/is…) right at the same time that I got annoyed by `@/…` complicating my DB seed script for a demo.

package.json#imports have been practically unusable since they were introduced in 2020 because they didn't support top-level wildcards, e.g. "#/*" insanely, it turns out there was literally no reason for this and it was just never reconsidered after the initial PR