vocs
vocs copied to clipboard
Minimal Documentation Framework, powered by React + Vite.
After creating a fresh project through `npm init vocs` and installing the packages, I get the following error ```bash [vite] Error when evaluating SSR module C:\Users\samsc\Documents\GitHub\emotes\node_modules\vocs\_lib\app\index.server.js: failed to import "/@fs/C:/Users/samsc/Documents/GitHub/emotes/node_modules/vocs/_lib/app/routes.js"...
You can see a full example of this [reprod in this repository](https://github.com/oveddan/vocs-import-issue-example/blob/main/docs/pages/getting-started.mdx) Given I have two snippets: `docs/snippets/config.ts`: ```ts import { zora } from "viem/chains"; import { http, createPublicClient }...
I'm currently facing an error with cut off text in mermaid class diagrams (see image below). It looks a bit like the Vocs css classes are colliding with the plugin....
When navigating from the topNav, we are able to set a match attribute that will open a collapsed page and highlight on the sidebar. The same should be possible when...
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or [setup this action...
Hi, I raised an issue more than a month ago about the program crashes on Windows. Related issues and this PR will close it #52 . --- The following is...
When rendering a code block with ```tsx `https://${process.env.VERCEL_URL}` ``` The `$` is not rendered, how can I fix this?
Vocs currently crashes when it discovers syntax errors in: * MDX files * CSS files * Maybe others? This can be observed by saving a file with a syntax error...
It seems routing for pages with dot in the name does not work, for example `v1.0.md`. Is it expected or am I doing something wrong?
If a link is like `page.md#section-2`, then in the generated site it is converted to `page` instead of `page#section-2`. This is very important issue if pages are generated by another...