Frontend

Deno split its Standard Library into individual packages and published them all to the JSR package registry.

This also means you can install them with npm and use ~70% of them within Node.js projects 🤯

Deno split its Standard Library into individual packages and published them all to the JSR package registry.

This also means you can install them with npm and use ~70% of them within Node.js projects 🤯

https://deno.com/blog/std-on-jsr

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

I really hope that all the uwebsocket drama gets fixed soon 🤞

Barcelona based developer. I enjoy comics, gaming and sci-fi

https://www.npmjs.com/package/uws

https://unetworkingab.medium.com/beware-of-tin-foil-hattery-f738b620468c

hence the pkg is not on npm, and that causes deno to break on some libs that use uws.

Had to put on hold some projects because thirdweb, viem etc use uws

Really it is. Sometimes to change the runtime you have to replace hundreds of lines or even make weird hacks to fill gaps. Maybe with AI in the future 😅

Oof. Interoperability is such a hard problem. I’m glad the ecosystem is getting more platform-agnostic tools so we don’t all have to rely on a single service like npm.