“deno_land” — Fediverse search results on home.social

Frontend Dogma @[email protected] · 2025-05-25 · 18:35 UTC

A Brief History of JavaScript, by @deno_land:

https://deno.com/blog/history-of-javascript

#history #javascript #ecmascript #typescript #json #javascriptengines #runtimes #browsers

#browsers #runtimes #javascriptengines #json #typescript #ecmascript

Olivier Forget @[email protected] · 2023-12-30 · 18:32 UTC

I was looking through some old projects to find something I could submit for @deno_land 's #NodeToDenoChallenge . It was fun looking at my old stuff. Some really wild ideas, like a "CSS Debugger" that implements a special grammar to rewrite the #CSS specs in a machine-readable format that could be fed into an analysis tool for CSS. This was borne out of my frustration with the lack of debug tooling in browser #devtools at the time. (It's getting better now.)

https://github.com/teleclimber/CSS-debugger

1/

#nodetodenochallenge #css #devtools

Michał "rysiek" Woźniak · 🇺🇦 @[email protected] · 2022-12-14 · 10:41 UTC

Writing tests in #Deno :dinosaur: is positively *pleasant*.

No clue how they achieved that, but compared with Jest, and especially if you're testing stuff that relies on WebAPIs, Deno is a clear improvement.

Much recommend:
https://deno.land/[email protected]/basics/testing

Looks like I might be able to tear all the NodeJS/npm crap from #LibResilient after all. Fantastic. 🎉

#libresilient #deno

Greg Wolanski @[email protected] · 2026-04-04 · 21:01 UTC

I changed my mind: I want to keep only visual highlights from books on https://are.na. Today, I wrote a little script that removed all of the text highlights. I used @deno_land for this. I appreciate Deno's approach to security and the elegant pooledMap function in the standard library. :) #arena #deno

#arena #deno

poes 🇵🇸 @[email protected] · 2023-10-25 · 15:13 UTC

Ok, happy enough for an initial release. kview, a web app viewer for
@[email protected] KV Stores, both locally and on Deno Deploy. Check out: https://deno.land/x/kview. Feedback welcomed.

https://x.com/kitsonk/status/1716411380465856924?s=20

#deno #denokv

#denokv #deno

Greg Slepak @[email protected] · 2025-07-23 · 17:32 UTC

#JavaScript developers: do not use `npx`, ever.

Use @deno_land's `deno run` instead with appropriate sandboxing flags.

Example: https://github.com/okTurtles/chel/pull/58/files

#nodejs #npx #infosec #security

#javascript #infosec #nodejs #npx #security

Frontend Dogma @[email protected] · 2025-05-06 · 06:30 UTC

Add JSR Packages With pnpm and Yarn, by @lcasdev (@deno_land):

https://deno.com/blog/add-jsr-with-pnpm-yarn

#jsr #pnpm #yarn

#yarn #pnpm #jsr

Pelle Wessman @[email protected] · 2024-10-11 · 09:54 UTC

At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

- JS-runtime: Both uses V8
- Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
- Native code: Node.js uses C++, Deno uses Rust

So essentially it boils down to libuv vs tokio and C++ vs rust

If one ignore everything else about Node.js and Deno, the winner is clear to me.

#libuv #tokiors

Pelle Wessman @[email protected] · 2024-10-11 · 09:54 UTC

At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

- JS-runtime: Both uses V8
- Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
- Native code: Node.js uses C++, Deno uses Rust

So essentially it boils down to libuv vs tokio and C++ vs rust

If one ignore everything else about Node.js and Deno, the winner is clear to me.

#libuv #tokiors

Pelle Wessman @[email protected] · 2024-10-11 · 09:54 UTC

At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

- JS-runtime: Both uses V8
- Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
- Native code: Node.js uses C++, Deno uses Rust

So essentially it boils down to libuv vs tokio and C++ vs rust

If one ignore everything else about Node.js and Deno, the winner is clear to me.

#libuv #tokiors

Pelle Wessman @[email protected] · 2024-10-11 · 09:54 UTC

At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

- JS-runtime: Both uses V8
- Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
- Native code: Node.js uses C++, Deno uses Rust

So essentially it boils down to libuv vs tokio and C++ vs rust

If one ignore everything else about Node.js and Deno, the winner is clear to me.

#tokiors #libuv

Pelle Wessman @[email protected] · 2024-10-11 · 09:54 UTC

At a very basic core level, a comparison between @deno_land 2.0 and @nodejs could probably be summarised as:

- JS-runtime: Both uses V8
- Asynchronous I/O: Node.js uses #libuv, Deno uses #tokiors
- Native code: Node.js uses C++, Deno uses Rust

