Hi there,

Thanks for this project!

I have installed the project with this command: npx [email protected] init -t themes/content-wind my-website

How can i customize the layout? This is possible?

Pnpm version: 7.1.2

~/tmp/docs-test via  v16.14.2
❯ pnpm install --shamefully-hoist

~/tmp/docs-test via  v16.14.2 took 10s
❯ pnpm dev

> @ dev /Users/yesyes/tmp/docs-test
> nuxi dev
Nuxt CLI v3.0.0-rc.3                                                                              07:18:56
                                                                                                  07:18:56
  > Local:    http://localhost:3000/
  > Network:  http://192.168.1.13:3000/

✔ Using ~/components/content for components in Markdown                             @nuxt/content 07:19:00
ℹ Using default Tailwind CSS file from runtime/tailwind.css                      nuxt:tailwindcss 07:19:00
ℹ Merging Tailwind config from ~/tailwind.config.js                              nuxt:tailwindcss 07:19:00
ℹ Tailwind Viewer: http://localhost:3000/_tailwind/                              nuxt:tailwindcss 07:19:00
ℹ Vite server warmed up in 582ms                                                                  07:19:03
ℹ Vite client warmed up in 2660ms                                                                 07:19:03
✔ Vite server built in 2000ms                                                                     07:19:05
✔ Nitro built in 1317 ms                                                                    nitro 07:19:06
TypeError [ERR_PACKAGE_IMPORT_NOT_DEFINED]: Package import specifier "#imports" is not defined in package /Users/yesyes/tmp/docs-test/node_modules/.pnpm/@[email protected]/node_modules/@nuxt/content-edge/package.json imported from /Users/yesyes/tmp/docs-test/node_modules/.pnpm/@[email protected]/node_modules/@nuxt/content-edge/dist/runtime/components/ContentDoc.mjs
    at new NodeError (node:internal/errors:371:5)
    at throwImportNotDefined (node:internal/modules/esm/resolve:442:9)
    at packageImportsResolve (node:internal/modules/esm/resolve:819:3)
    at moduleResolve (node:internal/modules/esm/resolve:973:21)
    at defaultResolve (node:internal/modules/esm/resolve:1080:11)
    at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:40)
    at link (node:internal/modules/esm/module_job:78:36) {
  code: 'ERR_PACKAGE_IMPORT_NOT_DEFINED'
}

I have noticed a rendering issue when a route is visited for the first time after a build with NITRO_PRESET=azure

Steps to reproduce:

git clone [email protected]:Atinux/content-wind.git cw-issue
cd cw-issue
yarn
NITRO_PRESET=azure yarn build
npx @azure/static-web-apps-cli start .output/public --api-location .output/server

This should start the azure static web app cli on localhost:4280 which proxies requests to static pages and functions.

When I navigate to localhost:4280 the / route renders nicely. Clicking About in the nav bar yields the results in the image below. Reloading http://localhost:4280/about shows the properly rendered /about route.

Alternately, if I first navigate to localhost:4280/about it will render nicely. Then clicking on the Home link in the nav bar shows raw json from the path="/" content query.

Seems to need a full reload on each route. I suspect there is some state preserved serverside because after all the routes have been hit once, I can open the pages in a different browser or incognito and the issue is no longer there.

I see this issue when running builds locally and also when builds are freshly deployed to azure static web apps.

I'm guessing this might not be the right place to report this. I would appreciate any debug tips or redirects.

I ran npx tailwindcss init and it generates tailwind.config.js.

I put this in there:

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ["./content/**/*.md"],
  theme: {
    extend: {},
  },
  plugins: [],
}

and expected TailwindCSS Intellisense to "just work", but it's not 🤔

Anyone have a solution?

Reproduction

1. Cloned the repo
2. npm i
3. npm run dev

Errors in Terminal and the website doesn't show up

 ERROR  Missing "./dist/app/entry" export in "nuxt3" package

i Vite server using experimental vite-node...                                              

 ERROR  Missing "./dist/app/entry" export in "nuxt3" package

i @nuxt-themes/config-edge v0.0.1-27648855.385c9ae enabled!                                             
i Using Content Wind by Sebastien Chopin (@Atinux)                                                      
√ Design Tokens built in 120ms                                                                  

 ERROR  Rollup error:  Unexpected token (Note that you need plugins to import files that are not JavaScript)

√ Nitro built in 1503 ms

The localhost page is stuck on this:

And this error in Console:

GET http://localhost:3000/ 503 (Server Unavailable)

Hi,

It would be cool if this could support code diffs, like seen here:

In addition to file names and tabs like:

I wasn't sure if these are natively supported by Nuxt Content v2 already, and needed some form of syntax or flag. These are in the docs.

Use experimental nuxt-config-schema to define app config from nuxt.schema.ts. This way we can annotate documentation and have custom resolvers for appConfig.

input:

