Загрузка видео...

Не удалось загрузить видео

На главную

publishing a TypeScript module to npm vs. to JSR

58,432 просмотров • 1 год назад •via X (Twitter)

Комментарии: 9

Фото профиля Substance Wizard
Substance Wizard1 год назад

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 | 🇷🇴 ☦️
Andrei Bogdan | 🇷🇴 ☦️1 год назад

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

Фото профиля lanre
lanre1 год назад

Dumb comparison

Фото профиля Joe Pea
Joe Pea1 год назад

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
Anubhav Gupta1 год назад

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

Фото профиля Tùng 🇻🇳
Tùng 🇻🇳1 год назад

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
Stephen Rayner1 год назад

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
marcaurele.eth1 год назад

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
Jan Wilmake1 год назад

There's still lot of room for improvement!

Похожие видео