chore: upgrade deps

Author: farnabaz

docs/content/blog/studio-v2.md

@@ -24,13 +24,13 @@ We are excited to announce the release of Nuxt Studio v2, a major update bringin
 Studio is optimized for **Nuxt Content** project but the only real requirement is to have a *content* folder with Markdown files. This simple setup is enough to start editing and publishing your files with the platform.
 ::
 
-### **A more intuitive interface**
+## **A more intuitive interface**
 
 ![Nuxt studio v2 interface](/blog/v2-interface.webp)
 
 The main improvement in Version 2 is a **complete rework of the interface**. We have designed it to be more intuitive and user-friendly, especially for non-technical users. Our goal was to simplify the user experience, making it easier to create and set up projects with minimal hassle. The new interface is light, straightforward, and designed to streamline your workflow.
 
-### **Google authentication**
+## **Google authentication**
 
 ![Google and GitHub authentication](/blog/google-github.webp)
 
@@ -40,7 +40,7 @@ We now have two different authentication methods. You can either login with **Gi
 Since a Google user can not create a project, he has to **join a team** with existing projects to edit them.
 ::
 
-### **Minimal setup to edit your files**
+## **Minimal setup to edit your files**
 
 You can now edit your content **without any setup**, just import your repository and this is it. You can navigate through your files and medias, edit your content and publish on GitHub.
 
@@ -52,7 +52,7 @@ Collaboration is available for teams.
 Medias in the editor are not displayed until you set up the live preview (see section below).
 ::
 
-### Simplified setup for live preview
+## Simplified setup for live preview
 
 ![preview enable between notion like editor and website](/blog/preview.webp)
 
@@ -64,13 +64,13 @@ While GitHub pages deployment remains available and still does not require any c
 It's crucial to use the latest version of the **Studio module** to ensure compatibility and access to new features.
 ::
 
