Deno Support

[KnorpelSenf]

Currently, VuePress requires a Node.js setup. However neither the generated static content nor the client-side JS depends on Node in any way.

Deno is a new JavaScript and TypeScript runtime and it has pretty cool APIs that I'd love to use when developing plugins in order to customise my site. It would also speed up build time because the code no longer has to be compiled, since Deno can execute TypeScript.

What's your opinion on Deno support, be it through a migration/port or by creating a fork/second version of VuePress? How hard would this even be?

[Mister-Hope]

My first questions is: Are you sure all the upperchain tools support deno? E.g.: Vite.

You'd better make sure this point, before we evaluate deno support.

In my mind, deno split up its ecosystem with npm, and while vuepress are using 1000+ npm packages, we can not "Support Deno" by our own.

[KnorpelSenf]

I don't think that deno has a complete system

That's correct, this is very much in its infant stage. That's why it seems like it's time to do something and establish Vue as the first proper solution, no? :)

[KnorpelSenf]

we cannot migrate 100+ core packages directly to deno and maintain theme by ourselves

Ah well, fair enough. Thanks!

[KnorpelSenf]

There is an example repo for how to use Vite on Deno: https://github.com/bartlomieju/vite-deno-example

[Mister-Hope]

Hi, if you read more carefully about the demo and deno docs https://www.denojs.cn/manual/npm_nodejs/compatibility_mode, you will see that the demo is using an unstable feature called "Node.js compatibility mode" which allows node packages running on deno.

In this case, we might light vuepress run on deno, you can test it and report any uncompatable code in our repo through discussion, We might improve it if we do have a workaround.

Also any upsteam imcompatable issue is not something we are currently insterested in.

[Mister-Hope]

Or, more clearly, if we do write something that can not run on deno, and we do have another way to implement it and let it support deno, we will make the change if you can point out the issue clearly. Feedback and contributions are welcomed, but deno support is not in our road map. We are not insterested in updating our toolchains to make sure they are "Deno compatable" and we don't want to make progress and adding test to support deno.