I love the way Ryan talks about issues devs have on a day to day, and even presents the solution to developers; not marketers.

@mattymattffs

10 күн бұрын

These are issues that web developers have created themselves.

should have been called jdsl, because it's genius

@adwaithrajesh596

26 күн бұрын

Tom is a genius.

@pookiepats

26 күн бұрын

Prime has achieved indirect reference status 😊

@farrela.846

26 күн бұрын

Love me some jdiesel

@leonvolq6179

26 күн бұрын

😂😂😂❤

@plaintext7288

26 күн бұрын

Primal reference

I hope that the Node and Bun communities adopt this standard.

@mirvin11

26 күн бұрын

without alternate uses of TypeScript is bad

@zheil9152

26 күн бұрын

I hope not. It will ironically complicate crap even further

@ollierkul

26 күн бұрын

@@zheil9152 Why? Isn't that entirely dependent on implementation?

@zenpool

26 күн бұрын

Bun > Deno

@robertluong3024

25 күн бұрын

​@@zheil9152can you specifically state what will make it worse?

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.

@impromp02

21 күн бұрын

You should be worried 😟

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.

Hooray for floating head man and his creation

@JosephLuklukkyjoe

11 күн бұрын

now that you called him that i cannot (un)see it

I am extremely eager for private registries/packages. I want to try using this for work.

Deno is killing it

Can't wait for Primeagen to call this "JIZZER"

@Raykazen

26 күн бұрын

best timeline

@wyndmill

26 күн бұрын

oh no

@KushLemon

26 күн бұрын

Cringe.

@TillmannHuebner

26 күн бұрын

underrated

@shapelessed

26 күн бұрын

@@KushLemon 🤡

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

@julsius

24 күн бұрын

as long as it doesnt start demanding TS from team vanillaJS

Petition to rename "denoland" to "Jerassic Park"

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

@ismaely.racine4866

25 күн бұрын

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?

@kearfy

23 күн бұрын

@@ismaely.racine4866 I don't want to push big wasm files into my github repo :)

I love the work Ryan and Deno is doing, and JSR seems to be right there with all the other awesome tools from them

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.

@somebody-anonymous

24 күн бұрын

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

13:52 Japanese: 2024-12-31 this way you can have nesting directories that make sense.

Amazing work! I'm glag to see this new generation of registry!

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?

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!😊

Not sure why they didn't erupt in applause when he finished uploading the module. I would've gone nuts. That was so easy

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.

Can you upload it in 4K resolution?

Now I know the right date format, I keep use this for versioning.

does it work on cloudflare as a backend instead of s3 ?

Love that rotational symmetry in the logo

@gorandev

9 күн бұрын

And the fact that it looks similar to npm logo... Excellent job, whoever designed the logo

Sounds game changing!

Can we use this without GitHub ?

feels awesome seeing the creatorman playing around with all his creations, glad to know I'm using them correctly

this seems like such a big todo for the 6502 "Jump to SubRoutine" opcode introduced in the 1970s

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.

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

This video should be republish with minimum 1080p resolution, as is demoing some code, the code written looks blurry!

@buzz1ebee

25 күн бұрын

Yeah it's 2024. 720p isn't acceptable.

I like how it works with Bun.

Articulation of pain points around ts/js esm tsc is on point. Nobody wants to mess with that

gonna use one-true-date soon

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?

@deno_land

25 күн бұрын

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?

@ob4816

24 күн бұрын

@@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 🙂

@lucacasonato-deno

23 күн бұрын

@@ob4816 Yes this is possible.

Ryan! always making our lives much easier!

Google says you are talking about Java Specification Requests? ;)

Another good work from ryan, tnx

This looks amazing and extremely exciting

And I was there to see it :)

@js-ny2ru

25 күн бұрын

Same :)

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?

@deno_land

25 күн бұрын

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.

Why brilliant minds are so fit

Absolutely fantastic...

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.

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

@darkarie

15 күн бұрын

that sounds horrible

Maven Central has 13,833,950 indexed packages, a lot more than the 2 million in npm

Top 2 comments are about a KZreadr. We're finally in the goofiest timeline 😌

jet set radio is cool yeah

@TCRodriguez

16 күн бұрын

Came here to say this lol. First thing I thought when I read that.

This is amazing ! I want private github modules with this

If I don't want my source code to be open in my distribution is that possible?

@JohnnySacc

10 күн бұрын

minify it yourself lol

Great initiative 🎉

