Deno support for mojo.js

[recrof]

As both mojo.js and Deno are young projects that have great potential and are (imo) great match, would it be possible to port mojo.js to Deno ecosystem?

[kraih]

We would have to get rid of a few more dependencies, but yes, i think it is quite possible.

[recrof]

We would have to get rid of a few more dependencies, but yes, i think it is quite possible.

Deno includes some of the browser APIs that are not present on node.js, which could help remove few of the dependencies. As I'm from perl background and use mojo utils already(and I'm not mistaken that mojo.js also uses this) Mojo::DOM can use https://deno.land/x/deno_dom@v0.1.31-alpha/deno-dom-wasm.ts which is much closer to native DOMParser present in web browsers.

[kraih]

The DOM parser we already use probably works fine on Deno. HTTP and WebSocket bindings should be fairly easy too. And i'd like to have our own replacements for tough-cookie, form-data and busboy at some point anyway. Those three probably represent most of the real work required.

[kraih]

And now there is also Bun, which actually looks even better than Deno.

[ralyodio]

+1 for Bun. It looks awesome.

[shah]

Deno 1.28 now supports NPM modules natively so it's worth checking out if mojo.js will now work "out of the box".

[lschierer]

along the same lines, I tried to run a fresh install from pnpm create @mojojs/full-app --ts with the tsx instead of tsc, and it cannot find the example controller that the create command provided. I suspect that its the same underlying dependency issues that would prevent someone from using Deno or Bun.

I also tried bun, I get the following:

181 |     }
182 |     /**
183 |      * Create a new `Path` object from a `file://` URL.
184 |      */
185 |     static fromFileURL(file) {
186 |         return new Path(url.fileURLToPath(file));
                                  ^
TypeError: Argument must be a file URL
      at fromFileURL (/Users/lschiere/src/schierer/evonytkrtips-infrastructure/packages/backend2/node_modules/@mojojs/path/lib/path.js:186:29)
      at /Users/lschiere/src/schierer/evonytkrtips-infrastructure/packages/backend2/node_modules/@mojojs/core/lib/server.js:18:20

[shah]

Deno 2.0 was just released and is supposed to have even better NodeJS ecosystem support so it's worth checking out if mojo.js could be upgraded to support Deno "out of the box".

[kraih]

Wonder if the recent @mojojs/path change will help. mojolicious/path.js#50