[RFC] support deno

[pinghe]

Whether to support running on deno ?

https://github.com/denoland/deno

[Qix-]

I've never used Deno, is there some reason why this doesn't work on Deno?

[pinghe]

q1: import error

myprj.js

import debugdef from 'https://unpkg.com/debug'
const debug = debugdef('myapp:Index')

debug('testing.....')

output error:

Uncaught SyntaxError: The requested module 'https://unpkg.com/debug' does not provide an export named 'default'

fix:
bundles the debug modules for use with deno. https://github.com/reggi/node-to-deno

q2: The environment variable set does not take effect.

DEBUG=myapp:* deno my.js

[Qix-]

Would exports.default = exports work here? @sindresorhus what was the rationale behind not doing this? I can't remember what the arguments were and Google wasn't pulling anything up.

@pinghe ultimately, the Deno community needs to have a workaround for legacy modules they wish to use on Deno. You can't create a new runtime with different standards and expect modules/packages/plugins/whatever from other, incompatible runtimes to magically work with it.

v5 will use modules, but I won't be changing v4 to do so.

[sindresorhus]

sindresorhus/memoize#31

[Qix-]

Thanks, that's what I needed.

I'll fix this within the week.

[pinghe]

Thanks.

[trivikr]

Any update on this request for supporting Deno?
Latest update was in Jan 2020 #736 (comment)

sindresorhus/memoize#31

Thanks, that's what I needed.
I'll fix this within the week.

[trivikr]

Update: Deno community built it's equivalent debug utility https://deno.land/x/debug@0.1.1
GitHub: https://github.com/denosaurs/debug

[Qix-]

Yeah, Deno is a completely different platform and language. I don't really see how we'd support that.

Going to close, thanks for the update @trivikr.

[tracker1]

Should be very similar to the browser module, but exported as esm.

[AddictArts]

@pinghe ultimately, the Deno community needs to have a workaround for legacy modules they wish to use on Deno. You can't create a new runtime with different standards and expect modules/packages/plugins/whatever from other, incompatible runtimes to magically work with it.

It recently does, not sure when, but I ran into this issue. For anyone looking like I was using an import map, ex import_map.json will solve it. You can use deno cli arg --import-map= instead of the deno conf.

       │ File: .\import_map.json
   1   │ {
   2   │   "imports": {
   3   │     "debug": "npm:debug"
   4   │   }
   5   │ }

and to make cli execution easier ...

       │ File: .\deno.jsonc
   1   │ {
   2   │   "importMap": "./import_map.json",
   3   │   "tasks": {
   4   │     "run": "deno run --allow-read --allow-write --allow-env --allow-sys ./index.ts",
   5   │     "compile": "deno compile --allow-read --allow-write --allow-env --allow-sys --no-check --unstable ./index.ts"
   6   │   }
   7   │ }