Deno version & package.json

How often Deno upgrades? As i see currently, it uses pretty outdated version 1.22, which was released a year ago. And recent versions has a lot of amazing features, like package.json support: Deno 1.31: package.json support, so it would be nice to know when we would be able to use it.

Currently I can’t use edge functions cause I can’t even install my dependencies - the protocol npm: doesn’t work, let alone installing them from package.json directly

There’s no timeline as to when the version will update. We’re currently working on allowing npm: imports, but that will take some time (if at all it ends up making into production that is).

Hey there @hrishikesh :wave: , is the npm: protocol supported yet?

Context:

Trying to import import { withAccelerate } from "npm:@prisma/extension-accelerate@1.0.0" in this repo, is failing the build.

No, but you shuld not have to use it. We directly support npm modules: Support for npm modules in Edge Functions

Any update to this? We are unable to build a nuxt3 repo with edge functions, because the outdated version of deno that is on netlify always errors out

TypeError: Cannot read properties of undefined (reading 'setTimeout')

and it looks like a node’s http2 package issue which looks like was fixed in later versions of deno, since it build normally locally

I even tried bypassing the deno version by using a custom build command

#!/bin/bash
curl -fsSL https://deno.land/x/install/install.sh | sh
export PATH="/opt/buildhome/.deno/bin:$PATH"
yarn run build
exit 0

but i got

4:10:48 PM: Downloading Deno CLI to /opt/build/repo/.netlify/plugins/deno-cli
4:10:56 PM: No globalVersion or semver not satisfied. globalVersion: 2.1.4, versionRange: 1.37.0 - 1.44.4

which means it used the outdated local versino anyway…

Based on the comments in that linked issue, it seems to exist even in Deno 2. Or am I mis-understanding?

managed to look at it in more depth and saw that the problem was in a package that we had imported (socket-io-client), which was

so our issue is resolved and was not connected to deno version