react-compiler-runtime dependency issue

[jakewhiteley]

Version

module: 1.14.1
nuxt: 4.0.1

Reproduction

⚠️ without a minimal reproduction we wont be able to look into your issue

Link:
GitHub repository

What is expected?

The site compiles.

What is actually happening?

The following error is present in the browser console:

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=c79bc471' does not provide an export named 'c' (at mutations.js?v=c79bc471:1:10)

Steps to reproduce

Clone the above repo, run npm i && npm run dev then go to localhost:3000.

It is literally a brand new nuxt install with only the sanity module added, and then a single query in app.vue

Checklist

• I have tested with the latest Nuxt version and the issue still occurs
• I have tested with the latest module version and the issue still occurs
• I have searched the issue tracker and this issue hasn't been reported yet

What is expected?

As raised in #1249, the most recent version appears to simply not work due to a dependency issue.

[th-km]

I'm experiencing the same issue with a fresh Nuxt ^4.0.3 and @nuxtjs/sanity 1.14.1 install.
I have a reproduction here. But in my case, it's not only a warning in the browser console but a crash with an error 500.

Installing the required dependencies and adding this to your nuxt.config will solve the issue for now:

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

[jgs-thg]

Same issue after attempting to update to Nuxt 4.0.3, and @nuxtjs/sanity at 1.14.1. Downgrading Nuxt to 3.18.3 and @nuxtjs/sanity to 1.13.3 solves the issue, as I don't see installing React and including it to be a viable solution. Unless I'm misunderstanding it, and it's not actually including it in the build.

[th-km]

It definitely feels strange to include those dependencies in a Nuxt project. When using the latest Nuxt and @nuxtjs/sanity version, the live preview also stopped working for me with a websocket connection issue.

[hacknug]

I thought this was related to the use of visual editing but the repro clearly shows how it doesn't require visual editing or live mode to be enabled for the issue to occurr 🤔

Definitely the same issue as #1159 although with a much more minimal repro. The issue is most likely related to changes on the dependency chains I highlighted in this comment: #1159 (comment)

[danielroe]

resolved in 7741824

[th-km]

Hi @danielroe, this issue still occurs for me even after upgrading to 2.0.0. Here is a minimal repro. When I start the dev command, the app starts with the initial data but quickly crashes with a 500 error.

[danielroe]

@th-km what if you remove those react dependencies?

[th-km]

@danielroe This issue is happening on a larger codebase without the React dependencies, but I removed them from the repro to see, and I can confirm that it's still happening on my side.

[devzom]

In my case upgrading to 2.0.0 (pnpm) doesn't really changed anything.
As mentioned in previous comments hadn't issue with 500 anytime but always seen the console.error. Until had the react deps installed and
optimizeDeps: { include: ['react-compiler-runtime', 'react', 'react-dom'] } in nuxt.config, no issue but when uninstalled pkgs and removed optimizeDeps console.error is back.