KHi @Chriso. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
K----------------------
Your approach of colocating component files (Vue, schema, types, etc.) within a single directory (e.g.,
Here’s what is relevant from the sources:
Your approach of colocating component files (Vue, schema, types, etc.) within a single directory (e.g.,
app/storyblok/teaser/) is a solid organizational strategy and aligns well with modular, maintainable code practices. However, based on the knowledge sources provided, there is no official Nuxt or Nuxt Content documentation that directly addresses Storyblok "Schema as Code" setups or the use of import.meta.glob for schema management in this context.Here’s what is relevant from the sources:
K- Nuxt supports custom folder structures for arbitrary code, including types and utility files. You can create your own folders (like
/typesor/storyblok) and either import files manually or configure auto-imports via theimports.dirsoption in
if you want auto-imports for certain directories. However, you must ensure your custom folders do not conflict with future Nuxt reserved folders. Manual imports are always safe and flexible for custom setups Where can arbitrary code be placed in Nuxt 3?.nuxt.config.ts - There is no explicit documentation on using
import.meta.globfor schema files or on excluding such files from client bundles. Nuxt’s Vite integration allows you to use Vite plugins and advanced configuration, so a custom Vite plugin could be a solution for excluding files from the client bundle, but this is not covered in the official docs Using Vite Plugins in Nuxt. - The Nuxt Content module and Studio provide schema-based content management, but this is focused on content collections and app config schemas, not Storyblok schemas or external CMS schema management Defining Collections, Customize edition.
K- Colocating related files (component, schema, types) is a maintainable approach and supported by Nuxt’s flexible directory structure.
- You can use
import.meta.globto gather files for server-side scripts, but you’ll need to ensure these files are not included in the client bundle. This may require custom Vite configuration, which is possible but not documented in the official Nuxt sources. - Manual imports and custom folders are safe, but be mindful of potential future folder name conflicts with Nuxt.
- There is no official Nuxt or Nuxt Content support or guidance for Storyblok schema management as code, so your approach is custom and community-driven.
build.rollupOptions or a custom plugin, but the knowledge sources do not provide a ready-made solution for this.If you want to share or discuss your approach further, the Nuxt community (GitHub Discussions, Discord) may have more real-world examples and advice.
I'm sorry, but the knowledge sources do not contain enough information to provide a definitive, officially recommended setup for Storyblok schema as code in Nuxt. Your approach is valid, but it is not covered in the official documentation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
K@756569126184681542 Kapa.ai is still learning and improving, please let me know how I did by reacting below.
