Nuxt•4w ago

Nuxt content v2 -> v3

Nuxt version ^3.16.2:

  future: {
    compatibilityVersion: 4
  },
compatibilityDate: '2024-07-11'

  future: {
    compatibilityVersion: 4
  },
compatibilityDate: '2024-07-11'

I've updated nuxt content to 3.4.0. my content files are in root/content and I've always used this code to load my data. In this case root/content/general.md:

const { data: general } = await useAsyncData("general", () =>
  queryContent("general").findOne()
);

if (!general.value) {
  throw createError({
    statusCode: 404,
    statusMessage: "Content Data Page not found",
    fatal: true,
  });
}

const { data: general } = await useAsyncData("general", () =>
  queryContent("general").findOne()
);

if (!general.value) {
  throw createError({
    statusCode: 404,
    statusMessage: "Content Data Page not found",
    fatal: true,
  });
}

In the migration guide, I read that content files don't have to be modified. Using this, my app throws the error: Content Data Page not found. Also, queryContent("/").findOne() does return undefined. Next, I've tried using collections:

const { data: page } = await useAsyncData('general', () => {
  return queryCollection('general').path('/').first()
})

const { data: page } = await useAsyncData('general', () => {
  return queryCollection('general').path('/').first()
})

with the content.config.ts looking like this:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    docs: defineCollection({
      source: '**/*.md',
      type: 'data', // also tried 'page'
    }),
  },
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    docs: defineCollection({
      source: '**/*.md',
      type: 'data', // also tried 'page'
    }),
  },
})

Neither approach works, my .md (also tried .yml) content files cannot be found. Help would be much appreciated.

26 Replies

kapa.ai•4w ago

Hi @davcu. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- I can see you're having issues migrating from Nuxt Content v2 to v3. Let me help you with the correct approach. The Issue The main problem is that your migration approach isn't fully aligned with how Nuxt Content v3 works with collections. Let me explain the key changes needed: 1. In v3, you need to query a specific collection using queryCollection() instead of queryContent() 2. Your collection name in the query must match the collection name in your config 3. The path parameter works differently in v3 Solution Here's how to fix your implementation: 1. Update your content.config.ts First, make sure your collection name matches what you're querying:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    general: defineCollection({  // Changed from 'docs' to 'general'
      source: '**/*.md',
      type: 'page',  // 'page' is recommended for content that maps to pages
    }),
  },
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    general: defineCollection({  // Changed from 'docs' to 'general'
      source: '**/*.md',
      type: 'page',  // 'page' is recommended for content that maps to pages
    }),
  },
})

2. Update your query For a file at content/general.md, you should query it like this:

const { data: general } = await useAsyncData("general", () =>
  queryCollection('general').path('/general').first()
);

if (!general.value) {
  throw createError({
    statusCode: 404,
    statusMessage: "Content Data Page not found",
    fatal: true,
  });
}

const { data: general } = await useAsyncData("general", () =>
  queryCollection('general').path('/general').first()
);

if (!general.value) {
  throw createError({
    statusCode: 404,
    statusMessage: "Content Data Page not found",
    fatal: true,
  });
}

The key difference is that in v3, the path() method expects the full path to the content file, including the collection prefix. For a file at content/general.md, the path would be /general. Alternative Approach If you want to keep your content structure more flexible, you could define a more generic collection:

import { defineCollection, defineContentConfig } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    content: defineCollection({
      source: '**',  // Include all files
      type: 'page',
    }),
  },
})

import { defineCollection, defineContentConfig } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    content: defineCollection({
      source: '**',  // Include all files
      type: 'page',
    }),
  },
})

Then query it like:

const { data: general } = await useAsyncData("general", () =>
  queryCollection('content').path('/general').first()
);

const { data: general } = await useAsyncData("general", () =>
  queryCollection('content').path('/general').first()
);

This approach is similar to what's shown in the migration guide and installation documentation. Raw Content Access If you need access to the raw content data, you can also add a rawbody field to your schema:

import { defineCollection, defineContentConfig, z } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    general: defineCollection({
      source: '**/*.md',
      type: 'page',
      schema: z.object({
        rawbody: z.string()
      })
    }),
  },
})

