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?
https://t.co/9zui79l7gD will be a revenue-generating hosting service built on Cloudflare.
@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.
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 🎉
https://t.co/qDQIQvB0TW
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”.
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. ^^
@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.
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!
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. 🤞
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.
@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 (https://t.co/ypzmSJd8SY) right at the same time that I got annoyed by `@/…` complicating my DB seed script for a demo.