Apparently requested since 2004, according to gHacks[1], but the oldest entry in Bugzilla I could find was from 2014[2]. However, that entry does reference a post from mozillaZine from 2004[3]. Though it's not really a request, but an addon that made it possible to change keyboard shortcuts back then.

1: https://www.ghacks.net/2025/11/17/firefox-is-adding-support-...

2: https://bugzilla.mozilla.org/show_bug.cgi?id=972662

3: https://forums.mozillazine.org/viewtopic.php?f=48&t=72994

Wow that’s a long time. I’m not familiar with Firefox as an organization but I would have thought them as being big enough or prominent enough to respond to feature requests more quickly. Or is that unreasonable?

LiveScript was, and still is, a much better name

I'm quite curious on how they're doing the song extending!

Well done, the Deno team!

I found the FAQ in the announcement well made too, with some good and questions and answers.

I'm already having a great time with Deno v1 on my side project - thank you!

Amazing release!!

So nice to see the Standard Library stabilizing too. I'm using it more and more.

I think this is a really well done step in the right direction - bravo!

You can join the waitlist in the sneak peak of JSR linked in the end of the article: https://jsr.io/waitlist

I'm curious on what the Deno team is building here.

Like others have said, it's going to be a new package registry. It was unofficially announced at SeattleJS Conf 2023: https://www.youtube.com/watch?v=Dkqs8Mcxbvo&t=424s

I didn't see any major reason for why they were creating another registry.

I thought their whole thing was to maintain backwards compatibility, not introduce new, redundant standards?

Here's the specific talk https://youtube.com/watch?t=822&v=dipwQfcV0AU (CascadiaJS channel) or https://youtube.com/watch?t=822&v=5DX49vzLfqw (Deno channel)

Here's what they have to say on the JSR site:

Why Choose JSR? A True TypeScript-First Environment: Efficient type checking and no transpilation hassles—write in TypeScript and deploy directly.

Performance and Usability at the Forefront: With integrated workspaces and seamless NPM integration, JSR puts usability first.

Secured and Accessible Modules: All modules in JSR are exposed over HTTPS, ensuring your code is always secure.

Open Source, Community-Driven: Built by developers, for developers, JSR is shaped by the real-world needs and contributions of the JavaScript community.

JSR = JavaScript Registry (from the site). It seems fairly clear this is a package registry, i.e. an NPM alternative.

But they promoted they will not need one at any time, to extent they will never build one. There was only deno.land as a point to discover libraries or what community builds.

Yep, but it seems they learned something from the experience?

Hopefully it will be closer to how Go does it.

Hmm, curious too. Maybe, given the few hints, an alternative to npmjs.com registry.

I assume it's an npm competitor? Likely with a different technical design.

I randomly stumbled into Deno's homepage today, and was amazed by both how far it has come, and how good the homepage is now!

Interesting take from him:

" ... one of the most interesting parts of Dieter's story is that he now looks back on his career with some regret. «If I had to do it over again, I would not want to be a designer,» he's said. «There are too many unnecessary products in this world.» Dieter has long been an advocate for the ideas of environmental consciousness and long-lasting products. He's dismayed by today's unsustainable world of over-consumption, where "design" has been reduced to a meaningless marketing buzzword."

"Rams is a design documentary, but it’s also a rumination on consumerism, materialism, and sustainability. Dieter's philosophy is about more than just design, it’s about a way to live. It’s about getting rid of distractions and visual clutter, and just living with what you need. The film features original music by pioneering musician and producer Brian Eno."

- https://www.hustwit.com/rams