import { defineCollection, defineContentConfig, z } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    general: defineCollection({
      source: '**/*.md',
      type: 'page',
      schema: z.object({
        rawbody: z.string()
      })
    }),
  },
})

This will allow you to access the raw content as described in the Raw Content documentation. Hope this helps with your migration! Let me know if you have any other questions. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai Right now, I am using type: 'page' but in my app, I am using the .yml as collections of localizations and not really 1:1 represenations of pages. My general.yml looks like this:

company:
  main: Name
  dictionary: Dic
legal:
  termsOfService: Service
  privacyPolicy: Policy

company:
  main: Name
  dictionary: Dic
legal:
  termsOfService: Service
  privacyPolicy: Policy

After importing the data like this:

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

I want to use it like this in my template: {{ general.company.main }} Would type: 'data' be recommended here?

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on your use case, yes, type: 'data' would be more appropriate for your YAML files containing localization data. Let me explain why. Data vs Page Type For your specific scenario where you're using YAML files as collections of localizations rather than page representations, the data type is the recommended approach. Here's why: - type: 'page' is designed for content that has a 1:1 relationship with pages on your site - type: 'data' is ideal for structured data that doesn't directly correspond to a webpage, like your localization data Collection Types Recommended Configuration Here's how you should configure your collection:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',  // Target all YAML files
      type: 'data'  // Use data type for non-page content
    })
  }
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',  // Target all YAML files
      type: 'data'  // Use data type for non-page content
    })
  }
})

Querying Your Data Your current query approach is correct:

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

And yes, you can access nested properties in your template exactly as you described:

{{ general.company.main }}

{{ general.company.main }}

Example from Documentation This approach aligns with the YAML data examples in the Nuxt Content documentation. For example, in the YAML documentation, they show how to define a data collection for YAML files and then query that data. The data type gives you complete control over the schema, allowing you to define custom structures like your nested localization data without the additional page-specific fields that would be generated with the page type. Let me know if you need any further clarification on using YAML data collections in Nuxt Content v3! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai If I use type: 'data', do I HAVE to use a schema? Typescript seems to require one. Also, whenever I change type to 'data', The content files like general.yml cannot be read anymore. The console log here returns 'undefined':

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

console.log("general", general.value);

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

console.log("general", general.value);

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the knowledge sources, I can help clarify your questions about using type: 'data' in Nuxt Content v3. Schema Requirements You don't have to define a schema when using type: 'data', but it's highly recommended for TypeScript integration. Unlike the page type which has built-in schema fields, the data type gives you complete control over the schema structure. From the documentation:

With data collections, you have complete control over the schema, allowing you to define custom structures.

Collection Types Troubleshooting Your YAML Issue If your content files can't be read when using type: 'data', there are a few things to check: 1. File Extension: Make sure you're specifying the correct file extension in your collection source:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      type: 'data',
      source: '**/*.yml', // Make sure this matches your file extension
    })
  }
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      type: 'data',
      source: '**/*.yml', // Make sure this matches your file extension
    })
  }
})

2. Path Parameter: When using path(), make sure you're using the correct path format. For a file at content/general.yml, you should use:

queryCollection("translations").path("/general").first()

queryCollection("translations").path("/general").first()

3. Collection Name: Ensure the collection name in your query matches the one in your config. Example from Documentation Here's an example from the YAML documentation showing how to define and query a YAML collection:

// Define collection
import { defineCollection, defineContentConfig } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    authors: defineCollection({
      type: 'data',
      source: 'authors/**.yml',
      schema: z.object({
        name: z.string(),
        avatar: z.string(),
        url: z.string()
      })
    })
  }
})

// Query data
const { data: author } = await useAsyncData('larbish', () => {
  return queryCollection('authors')
    .where('stem', '=', 'larbish')
    .first()
})

// Define collection
import { defineCollection, defineContentConfig } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    authors: defineCollection({
      type: 'data',
      source: 'authors/**.yml',
      schema: z.object({
        name: z.string(),
        avatar: z.string(),
        url: z.string()
      })
    })
  }
})

// Query data
const { data: author } = await useAsyncData('larbish', () => {
  return queryCollection('authors')
    .where('stem', '=', 'larbish')
    .first()
})

If you're still having issues, you might want to try using the .where() method instead of .path():

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations")
    .where('stem', '=', 'general')
    .first()
);

