#nuxt-og-image - Failed to load empty.mjs from unenv

10 messages · Page 1 of 1 (latest)

vital siren
#

I started getting this error out of thin air after trying to launch my nuxt project in dev mode today

[nitro 3:37:29 PM]  ERROR  Error: Could not load /Users/krists/Desktop/Projects/[redacted]/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/Users/krists/Desktop/Projects/[redacted]/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'


undefined

Ive already tried reinstall node_modules, clearing cache, updating packages and nothing has seemed to fix this. Any ideas ?

hardy raptorBOT
#

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

#

This issue appears to be related to a compatibility problem between Nuxt 3.16.0 and the nuxt-og-image module, specifically with the unenv dependency. Based on the knowledge sources, several users have encountered similar errors after upgrading to Nuxt 3.16.0.

The error occurs because of changes in how unenv is handled in newer versions of Nuxt. According to the information in the knowledge sources, there are a few potential solutions:

  1. Add unenv as a dev dependency:
    One user reported that manually adding unenv as a dev dependency resolved the issue:

    npm add -D unenv
# or
pnpm add -D unenv
# or
yarn add -D unenv

  2. Update unenv to the latest version:
    As mentioned in this GitHub issue, updating unenv to the latest version helped resolve similar errors.

  3. Check for module compatibility:
    This appears to be part of a broader issue with module compatibility in Nuxt 3.16.0. Several modules including nuxt-og-image have had issues with the unenv dependency in this version.

The error specifically mentions a path issue with unenv/dist/runtime/runtime/mock/empty.mjs, which suggests there might be a problem with how the module paths are being resolved. This is consistent with the issues reported in the GitHub discussions where changes in Nuxt 3.16.0 affected how dependencies are handled.

If the above solutions don't work, you might need to temporarily downgrade to Nuxt 3.15.4 until the compatibility issues are fully resolved.

Would you like me to provide more specific instructions for any of these potential solutions?

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

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

vital siren
#

@hardy raptor im using nuxt 3.15.4

hardy raptorBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

Thank you for clarifying that you're using Nuxt 3.15.4. This is important information since the error you're experiencing is not related to the Nuxt 3.16.0 upgrade issues I initially thought might be the cause.

Since you're on Nuxt 3.15.4, the issue is likely related to a different compatibility problem with the nuxt-og-image module and unenv. Based on the knowledge sources, there are still a few approaches you can try:

  1. Add unenv as a direct dependency:
    Even though you're not on 3.16.0, manually adding unenv might help resolve path issues:

    npm add -D unenv
# or
pnpm add -D unenv
# or
yarn add -D unenv

  2. Check for dependency conflicts:
    The error suggests there might be a path resolution issue with unenv. You could try running a dependency check command like npm ls unenv or pnpm why unenv to see if there are multiple versions or conflicts.

  3. Rebuild with specific architecture flags:
    If you're using Sharp (which is often used with image processing), you might need to rebuild it with specific architecture flags as mentioned in this Stack Overflow post:

    npm rebuild --arch=x64 --platform=linux --libc=musl sharp

    (Adjust the architecture and platform flags according to your system)

  4. Clear Nuxt cache thoroughly:
    Try a more thorough cache clearing:

    npx nuxi cleanup

The specific error about empty.mjs suggests there might be an issue with how the mock modules are being loaded from unenv. This could be related to how nuxt-og-image is interacting with unenv in your project.

#

If none of these solutions work, you might want to consider temporarily removing nuxt-og-image until the compatibility issue is resolved, or check if there's a specific version of nuxt-og-image that works better with Nuxt 3.15.4.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

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

gleaming pewter
#

you're using unenv v2 (released with nuxt 3.16) with an old version of og image