Support for Deno directly from setup.

[ScarsTRF]

Since Deno has come a long way, especially with Deno 2.0 with npm package support, it would be nice to have the install script work with Deno as a option to generate the necessary outputs in the template.

A reason for Deno for some is the built in security stall for network, env, file access and so on for those who want it for the safety of rouge npm packages they would possibly use for background processing of data.

Having all this setup from the start could make building and deploying bots much easier with Deno thanks to the built-in compiler to build and distribute bots for people to use or to compile for servers to run in a pinch.

[ScarsTRF]

@twlite #286 doesn't seem to really be a full support as this doesn't generate a deno.json which is what deno uses. On top of that, the imports in the Typescript templates don't have npm:commandkit or npm:discord.js within the app.ts or the commands.

I will say that even after swapping it to Deno by manually generating the deno.json and setting up the tasks and imports needed for the project, I do run into an error running deno task dev stating this:

Task dev commandkit dev
error: Unable to load /home/scarvorrix/.cache/deno/npm/registry.npmjs.org/commandkit/1.0.0-next-beta.20240203223402/bin/index.mjs

Caused by:
    No such file or directory (os error 2)

After looking into the directory, there is no index.mjs but instead index.cjs.

I hope this helps making Deno runtime more supported.

If falling back to the package.json is required, that might be all we need but to say that the runtime is not happy even with that as it returns commandkit not found when running deno task dev

[twlite]

imports in the Typescript templates don't have npm:commandkit or npm:discord.js within the app.ts or the commands

as per deno docs, any dependencies listed in package.json does not require npm: prefixed import and can be referenced directly https://docs.deno.com/runtime/fundamentals/configuration/#dependencies

After looking into the directory, there is no index.mjs but instead index.cjs

The bin file is indeed .mjs https://github.com/underctrl-io/commandkit/blob/main/packages/commandkit/bin/index.mjs and this file is published to npm as it is (unbundled/not transpiled)

and node compatible environment is required as commandkit internally makes the use of various node specific APIs

[twlite]

maybe it requires node_modules to be present, I will investigate

[twlite]

okay the issue seems to be how deno resolves dependencies from other tags, commandkit@^1.0.0-dev.20250702022547 is resolved as version 1.0.0-next-beta.20240203223402 by deno which is a weird behavior considering all other package managers resolve the correct version.

commandkit@1.0.0-dev.20250702022547 however, resolves to commandkit@1.0.0-dev.20250702022547

[twlite]

deno install npm:commandkit@1.0.0-dev.20250702022547

seems to resolve the exact version which seems to work with deno task

[twlite]

I believe this will not be an issue in @latest tag once v1 is officially published, but with @dev this seems like a bug? in deno

Additionally, I have also created deno project example here https://github.com/underctrl-io/commandkit-deno

[ScarsTRF]

Weird, I'm gonna play around with Deno a little more and see if I can't figure out myself as to why the @dev tag isn't resolving to the latest dev version. Other than that I think that was the entire reason why commandkit itself wasn't working out of the box with Deno.

as per deno docs, any dependencies listed in package.json does not require npm: prefixed import and can be referenced directly docs.deno.com/runtime/fundamentals/configuration#dependencies

As for this, I wasn't aware of that until my latest reply which was why I edited my reply adding the package.json response. Doesn't help that I just recently started moving to Deno either