const { data: general } = await useAsyncData("general", () =>
  queryCollection("translations")
    .where('stem', '=', 'general')
    .first()
);

Let me know if this helps resolve your issue! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai how would I use .where with this path: queryCollection("translations").path("/notifications/notifications").first() ?

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on your question about converting a .path() query to use .where() in Nuxt Content v3, here's how you would do it: To replace this query:

queryCollection("translations").path("/notifications/notifications").first()

queryCollection("translations").path("/notifications/notifications").first()

You would use .where() with the path field like this:

queryCollection("translations")
  .where('path', '=', '/notifications/notifications')
  .first()

queryCollection("translations")
  .where('path', '=', '/notifications/notifications')
  .first()

Alternatively, if you're trying to match by the file name (stem) rather than the full path, you could use:

queryCollection("translations")
  .where('stem', '=', 'notifications')
  .first()

queryCollection("translations")
  .where('stem', '=', 'notifications')
  .first()

The stem field refers to the filename without extension, which might be useful if you're trying to match a specific file regardless of its directory location. If you need to count the number of matches for this query, you could also use the .count() method:

queryCollection("translations")
  .where('path', '=', '/notifications/notifications')
  .count()

queryCollection("translations")
  .where('path', '=', '/notifications/notifications')
  .count()

This approach is documented in the queryCollection documentation, which shows how to use various conditions to filter your content. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai if have source: '**.yml' in my content.config.ts, can it read all .yml files in the main content directory as well as subdirectories?

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the knowledge sources, the pattern '**.yml' in your content.config.ts file would not correctly match all YAML files in both the main content directory and subdirectories. The correct glob pattern to match all YAML files in both the main content directory and all subdirectories would be '**/*.yml'. Here's the correct way to configure your collection to read all YAML files:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml', // This will match all .yml files in content/ and subdirectories
      type: 'data'
    })
  }
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml', // This will match all .yml files in content/ and subdirectories
      type: 'data'
    })
  }
})

From the documentation on Collection Sources, here are some examples of glob patterns: - source: '**' includes all files within the content directory and its subdirectories - source: '**/*.md' includes all Markdown files within the content directory and its subdirectories - source: 'docs/**/*.yml' includes all YML files within the content/docs and its subdirectories - source: '**/*.{json,yml}' includes JSON or YML files within the content directory and all its subdirectories - source: '*.json' includes only JSON files located directly within the content directory, excluding any subdirectories The key difference is that you need the **/ part to match files in subdirectories, and the * before the extension to match any filename. Let me know if you need any further clarification on configuring your content sources! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai I am using source: '*/.yml'. Why would my file in content/notifications/notifications.yml not be found using this code:

const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("path", "=", "/notifications/notifications")
    .first()
);

const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("path", "=", "/notifications/notifications")
    .first()
);

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the knowledge sources and our previous conversation, there are a few potential reasons why your file at content/notifications/notifications.yml isn't being found with your current query. Possible Issues 1. Path Format: The path format in your .where() query might not match how Nuxt Content v3 formats paths for YAML files in collections. 2. Collection Configuration: Your collection might not be correctly configured to include the file. 3. Path vs. Stem: You might need to query by stem (filename) rather than full path. Solutions to Try 1. Check Your Collection Configuration First, ensure your content.config.ts is correctly set up:

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',
      type: 'data'
    })
  }
})

import { defineCollection, defineContentConfig } from '@nuxt/content'

export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',
      type: 'data'
    })
  }
})

2. Try Different Query Approaches For a file at content/notifications/notifications.yml, try these alternative queries:

// Try querying by stem (filename without extension)
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications")
    .first()
);

// Or try with a different path format
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .path("/notifications/notifications")
    .first()
);

// Try querying by stem (filename without extension)
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications")
    .first()
);

// Or try with a different path format
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .path("/notifications/notifications")
    .first()
);

3. Debug with a Query for All Files To better understand what's happening, try listing all files in your collection:

const { data: allFiles } = await useAsyncData("allTranslations", () =>
  queryCollection("translations").all()
);
console.log("All files:", allFiles.value);

const { data: allFiles } = await useAsyncData("allTranslations", () =>
  queryCollection("translations").all()
);
console.log("All files:", allFiles.value);

