new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Nuxt · API · all subjects

kit

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

getViteConfig example using Kit utilities

To access the Vite config that Nuxt uses in a Nuxt Kit integration, call loadNuxt with options cwd: process.cwd(), dev: false, and overrides: { ssr: false }. Then create a Promise that listens to the 'vite:extend' hook to capture the config, and call buildNuxt(nuxt) to trigger the hook. After the config is resolved or an error is caught, call nuxt.close() to clean up. The example imports buildNuxt and loadNuxt from '@nuxt/kit'.

Accessing Nuxt Vite config from integrations

When building integrations that need runtime access to Vite or webpack config, Kit utilities can be used to extract this configuration. Projects like histoire, nuxt-vitest, and @storybook-vue/nuxt implement this pattern.

Give your agent this brain