Divyansh Singh

I think this can be implemented in the core. I have hit an issue though. If detailed view is not enabled, there will be no text in the search results...

> Is there a way to define documentation across multiple packages in multiple github repositories, while having a single repository for documentation, but keep each package's documentation in their own...

There are actually many more things that will be broken. For example all of these need js-required: copy code, code groups, sidebar groups, vplocalnav, vpflyout, last updated, ... all of...

Try the solutions mentioned in this threads - https://stackoverflow.com/a/9983986/11613622 -- you can also search online for similar solutions (make a web search on something like "nginx redirect based on language...

> It is working alright in the past, but not working for now. This probably never supported badges with slots. For example - https://stackblitz.com/edit/vite-2j5pug?file=package.json (we added badge in alpha.27 which...

> Maybe the behaviors between badge with props and badge with children should be aligned Actually, it's a bit more complicated. Let me explain: ``` ## foo bar is parsed...

Can you try with rc.33, the memory usage during build should be bit improved with this update. Regarding `paths()`, I think getters for params/content should already work: ```ts // [id].path.ts...

Async generators (`async function* paths`) won't work, because we need the list of pages (params) beforehand. And if you're talking about async getters (something like `async get content()`), that doesn't...

> but we can return a `Promise` from the getter Yeah that's what I wrote earlier. That can be done. > And AFAIK async generators should always be preferred because...

> build-time parallelization Probably we can track it at #3183. In vite-ssg, Kael had done this - https://github.com/vuetifyjs/vite-ssg/commit/1f1663a666b3c5fdc30a543b5cf42737fc4b4722 Our rendering is parallel enough I guess, but bundling process can get...