Divyansh Singh
Divyansh Singh
1 GB memory is kind of expected. If you want to reduce it further, you can set `buildConcurrency` to some lower value in vitepress config. But I doubt if it...
Can you provide me a minimal reproducible example where the error stack has no mention of corresponding file?
That already shows the file name: \ I agree it shows that in a way that might not be immediately clear (replaces `/` with `_` and the paths are relative...
> I think you misunderstand. This shows the file name of the markdown file where the error occurred, not the file name of the script in which the error occurred....
The code you've shared is not reproducible. Share a minimal reproducible example in form of repo or using https://vitepress.new and, in future, please use the issue templates while filing new...
Yeah, so that's kind of expected. You can disable the attrs plugin or change the delimiters. We can indicate this behavior in docs/FAQs but we won't be disabling the plugin...
Yeah, regarding the stack trace, it's currently not proper because of markdown-it transforming markdown to vue (line mappings are currently lost here). > Can vitepress catch such an error and...
Ah, I'm currently looking into other PRs. Will get back to you on this in few days.
The bundle step https://github.com/vuejs/vitepress/blob/09e48db355f530c7a138437004659b61239f4b75/src/node/build/bundle.ts#L149-L156 can be made async too. We should do something about the cache in https://github.com/vuejs/vitepress/blob/09e48db355f530c7a138437004659b61239f4b75/src/node/markdownToVue.ts#L23 though. In parallel client and server bundles, it doesn't get hit much....
Ah, so it can't be an actual hash (since you want it to remain constant across edits), it should be a random string which is stored in some file(s) (tracked...