Content
@
0 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
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
5 replies
6 recasts
20 reactions
Marc
@marcgarcia.eth
I really hope that all the uwebsocket drama gets fixed soon đ€
1 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
Say more đ
1 reply
0 recast
0 reaction
Marc
@marcgarcia.eth
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
1 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
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.
1 reply
0 recast
0 reaction
Marc
@marcgarcia.eth
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 đ
1 reply
0 recast
0 reaction
Darryl Yeo đ ïž
@darrylyeo
`pnpm patch` saved my life on more than one occasion. Still waiting for bun to add it.
1 reply
0 recast
0 reaction
Marc
@marcgarcia.eth
not sure if it's the same or not, but patch-package is supported in bun if you use "bun install --yarn". Tried it rn and it works, you can patch and even install postinstall patches https://github.com/ds300/patch-package/issues/489
1 reply
0 recast
0 reaction
