Divyansh Singh

Technically, that same spec says this too: > For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model. > > A table element...

#15235 would fix this. But it's a breaking change, so it will probably be added in v6. Use `.cts` extension for now.

Probably ts-node has some issue with nodenext. You can do something like: ```jsonc // tsconfig.json { // ... "ts-node": { "transpileOnly": true, "compilerOptions": { "module": "ESNext", "moduleResolution": "Node10" } }...

Not a stable option, but you can patch `VPNavBar.vue` using a vite alias / plugin or pnpm patch / patch-package to add an extra component after `VPNavBarMenu`.

By load time, I'm guessing you meant when the component is loaded, i.e. on browser? If it's coming from some API, you can just do fetch inside onMounted and map...

Yeah so in this case you should be able to just fetch or import it inside onMounted: ```ts import { ref, onMounted } from 'vue' const versions = ref([]) onMounted(async...

> is this still relevant to the state of deno today Yes. `Deno.serve` is still a separate API. Node code won't instrument it. This PR is blocked by #15455 (see...

Are those links in sidebar working? Can you share a minimal version of this via https://vitepress.new ?

@bukowa In that example you've extra trailing slash. Remove them, it'll work fine:

The second link doesn't have trailing slash 🫠 /foo/index.md -> /foo/ /foo/bar.md -> /foo/bar /baz.md -> /baz