home.social

Search

1000 results for “deno_land”

  1. Is anyone an expert on Deno lock files?

    We have a 3rd party module on deno.land. When we build it creates entries like:

    "path-to-module": "HASH"

    That's fine. But the next time we run things the lock file gains a new line:

    "path-to-module#UNIXTIMESTAMP": "HASH"

    The hash hasn't changed but it has effectively created a new URL each time. This is really annoying because it means the deno.lock file grows and grows. Is there any way to get it to stop adding a time stamp to the path?

    #Deno #Lume

  2. Day 3 #30DayChartChallenge 2026: Mosaic 🟡🟠🔴
    This Voronoi scatterplot shows 889 endangered U.S. animal species from the IUCN Red List. Each dot is one species. Position encodes threat burden: x = total human-caused threats, y = how many distinct threat categories those threats span.
    Built with @observablehq Plot, #Svelte, @deno_land, and the IUCN Red List API.
    Live interactive: nicolelily.github.io/voronoi-s
    #DataViz #AnimalWelfare #IUCN #Conservation #Climate

  3. 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?

  4. @jensimmons
    @paul
    @jaffathecake
    @deno_land
    et al.

    #JS #Intl #i18n

    Hello browser people, hello server people, hello JS,

    what I do wonder about is if we could harmonize the data offered in your version of Intl developer.mozilla.org/de/docs/

    Two examples :
    - Federal States and Currency

    user story;
    A client-to-server federated software can rely on Intl and use all of its data and names in all of the languages consistently.

    Currently some environments only offer ISO3166-2 and "a subset of" ISO3166-2-lvl4 while others thankfully offer all ISO3166-2-lvl4 and ISO3166-2-lvl8 …
    Let's just get all of the states.

    Yesterday we had a quiz with the question of the currency in the "holiday paradise Curaçao and Sint Maarten" which is the Carribean Gulden since 2025.

    Could there be 1 repository for the data for all [despite hypercapitalism] ?

    Then we could e.g. write things comparing against e.g. wikidata, contribute, keep it updated and be happy.

    ?

  5. I thought this post on Twitter about the of the homepages of tools and frameworks was interesting, and I thought I’d cross post it here

    🛠️ It uses this tool: page-speed.dev/

    Here’s how some of my favorite tools do: @eleventy, @astro, @deno_land Fresh,

    🐥 Original post: x.com/fredkschott/status/17564

  6. 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.

  7. @deno_land Is this getting standardized through the #WinterCG? Couldn’t see it mentioned here: wintercg.org/work

    /cc @jasnell @lcasdev

  8. I changed my mind: I want to keep only visual highlights from books on 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

  9. Surprised to keep hearing about troubles in #deno land 🦕

    In the middle of an #agentic AI hype cycle, you'd expect for a permission-based #typescript runtime to be doing just fine.

    #rust btw

    What's not to like?