How to properly install deno as a runtime with pnpm?

[zkochan]

I want to add devEngines support to pnpm. This will allow users to declare their runtime. For instance:

{
  "devEngines": {
    "runtime": {
      "name": "deno",
      "version": "^1.0.0"
    }
  }
}

For Node.js we install the artifact directly from their website. The integrity that we add to the pnpm lockfile is calculated from the shasums file that every version ships. For instance: https://nodejs.org/download/release/v22.13.1/SHASUMS256.txt

What would be the best way to install deno? I see that there's a npm package called deno: https://www.npmjs.com/package/deno. So, is it OK if we just install it as a regular npm dependency?

[bartlomieju]

Hi Zoltan. The most reliable way would be to download Deno from the GH releases page, where you'll find binaries along the integrity files, eg. here's the latest 2.4.2 version: https://github.com/denoland/deno/releases/tag/v2.4.2

[dsherret]

FWIW, GitHub's API provides the checksums for all assets in a single request https://api.github.com/repos/denoland/deno/releases/232832123 (though I guess rate limiting could be an issue if relying on that api and not using a github token)

I see that there's a npm package called deno: https://www.npmjs.com/package/deno. So, is it OK if we just install it as a regular npm dependency?

That sounds fine to me and put the shasum of that in the lockfile? An issue at the moment is #27755 but hopefully we'll fix it soon.

[zkochan]

I'll have to think about it. It is easier to implement via the npm package for sure. We'll just have all these packages in the lockfile:

  '@deno/[email protected]':
    resolution: {integrity: sha512-0WhM9uEXjZoPRfzEnWCGwaGBOxEIVbyiTOebcSgQhvpsLnkLBStw95qdOBPH1c3pxsx8i2ORWNQKkGStSghNlA==}
    cpu: [arm64]
    os: [darwin]

  '@deno/[email protected]':
    resolution: {integrity: sha512-Five8JcH5mA0yEj6hxXBYzBqVz9lAAnWSWksE6g926FH/N/rrFywnPPZd1xleGDLjK0vD1vhImRI+dHubfAwuw==}
    cpu: [x64]
    os: [darwin]

  '@deno/[email protected]':
    resolution: {integrity: sha512-6tfJr8LcWJdPBNWZofu/Zit7113rgIb4QJsfFBTlPhrijHEmkgSwfbszY7S/kZ/nGA4F9hXKO4Af+Bk06PM1nQ==}
    cpu: [arm64]
    os: [linux]

  '@deno/[email protected]':
    resolution: {integrity: sha512-LzDLyrROm2oxt2g8sjG6niYWaZas/HLBk4Ns5qEhf2bGaDr8Lcq24VTnThZLepLUKt8cTfT3NGX3MZZWKwSVmA==}
    cpu: [x64]
    os: [linux]

  '@deno/[email protected]':
    resolution: {integrity: sha512-hW6NYp4w0jD0VLHl7E2tPG/NSxjrFSXACbxCdJWL36AGlIer7aVm7Mldp4JLXuMXfAyGdYFQUvtgB7z9Kotgdg==}
    cpu: [arm64]
    os: [win32]

  '@deno/[email protected]':
    resolution: {integrity: sha512-47tNwcQus0AFRX4oxWCrLF6R7/0r8al/5HwqnSrF5iayMRd9BnkDxvRRRo3KqRuGIPxpVSxbkbsFvpj9Hp5Zhw==}
    cpu: [x64]
    os: [win32]

  [email protected]:
    resolution: {integrity: sha512-HlQGDol7S+Dwm3Kzn0U9TYr9XqI0PNJZ5qB6OtbEJcmo+jlRiwj2So/LhmxNzkxVexgu1AFzdv6BZL0+ygyyUw==}
    hasBin: true

But we'll also have to run deno's postinstall script.

[zkochan]

I see that in the packages uploaded to npm, there is a package for windows with arm64 cpu. But in the assets on the release page I only see deno-x86_64-pc-windows-msvc.zip for windows. How so? I guess in that case the npm package would support more systems.

[dsherret]

Yeah it's just a copy of the x86_64 package atm.

[zkochan]

I have decided to use the npm registry to resolve the version and then download the binaries from the Github release page. Here's the PR: pnpm/pnpm#9791