N
Nuxt•2mo ago
Hum+

Getting a error from [email protected]

Uncaught SyntaxError: The requested module '/_nuxt/@fs/C:/Users/justserdar/Documents/GitHub/.../node_modules/.pnpm/[email protected]/node_modules/unhead/dist/index.mjs?v=4b4d1985' does not provide an export named 'getActiveHead'
10 Replies
kapa.ai
kapa.ai•2mo ago
Hi @Hum+. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Hum+
Hum+OP•2mo ago
Ahh it's i18n...
kapa.ai
kapa.ai•2mo ago
---------------------- This error is related to the upgrade of Unhead to version 2 in Nuxt 3.16.0. The getActiveHead function was removed in Unhead v2 as part of removing the implicit context implementation, which was one of the main reasons for the v2 upgrade. Why this is happening In Unhead v2, the implicit context implementation was removed to prevent potential memory leaks. This implementation previously kept a global instance of Unhead available for use in non-Vue contexts, represented by the getActiveHead() function that your code is trying to use. How to fix it The most common cause of this error is using an older version of a Nuxt module (particularly @nuxtjs/i18n) with Nuxt 3.16.0+. Here are the solutions: 1. Update your modules: If you're using @nuxtjs/i18n, update it to version 9.3.0 or later: 
   npm install @nuxtjs/i18n@latest
   # or
   pnpm add @nuxtjs/i18n@latest
   
   npm install @nuxtjs/i18n@latest
   # or
   pnpm add @nuxtjs/i18n@latest
2. Check other modules: Other modules like nuxt-og-image might also need updates if they depend on the removed function. 3. Configuration option: If you need to maintain compatibility with older modules temporarily, you can enable legacy mode in your nuxt.config.ts: 
   export default defineNuxtConfig({
     unhead: {
       legacy: true
     }
   })
   
   export default defineNuxtConfig({
     unhead: {
       legacy: true
     }
   })
Additional information This change was part of the Unhead v2 upgrade in Nuxt 3.16.0. The upgrade removed several deprecated features including: - Removed props: vmid, hid, children, body - Promise input is no longer supported - Tags are now sorted using Capo.js by default If you're using any of these features, you'll need to update your code according to the Unhead v2 migration guide. Nuxt Upgrade Guide provides more details about the migration process. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai•2mo ago
<@544244461228654592> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Hum+
Hum+OP•2mo ago
export function useSetI18nParams(seoAttributes) {
    const common = initCommonComposableOptions();
    const head = getActiveHead();
    const i18n = getComposer(common.i18n);
    const router = common.router;
    const locale = getLocale(i18n);
    const locales = getNormalizedLocales(getLocales(i18n));
    const _i18nParams = ref({});
    const experimentalSSR = common.runtimeConfig.public.i18n.experimental.switchLocalePathLinkSSR;
export function useSetI18nParams(seoAttributes) {
    const common = initCommonComposableOptions();
    const head = getActiveHead();
    const i18n = getComposer(common.i18n);
    const router = common.router;
    const locale = getLocale(i18n);
    const locales = getNormalizedLocales(getLocales(i18n));
    const _i18nParams = ref({});
    const experimentalSSR = common.runtimeConfig.public.i18n.experimental.switchLocalePathLinkSSR;
harlan
harlan•2mo ago
yes you should upgrade to the latest version of i18n
Hum+
Hum+OP•2mo ago
Ty, I told Sandro too, we we're both tired when we looked at it yday night surprised kapa just one shot it milleseconds after me noticing what was wrong
harlan
harlan•2mo ago
oh ye i didn't even bother reading it that's pretty good, maybe it's synced to gh issues 🤔
Hum+
Hum+OP•2mo ago
we can close this post tho now closed it oh btw upgrading to latest i18n doesnt work you need to add a dependency @harlan pnpm add @intlify/message-compiler (sorry for pinging, but might think u'd miss this now in the closed post)
Hum+
Hum+OP•2mo ago
found the 6h old issue https://github.com/nuxt-modules/i18n/issues/3415
GitHub
Could not resolve module "@intlify/message-compiler/dist/message-co...
Environment Operating System: Darwin Node Version: v20.19.0 Nuxt Version: 3.16.0 CLI Version: 3.22.5 Nitro Version: 2.11.5 Package Manager: [email protected] Builder: - User Config: modules, devtools, cs...

Did you find this page helpful?