@@mattymattffs, no, these are issues that inexperienced web developers that were born before 2000 created for themselves. Those of us that lived during the start of the internet, in the 90's, don't have this problem.
i just tried publishing an existing package I had. it's almost irritating how easy that was. thank god I no longer have to deal with separate tsconfig for esm and cjs, different build commands for esm and cjs, manually specifying the exports field, etc.
What I like about JSR is the fact that you _can_ have a build step. Not having one is fine for most packages, but when working with wasm packages it’s especially useful
Why so? Do you mean specifically for dev dependencies, so you don't have to ship binaries for all different architectures? Or does it also help to have a build step if it needs to be shipped to the client, and I'm missing something?
Well, the registry server is open source, so it is well on its way to supporting that. Just need deno to be able to pull from multiple regstres. Getting interop with NPM for private registries may be the hard part. (Or not. Just a guess.)
Ultimately people will still want to publish to npm for full compatibility and reach. Will JSR automate this by allowing mapping to an npm repository or namespace? Or do we need to handle both publishing steps ourselves, therefore re-adding some of the pain that jsr is trying to prevent.
Would have been nice to dive into the details of node_modules. I'm curious when transpilation occurs - does it happen when a package is published or when a package is installed?
This needs strict semver controls too. If a package author changes an interface in a breaking manner, they should not be allowed to bump minor or patch.
Non agentic (direct LLM) AI has flagged your patch as potentially breaking, which is not allowed for approved packages. Your patch is now pending human and agentic AI review. Please approve immediately starting the review process, or cancel the patch if the changes are breaking to avoid reputation damage
I need JSR to do 2 things: 1. automatically compile my library for NPM 2. Support typescript using a separate definitions file. Any idea if thats possible or will be possible soon?
JSR already automatically compiles your library for npm. JSR offers first class TypeScript support - you can publish your TypeScript source code, and it'll automatically generate .js/.d.ts files for npm users. Did that answer your question?
@@deno_land you only answered the first half of my question. My second question is if I can use my vanilla source code with a separate type definitions file inside of JSR. Thank you 🙂
That’s going to help push the Deno philosophy regarding package management. Given that people want to eject npm from node, this makes a lot of sense. Specifically because Microsoft acquired it.
Would be awesome to have "chat jsr" where you can talk about what things you want to achieve and it recommends packages suitable for that. Or a page where you can sort packages by category. Blog about packages that everyone should use is also would be welcome.
Then what about the time?? should we keep the minutes first and then the hour and then the seconds or the seconds the hours and then the minutes… obviously 🙄 people who don’t know how to do things will always be ready to fight and pragmatic people will be able to enjoy 😉 I think it’s the best thing ever he has converted me into the deno in such a short time frame (well if we start to calculate it from the 2.0 version it got me exactly when his feet touched the ground)🎉🎉🎉🎉
here's a thought- add a 'comments' tab or similar? even if moderated by the publisher, would it risk being too much like github with something like that?
12:37 Mh. I wish that is different. There is no shame in monetizing and doing open source at the same time. A monetized project has a much healthier long term outlook, than one where the people behind it are simply waited for be eventually burned out. I hope this project succeeds
think it’s the best thing ever he has converted me into _the deno_ in such a short time frame (well if we start to calculate it from the 2.0 version it got me exactly when his feet touched the ground)🎉🎉🎉🎉 you know it will be successful because if we just think about it… one can’t say that Ry! don’t know what he is talking about!!!
I think it's fine if we defer the build process into the registry and we're all can have it working in our different runtimes that this registry support. pretty neat
i didn't see how you solve the issue, when i can push some shit into my package as a path version and someone pull it automatically trough npm/jsr. it's a headake when a contributor pull dirty code and i pull it with npm install command. i think you make your own name, not frontend
Good thing about NPM is that it evolves as the ecosystem does. Yarn tried to replace it and they implemented the missing features that added yarn such as workspaces and same speed optimizarions. Now this is game changer as well, but I don’t see it becoming a standard anytime at all. NPM is probably implementing this publish flow and we wont need another technology in our stack
Thank you! Very attractive Few questions 1. is it possible to validate a module and get recommendations to increase score before actually publishing a module ? 2. If one is looking for a module should they specifically be searching in jsr, how well jsr is indexed ? does it appear in search results as well as npm does, if one is searching in npm would be great if it would search both npm and jsr?
We're currently working on the ability to calculate your score from your command line before publishing. github.com/jsr-io/jsr/issues/199 If you're looking for a module on JSR, you should search for it in JSR. right now you can't find JSR packages by searching in npm.
I would like to know what Bun stuff is coming to Deno. i really don't know what things bun has lol, but speed is always mentioned and you can't say that more speed doesn't sound nice. so are you guys planning to improve the performance in Deno? I haven't used Deno either but the metrics that Bun always shows seem to be far above anything else. Thanks
Hey, Deno's performance is on par or exceeding Bun's performance in many benchmarks. Both Deno and Bun are often significantly faster than Node at executing code.
@@lucacasonato-deno I have the feeling that Bun has been selling the idea that it is x2 x3 x50 x100 faster than all the other alternatives. For example I have heard that it is super fast as a package manager. I have also seen some benchmarks shared by the creator of Elysia. What do you think? Thanks
if you're worried about performance you should not be using javascript to begin with. these runtimes are fast relative to javascript but they're nothing compared to go or rust. the benchmarks they use are hello world programs. in real applications they're far behind. i've done the benchmarks myself.
But it was created after _October 2023_ and my *best friend,* who knows everything about anything have no clue about what happened after that cut off date 😅
@@xpynim bro use whatever suits you best, both bun and deno can be annyoing and have silly bugs so read a bit more on "is bun/deno good for {whatever you're working on}"
15:30 the entire npm in a nutshell, you have one function to write that does one thing and you still chose to use a library that has a oneliner for your whole package !
Should have been called TSR (Typescript Repo) 😁 By the way, this new TH-cam layout sucks. First thing they can do is make the title font size smaller so you can actually see it. Congrats on the project. Looks rad
A shame that this JSR transition completely shafts the URL based paradigm/ecosystem they were previously pushing. Deno had shown again and again that it is ultimately vcware and all these walkbacks and general instability has made it a pain to build on.
I love the way Ryan talks about issues devs have on a day to day, and even presents the solution to developers; not marketers.
These are issues that web developers have created themselves.
@@mattymattffs, no, these are issues that inexperienced web developers that were born before 2000 created for themselves.
Those of us that lived during the start of the internet, in the 90's, don't have this problem.
i just tried publishing an existing package I had. it's almost irritating how easy that was. thank god I no longer have to deal with separate tsconfig for esm and cjs, different build commands for esm and cjs, manually specifying the exports field, etc.
should have been called jdsl, because it's genius
Tom is a genius.
Prime has achieved indirect reference status 😊
Love me some jdiesel
😂😂😂❤
Primal reference
i used a jsr package earlier today without knowing what jsr is, and then youtube recommended me this and i'm mind blown.
this is amazing.
You should be worried 😟
Deno is killing it
it is quite literally what is happening… 😅😅😅
Hooray for floating head man and his creation
now that you called him that i cannot (un)see it
I hope that the Node and Bun communities adopt this standard.
without alternate uses of TypeScript is bad
I hope not. It will ironically complicate crap even further
@@bob_kazamakis Why? Isn't that entirely dependent on implementation?
Bun > Deno
@@bob_kazamakiscan you specifically state what will make it worse?
Love that rotational symmetry in the logo
And the fact that it looks similar to npm logo... Excellent job, whoever designed the logo
the fact that he has seen the light of the one true way of writing dates convinced me to use deno
This is incredible! I really hope JSR becomes the default way to publish and consume packages with JS
as long as it doesnt start demanding TS from team vanillaJS
@@julsiushe literally said it does not
stripping TS is pretty easy
I love the work Ryan and Deno is doing, and JSR seems to be right there with all the other awesome tools from them
What I like about JSR is the fact that you _can_ have a build step. Not having one is fine for most packages, but when working with wasm packages it’s especially useful
Why so? Do you mean specifically for dev dependencies, so you don't have to ship binaries for all different architectures? Or does it also help to have a build step if it needs to be shipped to the client, and I'm missing something?
@@some.handle I don't want to push big wasm files into my github repo :)
Love the attitude of Ryan to technical issues and how to improve things!
Can't wait for Primeagen to call this "JIZZER"
best timeline
oh no
Cringe.
underrated
@@KushLemon 🤡
I am extremely eager for private registries/packages. I want to try using this for work.
Well, the registry server is open source, so it is well on its way to supporting that. Just need deno to be able to pull from multiple regstres. Getting interop with NPM for private registries may be the hard part. (Or not. Just a guess.)
Ultimately people will still want to publish to npm for full compatibility and reach. Will JSR automate this by allowing mapping to an npm repository or namespace? Or do we need to handle both publishing steps ourselves, therefore re-adding some of the pain that jsr is trying to prevent.
Amazing work! I'm glag to see this new generation of registry!
Soooo cool, transpiled code has been killing me recently trying to figure out what some code was meant to do vs actually doing, long live TS!😊
Would have been nice to dive into the details of node_modules. I'm curious when transpilation occurs - does it happen when a package is published or when a package is installed?
feels awesome seeing the creatorman playing around with all his creations, glad to know I'm using them correctly
This needs strict semver controls too. If a package author changes an interface in a breaking manner, they should not be allowed to bump minor or patch.
Non agentic (direct LLM) AI has flagged your patch as potentially breaking, which is not allowed for approved packages. Your patch is now pending human and agentic AI review. Please approve immediately starting the review process, or cancel the patch if the changes are breaking to avoid reputation damage
Petition to rename "denoland" to "Jerassic Park"
Not sure why they didn't erupt in applause when he finished uploading the module. I would've gone nuts. That was so easy
13:52 Japanese: 2024-12-31
this way you can have nesting directories that make sense.
and sorting that makes sense too
This video should be republish with minimum 1080p resolution, as is demoing some code, the code written looks blurry!
Yeah it's 2024. 720p isn't acceptable.
Deno is like oxygen , no more dizzying setups
I need JSR to do 2 things: 1. automatically compile my library for NPM 2. Support typescript using a separate definitions file. Any idea if thats possible or will be possible soon?
JSR already automatically compiles your library for npm. JSR offers first class TypeScript support - you can publish your TypeScript source code, and it'll automatically generate .js/.d.ts files for npm users. Did that answer your question?
@@deno_land you only answered the first half of my question. My second question is if I can use my vanilla source code with a separate type definitions file inside of JSR. Thank you 🙂
@@ob4816 Yes this is possible.
Can you upload it in 4K resolution?
Now I know the right date format, I keep use this for versioning.
Great initiative 🎉
What about minifying the library, and build step of the same library compared npm vs jsr?
Why cant the user decide if they want to minify
@@xyangst why wouldn’t they want it and ship less mb to their customers?
@@mr.komp1004 bcs its nice to look at source code of the libaries ur using
That’s going to help push the Deno philosophy regarding package management. Given that people want to eject npm from node, this makes a lot of sense. Specifically because Microsoft acquired it.
Would be awesome to have "chat jsr" where you can talk about what things you want to achieve and it recommends packages suitable for that. Or a page where you can sort packages by category. Blog about packages that everyone should use is also would be welcome.
Can we use this without GitHub ?
I agree 100% with Ryan - this is the only valid way to format date. End of discussion.
Then what about the time?? should we keep the minutes first and then the hour and then the seconds or the seconds the hours and then the minutes… obviously 🙄 people who don’t know how to do things will always be ready to fight and pragmatic people will be able to enjoy 😉 I think it’s the best thing ever he has converted me into the deno in such a short time frame (well if we start to calculate it from the 2.0 version it got me exactly when his feet touched the ground)🎉🎉🎉🎉
Sounds game changing!
Ryan! always making our lives much easier!
here's a thought- add a 'comments' tab or similar? even if moderated by the publisher, would it risk being too much like github with something like that?
this seems like such a big todo for the 6502 "Jump to SubRoutine" opcode introduced in the 1970s
This is amazing ! I want private github modules with this
12:37 Mh. I wish that is different. There is no shame in monetizing and doing open source at the same time. A monetized project has a much healthier long term outlook, than one where the people behind it are simply waited for be eventually burned out. I hope this project succeeds
Here we go awain, another technology that recruiters won't know even how to spell and ask for 5 years of experience on it
think it’s the best thing ever he has converted me into _the deno_ in such a short time frame (well if we start to calculate it from the 2.0 version it got me exactly when his feet touched the ground)🎉🎉🎉🎉 you know it will be successful because if we just think about it… one can’t say that Ry! don’t know what he is talking about!!!
I think it's fine if we defer the build process into the registry and we're all can have it working in our different runtimes that this registry support. pretty neat
9:53 - "JSR requires a GitHub login unless you use GitHub Actions, in which case you can use OpenID Connect authentication."
Articulation of pain points around ts/js esm tsc is on point. Nobody wants to mess with that
i didn't see how you solve the issue, when i can push some shit into my package as a path version and someone pull it automatically trough npm/jsr. it's a headake when a contributor pull dirty code and i pull it with npm install command.
i think you make your own name, not frontend
so how does npm know what to do with jsr: ?
This looks fantastic. I hope this takes off.
This talk inspired me to write a library. Thanks Ryan.
And I was there to see it :)
Same :)
Good thing about NPM is that it evolves as the ecosystem does. Yarn tried to replace it and they implemented the missing features that added yarn such as workspaces and same speed optimizarions. Now this is game changer as well, but I don’t see it becoming a standard anytime at all. NPM is probably implementing this publish flow and we wont need another technology in our stack
that sounds horrible
Google says you are talking about Java Specification Requests? ;)
Thank you! Very attractive
Few questions
1. is it possible to validate a module and get recommendations to increase score before actually publishing a module ?
2. If one is looking for a module should they specifically be searching in jsr, how well jsr is indexed ? does it appear in search results as well as npm does, if one is searching in npm would be great if it would search both npm and jsr?
We're currently working on the ability to calculate your score from your command line before publishing. github.com/jsr-io/jsr/issues/199
If you're looking for a module on JSR, you should search for it in JSR. right now you can't find JSR packages by searching in npm.
If I don't want my source code to be open in my distribution is that possible?
minify it yourself lol
does it work on cloudflare as a backend instead of s3 ?
jet set radio is cool yeah
Came here to say this lol. First thing I thought when I read that.
Another good work from ryan, tnx
When is JSR replacing NPM?
Why brilliant minds are so fit
Absolutely fantastic...
I like how it works with Bun.
gonna use one-true-date soon
27:32 Prime mentioned
I would like to know what Bun stuff is coming to Deno. i really don't know what things bun has lol, but speed is always mentioned and you can't say that more speed doesn't sound nice. so are you guys planning to improve the performance in Deno? I haven't used Deno either but the metrics that Bun always shows seem to be far above anything else. Thanks
Hey, Deno's performance is on par or exceeding Bun's performance in many benchmarks. Both Deno and Bun are often significantly faster than Node at executing code.
@@lucacasonato-deno I have the feeling that Bun has been selling the idea that it is x2 x3 x50 x100 faster than all the other alternatives. For example I have heard that it is super fast as a package manager. I have also seen some benchmarks shared by the creator of Elysia. What do you think? Thanks
if you're worried about performance you should not be using javascript to begin with. these runtimes are fast relative to javascript but they're nothing compared to go or rust. the benchmarks they use are hello world programs. in real applications they're far behind. i've done the benchmarks myself.
@@matress-4-2323 i'm not worried i'm just curious. i like node.js
Top 2 comments are about a TH-camr. We're finally in the goofiest timeline 😌
Hot take: Is JSR already outdated by Framework X released 3 hours ago?
Maven Central has 13,833,950 indexed packages, a lot more than the 2 million in npm
But it was created after _October 2023_ and my *best friend,* who knows everything about anything have no clue about what happened after that cut off date 😅
14:28 i am here for this
yyyy-MM-dd
16:29 yes
This looks amazing and extremely exciting
Truly an awesome talk.
Haha, the solution to all the clutter ... is another overlay ... not sure what's going on with these guys.
Love this!
Thanks Ryan, this looks awesome 🎉🎉🎉
If we're getting go to definition and seeing full TS source with comments, won't download times be extra long?
that has always happened
source code is only text... not images.
Would be good to see NPM / JS packages not intricately linked to Microsoft.
How is it 720p and yet it's 2024...
this sounds cool!
bruh, i thought it was about JetSetRadio lol
i use bun, should i use deno?
No
@@mrcheeseguyman ok
@@xpynim bro use whatever suits you best, both bun and deno can be annyoing and have silly bugs so read a bit more on "is bun/deno good for {whatever you're working on}"
Thank you Ryan ❤
The way he talks and presents reminds me of Richard Hendricks from Silicon Valley show lmao
That's how you know he's not trying to grift like 99% of every other talking head trying to get you to use their software these days.
I was thinking the same kkkk
Love this, thank you!
15:30 the entire npm in a nutshell, you have one function to write that does one thing and you still chose to use a library that has a oneliner for your whole package !
it was to show that you can publish a package with npm dependencies to jsr
@@lunafoxfire I get it but the example kinda triggers me as I've seen several similar packages like isOdd and leftpad
GitHub vendorlock?
Too much dependance on microsoft owned github
typescript is microsoft
it is completely the game changer!!
Not a very good speaker with all due respect, BUT compensated by the genius of the project. I want this so badly.
dissapointed to find out this has nothing to do with Jet Set Radio
Amazing work
video quality is 720p at max
Should have been called TSR (Typescript Repo) 😁 By the way, this new TH-cam layout sucks. First thing they can do is make the title font size smaller so you can actually see it. Congrats on the project. Looks rad
A shame that this JSR transition completely shafts the URL based paradigm/ecosystem they were previously pushing.
Deno had shown again and again that it is ultimately vcware and all these walkbacks and general instability has made it a pain to build on.
JSR itself is pretty good step forward for js in general on the other hand.
Think the prob is that general URLs guarantee no standard for dealing with TS source and documentation; JSR does
Good to see my bro ❤
Very cool
Its about time.
Thank you for restricting access from Iran, lovely move
Wat?
The logo ...
Jahar ❤❤