Divy

vitepress is trying to access `location.hash`. If I run the build script using `deno run --location http://example.com`, it works.

Hmm, does it work using BYONM? ```jsonc // deno.jsonc { unstable: ["byonm"] } ``` ``` $ npm i vitepress $ deno task docs:build ```

> where will these details for each framework be stored? Could there be a frameworks section somewhere in the [deno docs](https://docs.deno.com/runtime/tutorials/hello_world)? We still need to figure out a good DX...

@marvinhagemeister It works with `npm i` with `DENO_FUTURE=1`. Removing the `node resolution` tag.

Closing, all functionality is working with DENO_FUTURE=1. DX will get better when `deno i` is added ``` $ deno run -A npm:vitepress init $ npm i vitepress $ export DENO_FUTURE=1...

Interesting :thinking: We don't have any symbol named `_computedKey` in Deno internals. This seems like something generated by SWC for the Decorators proposal. Ref https://github.com/swc-project/swc/issues/8551 cc @dsherret

Fixed with https://github.com/denoland/deno/pull/24166. Thanks @HasanAlrimawi

hmm yeah its errors with: ``` The requested module 'node:http2' does not provide an export named 'Http2ServerRequest' ```

I can reproduce this in `deno repl` The event loop seems to be spinning the CPU at 100%. 

Adding `unstable: ["byonm"]` in deno.jsonc fixed this error.