How to publish a JavaScript package in 2024

Originally broadcast as part of Future Frontend 2024: • Future Frontend 2024 D...
00:00 Intro
01:09 Publishing JS package with npm is complicated
03:05 Why is npm so bad?
05:25 How JSR addresses shortcomings of npm
08:00 First class TypeScript support
11:22 JSR is a superset of npm
12:04 JSR is runtime agnostic
12:52 JSR is secure and auditable
13:41 JSR generates docs automagically
14:07 JSR scores packages
15:28 Luca shows JSR website
17:35 Luca publishes a new package to JSR
27:35 Luca installs a new package from JSR
33:00 How auto-generated docs works
34:15 Luca publishes a package to JSR from GitHub
Resources:
- JSR: jsr.io
- Introducing JSR: deno.com/blog/jsr_open_beta
- How we built JSR: deno.com/blog/how-we-built-jsr
- JSR is not another package manager: deno.com/blog/jsr-is-not-anot...
- How to document your JavaScript package: deno.com/blog/document-javasc...
Website: deno.land
GitHub: github.com/denoland
Discord: / discord
Twitter: / deno_land

[@felipezarco9502]

I loved JSR, I believe it will grow to be the reference registry eventually!

[@cg219]

Nice demoLuca!

[@93pnmx]

Excellent speaker, enjoyed his talk

[@sle6423]

Love it!

[@benheidemann3836]

I recently published my first package to JSR… and the my second, and third, and fourth 😅

[@deno_land]

haha amazing!

[@javadbat3364]

it's working with your package but what happens when you need to use react or when we need our custom build. for example, in my web-component design system, I need to import ".HTML" or ".scss" files or even ".svg" files and I need rollup with plugins to build and bundle them. how should I handle this by jsr. can I have my own build tools or can you publish some rollup package to help us bundle our deno code to packages?

[@Insane430]

🦕

[@m.jeremy1375]

don't understand if deno handle monorepo (only with deno stuff)

[@benheidemann3836]

Deno does support monorepos 👍

[@m.jeremy1375]

@@benheidemann3836 only for deno. with npm/bun I look the doc but very painfull to understand.

[@AadityaSinghVohra-wf9lu]

Aint deno started with NPM is bad as its centralized, what is the justification now that it needs a registry itself?

[@thijskoerselman]

watch the video?

[@cotyhamilton]

It’s a registry for every js runtime and it’s open source

[@benheidemann3836]

As I understand, that was one of several initial motivations for Deno. But JSR is not the Deno repository, it’s the JavaScript repository. Deno can still import from URL and whatever else. Though I think Ryan Dahl did also acknowledge the need for a centralised package manager, which is pretty reasonable - you don’t always need to be 100% right about everything from the start 😊

[@Caldaron]

can't run npx on a jsr package...

[@olatrials]

"npx jsr run " or "npx jsr " would be the equivalent.

[@mattvr]

so much better than npm

[@Gengurke]

🦕🦕🦕🦕

[@inononeeee]

jsr docs are easy to understand

[@BinaryReader]

I am not interested in TS documentation generation ... this is not interesting nor is it an innovation (other languages have had this for decades). I am also not interested in being scored on the amount of superfluous comments I can slap on my code. I am ONLY interested a Node compatible publishing system that supports TS modules. Everything else is window dressing....

[@lucacasonato-deno]

Well, I'm happy that you like JSR :)

[@sebastienringrose5440]

It's true that these features may not hit home for devs familiar with the territory but consider learners entering the community; validating that a package can explain itself before jumping into it could be very comforting.

[@the_inalienable_dreamless]

"a new javascript registry". for how long now has it been """""new"""""?