export default defineNuxtConfigSchema({
  appConfig: {
    cover: '/cover.jpg',
    socials: {
      /** Twitter handle */
      twitter: '',
      /** Github repository name */
      github: '',
    }
  }
})

output: (.nuxt/schema/nuxt.schema.d.ts)

export interface NuxtUserConfig {
   appConfig: {
    /** @default "/cover.jpg" */
    cover: string,

    socials: {
       /**
        * Twitter handle
        * @default ""
       */
       twitter: string,

       /**
        * Github repository name
        * @default ""
       */
       github: string,
    },
  },
}

The current theme switcher button shows Sun icon when it's light mode and Moon icon when it's in dark mode, which is actually quite the opposite of how its supposed to behave. It should be Moon when it's in light mode and vice-versa.

Can open a PR if you feel like this needs to be fixed.

Hello, i don't find how to display the excerpt on a list of articles.

 <div v-for="article in articles" :key="article._path">
      <h2>{{ article.title }}</h2>
      <ContentRenderer :value="article" :excerpt="true" />
    </div>

this code display all the content of page :

Thanks for help 👍🏼

Getting this error spammed after I try to visit the locally served app. Using M1 mac, yarn 1.22.17 - any idea? I basically just cloned and installed dependencies.

[nuxt] [request error] fetch failed ()
  at createError (./node_modules/h3/dist/index.mjs:191:15)
  at nodeHandler (./node_modules/h3/dist/index.mjs:381:21)
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
  at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
  at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
  at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:336:16)
  at async nodeHandler (./node_modules/h3/dist/index.mjs:389:9)
  at async ufetch (./node_modules/unenv/runtime/fetch/index.mjs:9:17)
  at async $fetchRaw2 (./node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
  at async Object.errorhandler [as onError] (./.nuxt/dev/index.mjs:336:16)
[h3] [unhandled] H3Error: fetch failed ()
    at createError (file:///Users/bird/GitHub/wtfffff/node_modules/h3/dist/index.mjs:191:15)
    at nodeHandler (file:///Users/bird/GitHub/wtfffff/node_modules/h3/dist/index.mjs:381:21)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ufetch (file:///Users/bird/GitHub/wtfffff/node_modules/unenv/runtime/fetch/index.mjs:9:17)
    at async $fetchRaw2 (file:///Users/bird/GitHub/wtfffff/node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
    at async Object.errorhandler [as onError] (file:///Users/bird/GitHub/wtfffff/.nuxt/dev/index.mjs:336:16)
    at async nodeHandler (file:///Users/bird/GitHub/wtfffff/node_modules/h3/dist/index.mjs:389:9)
    at async ufetch (file:///Users/bird/GitHub/wtfffff/node_modules/unenv/runtime/fetch/index.mjs:9:17)
    at async $fetchRaw2 (file:///Users/bird/GitHub/wtfffff/node_modules/ohmyfetch/dist/chunks/fetch.mjs:131:20)
    at async Object.errorhandler [as onError] (file:///Users/bird/GitHub/wtfffff/.nuxt/dev/index.mjs:336:16) {
  statusCode: 500,
  fatal: false,
  unhandled: true,
  statusMessage: 'Internal Server Error'
}

I'm using the unocss module and my classes have duplicated definitions due to both frameworks generating their own styles.

I'd like a way to opt-out, similar to how the typography setting works.

Hi, I'm just setting up the project and I'm getting 2 errors in vscode.

These errors do not affect the functionality of the project, but I find them a bit annoying during development.

List.vue:

ColorModeSwitch.vue:

Is it only me who has these errors and how can I fix them?

I might have already found a solution for the first error:

<script setup lang="ts">
const { flatUnwrap } = useUnwrap()
const slots = useSlots()

defineProps({
  icon: {
    type: String,
    default: 'ph:check-circle-duotone'
  }
})
</script>

<template>
  <ul class="p-0">
    <li v-for="(item, index) of flatUnwrap((slots.default && slots.default()) ?? [], ['ul'])" :key="index" class="flex pl-0 space-x-2 my-1 items-center">
      <Icon :name="icon" class="flex-shrink-0 w-6 h-6 mt-1 text-emerald-500" />
      <span><ContentSlot :use="() => item" unwrap="li" /></span>
    </li>
  </ul>
</template>

For the second one I haven't found anything yet, but I don't seem to be the only one with this problem: https://github.com/nuxt-modules/color-mode/issues/168

I would like to use Nuxt Content to generate HTML form Obsidian files (see https://www.obsidian.md). Obsidian uses the Wikilink syntax to reference files.

e.g. [[anotherfile]] references the file "anotherfile.md" in the current directory.

This syntax is (as far as I could see) not supported by nuxt content. I could do some preprocessing to convert that syntax to the standard markdown syntax. But that would not work if I use the content-directory directly as the root folder for the Obsidian vault.

Therefore it would be great if you could provide a remark plugin and a configuration example that handles that.