Loading video...

Video Failed to Load

Go Home

publishing a TypeScript module to npm vs. to JSR

58,432 views • 1 year ago •via X (Twitter)

9 Comments

Substance Wizard's profile picture
Substance Wizard1 year ago

I might be stupid for suggesting this, but wouldn't it just be faster to stay in vscode and type faster so you don't have to switch tabs?

Andrei Bogdan | 🇷🇴 ☦️'s profile picture
Andrei Bogdan | 🇷🇴 ☦️1 year ago

npm looks fun, thanks for sharing this I was kinda bored of jsr

lanre's profile picture
lanre1 year ago

Dumb comparison

Joe Pea's profile picture
Joe Pea1 year ago

Hello! I see JSR support Firefox, Chrome, Safari, etc, but when I look at a package, it is missing the instructions for importing to any browser:

Anubhav Gupta's profile picture
Anubhav Gupta1 year ago

Hey, one thing that is not clear to me, how did JSR knew that the file name was mod.ts?

Tùng 🇻🇳's profile picture
Tùng 🇻🇳1 year ago

publishing is failing intermittently. I know this is still a beta thing, but the act of publishing involves 3 separately moving parts: the npm jsr cli, the deno runtime and the remote server. Do you have a story for end-to-end testing prior to general availability?

Stephen Rayner's profile picture
Stephen Rayner1 year ago

It’s not ready, we’re with you on this but needs more work. Collect user feedback. Get @t3dotgg to shit all over it with his live stream chat. And then incorporate into roadmap ❤️🩸

marcaurele.eth's profile picture
marcaurele.eth1 year ago

Is it possible to publish the same package to both @jsr_io and @npmjs? Loving the progress @deno_land is making with V2.0 and its awesome #NPM support! It would be great to have an easy way to publish to both platforms. If @lernajs added #Deno support, it’d be a huge win for #devEX. I’ve made a feature request, feel free to 👍:

Jan Wilmake's profile picture
Jan Wilmake1 year ago

There's still lot of room for improvement!

Related Videos