Open DwieDave opened 1 year ago
For a number of years we have followed interest in deno
for our other products, (Quokka.js and Wallaby.js), but there are a few features we require to add support.
Console Ninja operates a bit differently so it may/may not be possible to support deno
/ fresh
.
After initial investigation, we think we may be able to add support for some front-end frameworks (e.g. specifically Vue, React) but I guess if you were using vue
/ react
, you would probably use node
instead.
With fresh
being completely implemented in deno
, we need to guage interest before we investigate further.
If you would like to see support for deno
, please:
deno
, i.e. front-end app, back-end app, how you are launching deno
(and any CLI parameters you use)deno
in combination with fresh
(which does not need a build-step -- it must be run by deno directly)deno task start
which runs the following command deno run -A --watch=static/,routes/ dev.ts
for local development--watch=...
option provides auto-restarting on file-change/save of the comma separated paths-A
allows all permissions (--allow-net, --allow-read, --allow-write, --allow-env, ...) for development purposesI don't currently use Deno/Fresh but will consider it in the future. It depends on the development, BUT Deno sets the right foundation and is very innovative.
We need that!
Describe the feature you'd like.
Would it be possible for console-ninja to support Deno? Or is that too much of a change? They are supporting npm packages since Deno Version 1.28.