This will help you see how the paths are actually structured in Nuxt Content v3. 4. Check for Dot Files Exclusion According to the documentation, you might need to check if your configuration is excluding dot files:

defineCollection({
  source: {
    include: '**/*.yml',
    exclude: ['**/.*'] // This would exclude dot files
  }
})

defineCollection({
  source: {
    include: '**/*.yml',
    exclude: ['**/.*'] // This would exclude dot files
  }
})

If you're using a more complex source configuration, make sure it's not accidentally excluding your file Ignore dot files. Let me know which of these approaches helps resolve your issue! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.aiconsole.log("All files:", allFiles.value); gives me all files. the notifications element is this:

{ id: 'translations/notifications/notifications.yml',
    extension: 'yml',
    meta:
     { path: '/notifications/notifications',
        ...data...
       body: [Object],
       title: 'Notifications' },
    stem: 'notifications/notifications',

{ id: 'translations/notifications/notifications.yml',
    extension: 'yml',
    meta:
     { path: '/notifications/notifications',
        ...data...
       body: [Object],
       title: 'Notifications' },
    stem: 'notifications/notifications',

but still, I cannot query this collection using .path('/notifications/notifications') or .where("stem", "=", "notifications"). why is that

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I see the issue now. Looking at the console output you shared, there are a couple of important details that explain why your queries aren't working: 1. The stem value is actually "notifications/notifications" (including the directory), not just "notifications" as we might have expected. 2. The structure of your content item shows that the path is correctly stored as /notifications/notifications, but there might be an issue with how you're querying it. Based on this information, here are the correct ways to query your file:

// Using stem with the full path including directory
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications/notifications")
    .first()
);

// Or using the id directly
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("id", "=", "translations/notifications/notifications.yml")
    .first()
);

// Using stem with the full path including directory
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications/notifications")
    .first()
);

// Or using the id directly
const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("id", "=", "translations/notifications/notifications.yml")
    .first()
);

The issue with your .path() query might be related to how Nuxt Content v3 handles paths internally. According to the queryCollection documentation, the .path() method is specifically designed for the page type collections, and might behave differently with data type collections. Since you're using a data type collection, the .where() method with the correct stem or id value is more reliable. The stem includes the subdirectory path because Nuxt Content v3 uses this to maintain the hierarchical structure of your content. Let me know if using the correct stem value with the directory included resolves your issue! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai I get this error: [CAUSE] SqliteError { message: 'no such column: "path" - should this be a string literal in single-quotes?', stack: 'no such column: "path" - should this be a string literal in single-quotes?\n' +

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I see you're encountering a SQLite error when trying to query your Nuxt Content collection. This error occurs because the path column doesn't exist in your data collection. This is a common issue when working with Nuxt Content v3, especially when using the data type collections instead of the page type. The error message "no such column: 'path'" indicates that you're trying to query a field that doesn't exist in your collection's schema. Why This Happens According to the documentation, the path field is automatically generated for collections with type: 'page', but not for collections with type: 'data':

When you use the page type, Nuxt Content generates several standard fields that are commonly used for web pages. These fields provide structure and are automatically applied to the collection's schema: - path: Generated route path - title: Page title - ...

Collection Types Solutions Based on your previous conversation, you're using YAML files for translations with type: 'data'. Here are your options: 1. Switch to using the id or stem field As we saw in your console output, these fields exist in your data:

const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications/notifications")
    .first()
);

const { data: not } = await useAsyncData("notifications", () =>
  queryCollection("translations")
    .where("stem", "=", "notifications/notifications")
    .first()
);

2. Change your collection type to page If you need to use the path field, you could change your collection type:

defineCollection({
  source: '**/*.yml',
  type: 'page'  // Instead of 'data'
})

defineCollection({
  source: '**/*.yml',
  type: 'page'  // Instead of 'data'
})

3. Define a schema that includes the path field You can explicitly add a path field to your schema:

import { defineCollection, defineContentConfig, z } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',
      type: 'data',
      schema: z.object({
        path: z.string(),
        // other fields...
      })
    })
  }
})

import { defineCollection, defineContentConfig, z } from '@nuxt/content'
export default defineContentConfig({
  collections: {
    translations: defineCollection({
      source: '**/*.yml',
      type: 'data',
      schema: z.object({
        path: z.string(),
        // other fields...
      })
    })
  }
})

