Songkeys
A guide for js library maintainer
I just read the Deno 2 release blog, and it really got me excited about joining this ecosystem! And as a library maintainer, I’d love to know the recommended guidelines. For instance, if I want to deliver a library, it seems like I should write it in the Node.js (npm) style since Deno is compatible with Node, but not the other way around. However, this might not be great news for the Deno ecosystem and its future development. We could also suggest that maintainers publish to both npm and JSR, but that would require extra effort and might not be worth it due to Deno's compatibility with Node. I might've missed something. Any clarification would be greatly appreciated! Thanks!
8 replies