So essentially it boils down to libuv vs tokio and C++ vs rust

If one ignore everything else about Node.js and Deno, the winner is clear to me.

#libuv #tokiors

Mike Kasprzak 🦖 @[email protected] · 2023-02-10 · 16:23 UTC

Yo, there are so many modern #JavaScript frameworks and workflows!! 😅

I'm extremely fond of @preact, which makes me really excited to use #Fresh and @deno_land (especially now that #Deno supports NPM).

I'm trying my best to keep-up with all the ongoings, but I just learned about #Qwik today and I finally grokked what #Vite and #PartyTown do. 🤪

How does anyone keep all this JavaScript stuff straight? What's current, legacy, upcoming? 😅

#javascript #fresh #deno #qwik #vite #partytown

Olivier Forget @[email protected] · 2026-01-23 · 18:11 UTC

I don't use #react so I didn't pay much attention to this, but #react2shell is quite a thing, wow.

From what I understand if you were running your RSC in @deno_land with *minimal permissions* then the exploit's consequences would have been limited. In the post I boosted below, the exploit was used to overwrite the authorized SSH keys. You'd *never* run Deno in prod with that kind of access (right? RIGHT???).

What surprises me a bit is that I don't see many posts from people who were running their React in Deno (properly) and therefore largely escaped this massive vuln. I feel like they'd be celebrating, but I don't see it. Does nobody run React in Deno in prod? Or did they still get pwned somehow? Something else?

#react #react2shell

Olivier Forget @[email protected] · 2026-01-23 · 18:11 UTC

I don't use #react so I didn't pay much attention to this, but #react2shell is quite a thing, wow.

From what I understand if you were running your RSC in @deno_land with *minimal permissions* then the exploit's consequences would have been limited. In the post I boosted below, the exploit was used to overwrite the authorized SSH keys. You'd *never* run Deno in prod with that kind of access (right? RIGHT???).

What surprises me a bit is that I don't see many posts from people who were running their React in Deno (properly) and therefore largely escaped this massive vuln. I feel like they'd be celebrating, but I don't see it. Does nobody run React in Deno in prod? Or did they still get pwned somehow? Something else?

#react #react2shell

Deni Mintsaev (mintydev) @[email protected] · 2025-06-28 · 18:29 UTC

I attended an amazing developer conference in Munich today: JSCraftCamp. Met a ton of cool people, including the developer of JSR from @deno_land, and even got to give my own talk about developer experience. It was my first event like this, and I'm definitely looking forward to next year!

#JSCC25 #webdev #Javascript #Typescript #programming

#jscc25 #webdev #javascript #typescript #programming

Erik @[email protected] · 2025-02-24 · 15:20 UTC

This week on the pod Kamran and Erik unpack JSR, the new open alternative to the npm registry from the folks at @deno_land. They both published packages and discuss what JSR offers npm doesn't, when to use it, and how it works for both consumers and maintainers.

https://typescript.fm/6

**#typescript** **#javascript** **#jsr**

#typescript #javascript #jsr

Matthew Miller :donor: @[email protected] · 2024-11-05 · 04:40 UTC

First it was cool to target just Node, even if TypeScript added some complexity to the bundling process! Worth it!

But then there arrived Deno, which was TypeScript-first and came with a ton of tools built in...but required rewriting to stop using Node-specific data types, to include extensions on every relative import across the entire code base, then finding and referencing deps by HTTPS addresses, and then finding and incorporating another build process for two of the three monorepo packages to maintain the ability to deploy to NPM. Okay, fine I guess...

But wait! Announcing "Web API runtimes" like Bun and Cloudflare workers, and Vercel, requiring test harnesses to try and test future releases in.

It's cool, though: everything still fetches packages from NPM!

Except now there's deno.land/x that can host packages for Deno?! Fine, I'll support that too for the packages that make sense to run server-side.

Except wait there are Deno frameworks with SSR support that can load browser packages from deno.land/x too! But my third, browser-centric package not rewritten for Deno is now suffering from its lack of Deno support!

Maybe rewriting these packages to deploy through JSR.io might eliminate the TypeScript build step, support Node, Deno, and everything else, and make this browser package available in Deno projects?

Well Deno 2.0 did just drop, with workspaces support to boot, so if I'm going to do this, do I also refactor my monorepo to use Deno's workspaces support instead of this working combination of pnpm and Lerna and NX? Except the VS Code Deno extension's "format on save" breaks when you enables workspaces...

...Oh, don't mind me. Just some reminiscing from the OSS maintainer trenches 🥹

#javascript #typescript #deno #node #bun #npm #jsr #javascriptwasamistake

#javascript #typescript #deno #node #bun #npm