How do I disable Visual Editing (and react deps)?

[Lippiece]

I'm not using Visual Editing, but still have problems like #1277 and #1284 which breaks HMR. Looks like this feature has some react dependencies which not always work well. So would it be possible to ditch it?

I should note that it only happens if I install deps with bun.

The current workaround (nuxt.config.ts):

  vite: {
    optimizeDeps: {
      include: ['react-compiler-runtime', 'react', 'react-dom']
    },
  },

This workaround makes builds and dev compiling at least 5 times longer.

[jimrowetpa]

I would also be interested in being able to turn off visual editing.

[jakewhiteley]

This appears to be the only current workaround for

Uncaught (in promise) SyntaxError: The requested module '/_nuxt/@fs/C:/wamp64/www/temp/nuxt-sanity-demo/node_modules/react-compiler-runtime/dist/index.js?v=f8fd7759' does not provide an export named 'c'

and

Uncaught (in promise) SyntaxError: The requested module '/_nuxt/@fs/C:/wamp64/www/temp/nuxt-sanity-demo/node_modules/react/index.js?v=8bc1c419' does not provide an export named 'useSyncExternalStore'

errors mentioned in other tickets, but this is not a viable solution IMO - for one it requires users to search Github issues before they can get Nuxt to compile a single page.

is this something controllable by the package author, or is it an issue in react-compiler-runtime?

[richgcook]

This is unfortunately still an issue...

Nuxt 3.19.3 (with Nitro 2.12.7, Vite 7.1.9 and Vue 3.5.22)

[navidmirzaie]

I have got exactly the same issue with Nuxt 4.1.3 and "@nuxt/ui": "^4.0.1",
"@nuxtjs/sanity": "^2.0.0".

[nomve]

I "fixed" this issue for me by downgrading @sanity/visual-editing. We use yarn, so in package.json adding this below fixed it

"resolutions": {
    "@sanity/visual-editing": "1.8.22"
  }

[niemes]

At the moment React deps break the use of nuxt sanity after any sanity query. I don't use the visual editing only load content and even without a serializer it breaks the module. Cannot upgrade to 2.0.0 for now.

Content load -> try to gets react compiler -> crash