Love 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

27:32 Prime mentioned

When is JSR replacing 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

@lucacasonato-deno

23 күн бұрын

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.

@user-kt1iz4vc3x

23 күн бұрын

​@@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

@porcupinetree-bb3zg

3 күн бұрын

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.

@user-kt1iz4vc3x

2 күн бұрын

@@porcupinetree-bb3zg i'm not worried i'm just curious. i like node.js

Truly an awesome talk.

this sounds cool!

Amazing work

Very cool

Would be good to see NPM / JS packages not intricately linked to Microsoft.

Love this, thank you!

so how does npm know what to do with jsr: ?

That's great

bruh, i thought it was about JetSetRadio lol

i use bun, should i use deno?

@mrcheeseguyman

26 күн бұрын

No

@xpynim

26 күн бұрын

@@mrcheeseguyman ok

@thatsalot3577

25 күн бұрын

@@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}"

Jahar ❤❤

Thanks Ryan, this looks awesome 🎉🎉🎉

Hot take: Is JSR already outdated by Framework X released 3 hours ago?

If we're getting go to definition and seeing full TS source with comments, won't download times be extra long?

@luanbui5273

24 күн бұрын

that has always happened

@enkvadrat_

24 күн бұрын

source code is only text... not images.

it is completely the game changer!!

oh hi ryan

Its about time.

Good to see my bro ❤

Richard Hendricks from Pied Piper

Thanks god it's not another runtime, i have not catched up with last few dozens yet.

@josephengelmajer9668

25 күн бұрын

Deno has been around since 2018. The presentation was about a package registry not a runtime

oooh i like!

is amazing!!

Pretty cool. 👍

GitHub vendorlock?

The execution is good, but the idea is… Well, you are trying to replace the largest package registry in the world. In practice none of the shiny features make much sense. If I want to support JavaScript users, I still need to transpile myself. This way I can ensure my complex package is built the right way before publishing a faulty release to the users. If I don’t want to support JS, I can just push TS to npm. It also only works great with deno, thats why you didn’t „jump to definition“ in the Vite project, because it doesn’t work. As an author, I don‘t want to support deno, bun and whatever: First, because they are often incompatible and its a whole lot of work to make them compatible and maintain this. Second because the user base is too small to even think about it. New runtimes come out every month now that claim to be compatible with Node and NPM but actually aren’t. It´s great to see competition, especially because NPM is now also owned by Microsoft, but I don’t think this is the right approach.

@ollierkul

21 күн бұрын

Jump to definition actually does work. You can test it yourself by creating a new Vite project and install a jsr package using "npx jsr add ".

How is it 720p and yet it's 2024...

dissapointed to find out this has nothing to do with Jet Set Radio

video quality is 720p at max

Awesome

Should have been called TSR (Typescript Repo) 😁 By the way, this new KZread 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

The way he talks and presents reminds me of Richard Hendricks from Silicon Valley show lmao

@JoRyGu

26 күн бұрын

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.

@heitorfreitas3662

26 күн бұрын

I was thinking the same kkkk

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 !

@lydianlights

24 күн бұрын

it was to show that you can publish a package with npm dependencies to jsr

@thatsalot3577

23 күн бұрын

@@lydianlights I get it but the example kinda triggers me as I've seen several similar packages like isOdd and leftpad

Thank you Ryan ❤

Thank you for restricting access from Iran, lovely move

@edism

26 күн бұрын

Wat?

Haha, the solution to all the clutter ... is another overlay ... not sure what's going on with these guys.

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.

@croopercrat

25 күн бұрын

JSR itself is pretty good step forward for js in general on the other hand.

@__WONTFIX__

24 күн бұрын

Think the prob is that general URLs guarantee no standard for dealing with TS source and documentation; JSR does

Ryan "TOM" Dahl invents jDeezlr

Ryan is the best.

Too much dependance on microsoft owned github

@porcupinetree-bb3zg

3 күн бұрын

typescript is microsoft

Not a very good speaker with all due respect, BUT compensated by the genius of the project. I want this so badly.

jsr pkg size is 38.4 MiB

@Novacification

26 күн бұрын

Why is that an issue? It's a registry. Nothing new is packaged with your production code.

@Ace3260

24 күн бұрын

Smooth brain comment

What a crazy intro. JavaScript might be the fastest way to express business logic, but it's also the most error prone.

Here we go awain, another technology that recruiters won't know even how to spell and ask for 5 years of experience on it