Farnabaz

Changing your query to `const post = await queryContent().where({ slug }).findOne();` will resolve your issue. When you pass a path (string) into `queryContent` it two special behavior: - If you...

@mohong Have you checked my previous comment? https://github.com/nuxt/content/issues/1513#issuecomment-1249258736 If it is not helpful for you, please consider providing a simple reproduction using https://stackblitz.com/github/nuxt/starter/tree/content

It should be fixed 🙂

This is related to Nuxt's pre-render crawler. The `$router` links are not detected during page crawl. /cc @danielroe @pi0

For this, we need to create a specific driver to handle the single file. It should be able to handle a single file from every source, fs, github, ...

There is two way to create single-file drivers for unstorage: ## 1 - Allow unstorage to expose `storage` instance into drivers and create a simple alias driver ```ts // simple...

Have you used [`highlight`](https://content.nuxtjs.org/api/configuration/#highlight) in content options? By default code highlighting is disabled, and you need to enable it. If the issue proceeds, it would be great to create a...

Sorry for the late response, By default `ProseCode` does not show filename, in order to customize the design and add extra information like filename, you need to override `ProseCode` in...

This fixes in #1143 and #1174. Until next release you can use edge version to resolve this issue ```diff - "@nuxt/content": "^2.0.0", + "@nuxt/content": "npm:@nuxt/content-edge@latest", ```

Content v2 have same auto generated meta for each file. (names are changes though, and auto generated fields prefixed with `_` to prevent from possible conflict with non-generated content meta)...