The most straightforward solution is to use the stem or id field as shown in your previous console output, since these are guaranteed to exist for all content items. Let me know if you need further assistance with your Nuxt Content queries! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

erztemplerobbaOP•4w ago

@kapa.ai It only works if I use type: 'page'. I can settle for this. The only problem I have is that I need to access the 'body' property of the content file I'm loading. So instead of {{ general.company }}, now the correct object structure would be {{ general.body.company }}. I'd have to restructure a lot in my app. Is there an easy way to fix this?

kapa.ai•4w ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I understand your concern about having to restructure your app to use general.body.company instead of general.company when using type: 'page'. There are a few approaches you can take to address this issue. Option 1: Use a Custom Transformer You can create a custom transformer to modify how your content is processed. This would allow you to "lift" the properties from the body object to the root level:

// ~/transformers/lift-body.ts
import { defineTransformer } from '@nuxt/content'

export default defineTransformer({
  name: 'lift-body',
  extensions: ['.yml'],
  transform(file) {
    // Lift properties from body to root level
    return {
      ...file,
      ...file.body
    }
  },
})

// ~/transformers/lift-body.ts
import { defineTransformer } from '@nuxt/content'

export default defineTransformer({
  name: 'lift-body',
  extensions: ['.yml'],
  transform(file) {
    // Lift properties from body to root level
    return {
      ...file,
      ...file.body
    }
  },
})

Then register this transformer in your Nuxt config:

// nuxt.config.ts
export default defineNuxtConfig({
  content: {
    build: {
      transformers: [
        '~/transformers/lift-body',
      ],
    },
  },
})

// nuxt.config.ts
export default defineNuxtConfig({
  content: {
    build: {
      transformers: [
        '~/transformers/lift-body',
      ],
    },
  },
})

This approach is documented in the transformers section of the Nuxt Content documentation. Option 2: Use Content Hooks You can use the content:file:afterParse hook to modify the content structure:

// nuxt.config.ts
export default defineNuxtConfig({
  hooks: {
    'content:file:afterParse'(ctx) {
      if (ctx.extension === 'yml' && ctx.body) {
        // Copy body properties to root level
        Object.assign(ctx, ctx.body)
      }
    }
  }
})

// nuxt.config.ts
export default defineNuxtConfig({
  hooks: {
    'content:file:afterParse'(ctx) {
      if (ctx.extension === 'yml' && ctx.body) {
        // Copy body properties to root level
        Object.assign(ctx, ctx.body)
      }
    }
  }
})

This approach is documented in the hooks section of the Nuxt Content documentation. Option 3: Create a Composable If you prefer not to modify the content structure itself, you could create a composable that automatically extracts the body:

// composables/useContentBody.ts
export function useContentBody(contentData) {
  if (!contentData.value) return null
  
  // Create a proxy that merges the original object with its body
  return new Proxy(contentData.value, {
    get(target, prop) {
      // Check if property exists at root level
      if (prop in target) {
        return target[prop]
      }
      // Otherwise check in body
      if (target.body && prop in target.body) {
        return target.body[prop]
      }
      return undefined
    }
  })
}

// composables/useContentBody.ts
export function useContentBody(contentData) {
  if (!contentData.value) return null
  
  // Create a proxy that merges the original object with its body
  return new Proxy(contentData.value, {
    get(target, prop) {
      // Check if property exists at root level
      if (prop in target) {
        return target[prop]
      }
      // Otherwise check in body
      if (target.body && prop in target.body) {
        return target.body[prop]
      }
      return undefined
    }
  })
}

Then use it in your components:

const { data: generalData } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

const general = useContentBody(generalData);
// Now you can use general.company instead of general.body.company

const { data: generalData } = await useAsyncData("general", () =>
  queryCollection("translations").path("/general").first()
);

const general = useContentBody(generalData);
// Now you can use general.company instead of general.body.company

Of these options, the transformer approach is probably the most elegant and maintainable solution, as it handles the transformation at the content processing level. Let me know if you need more details on implementing any of these approaches! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@471682580719337482> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Gaming

Programming

Nuxt content v2 -> v3

Did you find this page helpful?