Rollup failed to resolve import "unenv/runtime/mock/noop"

Original message was deleted

kapa.ai•3/7/25, 9:21 PM

Hi @Quentin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•3/7/25, 9:21 PM

----------------------
This error appears to be related to a dependency resolution issue after updating to Nuxt 3.16. The error indicates that Rollup (the bundler used by Vite in Nuxt) is unable to resolve an import from the unenv/runtime/mock/noopunenv/runtime/mock/noop path.

Based on the knowledge sources, there have been several recent changes in Nuxt related to dependencies and imports that might be causing this issue:

There was a PR that dropped unneeded schema dependencies, including explicit dependencies on libraries like unimportunimport and others, which could affect how dependencies are resolved GitHub PR #30411.
Similar Rollup errors have been reported by other users after upgrading to newer Nuxt versions, as seen in issues #29804 and #28850.

To resolve this issue, you can try the following steps:

Clear your cache and node_modules:```rm -rf node_modules .nuxt .outputnpm cache clean --forcenpm install```
If you're using the clientNodeCompatclientNodeCompat experimental feature, make sure you're properly setting it up as mentioned in the documentation Experimental Features.
Check if you have any custom Vite or Rollup configurations that might be interfering with the dependency resolution.

If the issue persists, you might need to explicitly add the missing dependency to your external options in your nuxt.config.tsnuxt.config.ts:

export default defineNuxtConfig({
  vite: {
    build: {
      rollupOptions: {
        external: ['unenv/runtime/mock/noop']
      }
    }
  }
})

export default defineNuxtConfig({
  vite: {
    build: {
      rollupOptions: {
        external: ['unenv/runtime/mock/noop']
      }
    }
  }
})

kapa.ai•3/7/25, 9:21 PM

This appears to be a dependency resolution issue that can happen during major version updates, especially when there have been changes to how dependencies are managed in the framework.

If these steps don't resolve your issue, you might want to consider creating a minimal reproduction of the problem and opening an issue on the Nuxt GitHub repository.

Kapa: I notice you're using Nuxt 3.16, which is quite recent, and these types of dependency resolution issues are sometimes fixed in patch releases, so also make sure you're on the latest patch version of Nuxt 3.16.x.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•3/7/25, 9:21 PM

@179707857120395271 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

h0ranga•3/12/25, 9:29 AM

I have the exact same issue, it just appeard today...

h0ranga•3/12/25, 9:30 AM

have you solved anything ?

h0ranga•3/13/25, 10:02 AM

yep I found the solution.
in my case the path in my error was something like this:
D:\folder\user\node_modules\unenv\dist\runtime\runtime\mock\noop.mjs

as you can see there is this \runtime\runtime bug in the path.

what I did was to run: npm install unenv@latest --force
and it solved the path & fixed the error I was getting.

Rollup failed to resolve import "unenv/runtime/mock/noop"

Similar Threads

Similar Threads

Similar Threads