Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

publishing a TypeScript module to npm vs. to JSR

58,432 Aufrufe • vor 1 Jahr •via X (Twitter)

9 Kommentare

Profilbild von Substance Wizard
Substance Wizardvor 1 Jahr

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?

Profilbild von Andrei Bogdan | 🇷🇴 ☦️
Andrei Bogdan | 🇷🇴 ☦️vor 1 Jahr

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

Profilbild von lanre
lanrevor 1 Jahr

Dumb comparison

Profilbild von Joe Pea
Joe Peavor 1 Jahr

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:

Profilbild von Anubhav Gupta
Anubhav Guptavor 1 Jahr

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

Profilbild von Tùng 🇻🇳
Tùng 🇻🇳vor 1 Jahr

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?

Profilbild von Stephen Rayner
Stephen Raynervor 1 Jahr

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 ❤️🩸

Profilbild von marcaurele.eth
marcaurele.ethvor 1 Jahr

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 👍:

Profilbild von Jan Wilmake
Jan Wilmakevor 1 Jahr

There's still lot of room for improvement!

Ähnliche Videos