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

All the packages in the Deno Standard Library:

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

All the packages in the Deno Standard Library:

https://jsr.io/@std

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T>

It appears the era of TypeScript is upon us. Exciting stuff. Many years in the making.

Shit's getting real!

This is no small thing in terms of major quality boost to the ESM/Typescript ecosystem, eh?  All of it: deno, jsm, the goodies keep coming.

Engineering @neynar. Amusement, wonder, and uncertainty ✴︎ libred.org

For all of its flaws, the JavaScript ecosystem’s dedication to interoperability is pretty amazing.

deno stdlib rocks and nicely presents merits of deno.
Deno making it available on npm reminds me of a Trojan horse story :)

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

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