-### New documentation
+## New documentation
 
 With a revamped platform comes a [new documentation](https://nuxt.studio/docs/get-started/introduction). Don't hesitate to check it out to learn everything about the new Studio.
 
 Whether you are an [editor](https://nuxt.studio/docs/editors/introduction) or a [developer](https://nuxt.studio/docs/developers/introduction) you now have your dedicated section in the docs.
 
-### A new direction for Studio
+## A new direction for Studio
 
 Most available CMS solutions have to choose between being very customizable for developers or highly user friendly for content editors, with Studio we want to do both.
 
@@ -80,4 +80,4 @@ Most available CMS solutions have to choose between being very customizable for
 Our Notion-like editor has a bright future ahead, and we want to develop it collaboratively with the community.
 ::
 
-###
+##

docs/content/docs/1.getting-started/2.installation.md

@@ -3,7 +3,7 @@ title: Installation
 description: Get started with Nuxt Content v3 in your Nuxt application.
 ---
 
-### Install the Package
+## Install the Package
 
 Choose your preferred package manager to install Nuxt Content v3:
 
@@ -25,7 +25,7 @@ bun add @nuxt/content
 ```
 ::
 
-### Register the Module
+## Register the Module
 
 Add the Nuxt Content module to your `nuxt.config.ts`:
 
@@ -35,7 +35,7 @@ export default defineNuxtConfig({
 })
 ```
 
-### Automatic Setup
+## Automatic Setup
 
 When starting a new Nuxt project with the `create-nuxt` CLI, you can simply select `@nuxt/content` from the interactive module selector. This will automatically install and register the module for you.
 
@@ -71,7 +71,7 @@ If you don't want to install any package, you can use native SQLite from Node.js
 Checkout [`experimental.nativeSqlite` configuration](/docs/getting-started/configuration#experimentalnativesqlite-deprecated-use-sqliteconnector).
 ::
 
-### Create your First Collection
+## Create your First Collection
 
 Create a `content.config.ts` file in your project root directory:
 
@@ -98,7 +98,7 @@ The `type: page` means there is a 1-to-1 relationship between content files and
 Learn more in our **Collections guide**.
 ::
 
-### Create your First Markdown Page
+## Create your First Markdown Page
 
 Create a `content/index.md` file in your project root directory:
 
@@ -110,7 +110,7 @@ Here is some content.
 
 Read more about writing [Markdown pages](/docs/files/markdown).
 
-### Display your Page
+## Display your Page
 
 Create a `pages/index.vue` file and display the page content:
 

docs/content/docs/1.getting-started/3.configuration.md

@@ -523,4 +523,3 @@ export default defineNuxtConfig({
 ::prose-note
 This feature is only available in Node.js v22.5.0 and above. Enabling this feature in older version will not do anything.
 ::
-

docs/content/docs/1.getting-started/4.migration.md

@@ -148,7 +148,6 @@ Note that in order to make these files available for Module, you should define y
 a way that includes these files. For example `source: '**'` and `source: '**/*.{md,yml}'` will include these files
 in collection, but `source: '**/*.md'` will not include them.
 
-
 ## Ignore dot files
 
 By default, Content v3 does not ignore dot files. If you want to ignore them, you can add `ignore: ['**/.*']` in the `exclude` option of your collection source.
@@ -173,6 +172,3 @@ defineCollection({
   }
 })
 ```
-
-
-

docs/content/docs/2.collections/4.validators.md

@@ -9,7 +9,6 @@ Nuxt Content supports defining collection schemas with multiple validators. Out
 
 ## Using Zod v3
 
-
 ### Install
 
 ```bash
@@ -57,7 +56,7 @@ The `z` re-export from `@nuxt/content` is deprecated and will be removed in a fu
 
 Zod v4 provides a native JSON Schema export. No `zod-to-json-schema` dependency is required.
 
-### Install
+### Install Zod
 
 ```bash
 pnpm add -D zod
@@ -93,7 +92,7 @@ export default defineContentConfig({
 ## Using Valibot
 
 Use Valibot primitives to define your schema.
-### Install
+### Install Valibot
 
 ```bash
 pnpm add -D valibot @valibot/to-json-schema
@@ -144,5 +143,3 @@ You can enrich fields for Studio via `property(...).editor({ ... })` with both v
 ::tip{to="/docs/studio/content"}
 Learn how editor metadata maps to form inputs in Studio.
 ::
-
-

docs/content/docs/2.collections/5.inherit-schema-from-component.md

@@ -48,5 +48,3 @@ export default defineContentConfig({
 ::tip
 Pair `inherit()` with `editor(...)` for better Studio forms if you need custom inputs on top of the component's props.
 ::
-
-

docs/content/docs/3.files/1.markdown.md

@@ -227,7 +227,7 @@ This will be rendered inside the `description` slot.
   :::code-preview{icon="i-lucide-eye" label="Preview"}
     ::::example-hero
     My Page Title
-    
+
     #description
     This will be rendered inside the `description` slot.
     ::::
@@ -425,14 +425,14 @@ In addition to mdc components and `span`, attribute syntax will work on images,
 ```md [index.md]
 Attributes work on:
 
-- [link](#attributes){style="background-color: green;"}, `code`{style="color: cyan;"},
+- [Attributes](#attributes){style="background-color: green;"}, `code`{style="color: cyan;"},
 - _italic_{style="background-color: yellow; color:black;"} and **bold**{style="background-color: lightgreen;"} texts.
 ```
 
   :::code-preview{prose label="Preview"}
   Attributes work on:
 
-  - [link](#attributes){style="background-color: green;"}, `code`,
+  - [Attributes](#attributes){style="background-color: green;"}, `code`,
   - *italic* and **bold** texts.
   :::
 ::

docs/content/docs/3.files/4.csv.md

@@ -140,4 +140,4 @@ id;name;email
 
 ::note
 The CSV parser can be disabled by setting `csv: false` in the configuration if you don't need CSV support.
-:: 
+::

docs/content/docs/4.utils/1.query-collection.md

@@ -8,10 +8,8 @@ description: The queryCollection composable provides methods for querying and
 
 Use the auto-imported `queryCollection` to find contents inside a collection. Here we assume that you have defined `docs` collection inside `content.config.ts`.
 
-
 If you have not defined any collection, check [How to define a collection](/docs/collections/define#defining-collections).
 
-
 ```vue [pages/[...slug\\].vue]
 <script>
 const route = useRoute()

docs/content/docs/4.utils/2.query-collection-navigation.md

@@ -115,7 +115,6 @@ const { data } = await useAsyncData('navigation', () => {
 </template>
 ```
 
-
 ## Server Usage
 
 Nuxt Content provides a similar utility to query collections on the server side. The only difference is that you need to pass `event` as the first argument to the `queryCollectionNavigation` function.
@@ -180,7 +179,6 @@ const breadcrumb = findPageBreadcrumb(navigation, '/docs/guide/getting-started')
 // breadcrumb is an array of navigation items leading to the current page
 ```
 
-
 ### `findPageChildren(navigation, path, options?)`
 
 Finds and returns the direct children of a given path in the navigation tree.
@@ -199,8 +197,6 @@ const children = findPageChildren(navigation, '/docs/guide')
 // children is an array of navigation items under '/docs/guide'
 ```
 
-
-
 ### `findPageSiblings(navigation, path, options?)`
 
 Returns the sibling navigation items for a given path (i.e., other items with the same parent).