Enabling the Unstable Flag for Deno in Edge Functions?

Support
, ,
#1

Hello!

It appears that the major template languages for Deno (e.g. Eta, Handlebars) make use of Deno Standard Library functions that are marked as unstable. How can we control the Deno bundle (and I assume run) command for Edge Functions so we can enable running with unstable standard library functions?

See the build failure below for the standard library functions that will not work unless we can enable running with the unstable flag during the Deno bundle process. Or, if there is a suggested Deno templating language that does not depend on Deno.utime and Deno.utimeSync, I can give that a try instead.

Oddly, these work perfectly fine running netlify dev, but only fail when pushing a build.

7:48:48 PM: Warning Implicitly using latest version (undefined) for https://deno.land/x/handlebars/mod.ts
7:49:00 PM: error: TS2339 [ERROR]: Property 'utime' does not exist on type 'typeof Deno'. 'Deno.utime' is an unstable API. Did you forget to run with the '--unstable' flag?
7:49:00 PM:     await Deno.utime(dest, statInfo.atime, statInfo.mtime);
7:49:00 PM:                ~~~~~
7:49:00 PM:     at https://deno.land/std@0.110.0/fs/copy.ts:96:16
7:49:00 PM: TS2339 [ERROR]: Property 'utimeSync' does not exist on type 'typeof Deno'. 'Deno.utimeSync' is an unstable API. Did you forget to run with the '--unstable' flag?
7:49:00 PM:     Deno.utimeSync(dest, statInfo.atime, statInfo.mtime);
7:49:00 PM:          ~~~~~~~~~
7:49:00 PM:     at https://deno.land/std@0.110.0/fs/copy.ts:111:10
1 Like
#2

We’re in the same boat. The inability to enable Deno flags unstable and allow-ffi is gatekeeping us from Edge Functions.

#3

Hey all,

This is not possible at the moment. Thank you for flagging this so we can pass it on to the team to make it better for a stable release.