Daniel Roe

Neither Bridge nor Nuxt 3 support a custom `globalName`, and the last version of this module did not either: https://github.com/nuxt-community/color-mode-module/blob/139b0e68fced030db9035839ffdfd2fa1d80c117/lib/templates/plugin.client.js#L85-L90

As a workaround, you could set globals.readyCallback to `() => 'onNuxtReady'` without touching the rest of your code: https://nuxtjs.org/docs/configuration-glossary/configuration-global-name#the-globals-property

I've rebased and slightly tweaked implementation. I dropped https://github.com/nuxt-community/color-mode-module/pull/121/commits/dab64d8fff2d2d5e92d58d65ac6b629a7877664e as I couldn't see it was needed; what was the issue that caused you to add it @iamahuman?

You need to run `nuxt prepare` (or `nuxt dev`) to generate the types.

You run it with npm or yarn. Typically as a script in your package.json.

Run `npm run dev`. You can find out more at https://docs.npmjs.com/cli/v8/commands/npm-run-script. For running arbitrary binaries in your node_modules with npm, check out the info on npx: https://docs.npmjs.com/cli/v8/commands/npx. (So you could...

That's an error that npm is giving you. It sounds pretty straightforward. Definitely investigate it. Maybe you are running the command in the wrong directory?

Can you explain a bit about how/why Nuxt needs to extend from another tsconfig? What values in that tsconfig are important for the nuxt project?

Workaround for now (we'll need to investigate in Nuxt what the root cause is here): ```js import { defineNuxtConfig } from '@nuxt/bridge' export default defineNuxtConfig({ bridge: { resolve: false, }...

That's an unrelated issue. See https://v3.nuxtjs.org/concepts/esm. **Edit**: Forgive my too hasty assumption; are you saying this occurs only when you set `resolve: false`?