Nuxt•2mo ago

nuxt-umami module not found during typecheck despite being installed

I'm running into an issue with nuxt-umami in my project. When running pnpm lint (which runs nuxt typecheck && eslint .), I'm getting this error: ERROR: Could not load nuxt-umami. Is it installed? However, nuxt-umami is definitely installed in my package.json:

{
  "dependencies": {
    "nuxt-umami": "^3.1.1"
    // ... other deps
  }
}

{
  "dependencies": {
    "nuxt-umami": "^3.1.1"
    // ... other deps
  }
}

My nuxt.config.ts has the proper configuration:

export default defineNuxtConfig({
  modules: [
    'nuxt-umami'
  ],
  umami: {
    id: "xxx",
    host: "https://analytics.site.com",
    autoTrack: true
  }
})

export default defineNuxtConfig({
  modules: [
    'nuxt-umami'
  ],
  umami: {
    id: "xxx",
    host: "https://analytics.site.com",
    autoTrack: true
  }
})

Any ideas what might be causing this? The module works fine during development, it's just the typecheck that's failing. Environment: Nuxt 3.15.4 nuxt-umami 3.1.1 pnpm

13 Replies

kapa.ai•2mo ago

Hi @Sagar Kapoor. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the information provided in the knowledge sources, there isn't a specific mention of the nuxt-umami module or the exact error you're encountering. However, I can provide some insights based on related issues and potential solutions for Nuxt 3 type-checking problems. The issue you're experiencing seems to be related to type-checking in Nuxt 3, specifically when running nuxt typecheck. This command is used to check types throughout your app using vue-tsc, as mentioned in the nuxi typecheck documentation. A few things to consider: 1. Recent Nuxt versions have had some issues with module resolution during type-checking. This was notably discussed in issue #30749, which mentions problems with finding modules after upgrading to Nuxt 3.15.3. 2. As a workaround, you could try adding nuxt-umami to the noExternal list in your nuxt.config.ts:

   export default defineNuxtConfig({
     // ... your existing config
     vite: {
       ssr: {
         noExternal: ['nuxt-umami']
       }
     }
   })

   export default defineNuxtConfig({
     // ... your existing config
     vite: {
       ssr: {
         noExternal: ['nuxt-umami']
       }
     }
   })

This solution was suggested for similar issues in the mentioned GitHub issue. 3. Make sure you have the latest versions of vue-tsc and typescript installed as dev dependencies, as mentioned in the TypeScript documentation for Nuxt. 4. If the problem persists, you might want to try clearing your node_modules and lockfile, then reinstalling dependencies:

   rm -rf node_modules package-lock.json
   pnpm install

   rm -rf node_modules package-lock.json
   pnpm install

5. If none of the above helps, it might be worth checking if there's an open issue in the nuxt-umami repository or creating a new one if there isn't. Remember that while the module works fine during development, type-checking is a separate process that can sometimes have different requirements or encounter different issues. If these suggestions don't resolve your issue, you may need to wait for further updates to Nuxt or nuxt-umami, or consider reaching out to the Nuxt community or nuxt-umami maintainers for more specific assistance. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•2mo ago

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

Kairos•3w ago

Hi, did you ever find a fix to this? Considering implementing this module in a company project.

Sagar KapoorOP•3w ago

A few things to consider here, 1. have you tested this module out on the said project? 2. Are you using pnpm or npm 3. Have you actually encountered any problems? If so are they during the linting part?

Kairos•3w ago

1. Have not done so yet, no, wanted to see what other's experiences were first. 2. Project is currently using npm but would eventually be migrated to pnpm. 3. No and no.

Sagar KapoorOP•3w ago

All right then, I think you should not have to face any problems when using npm as a package manager. I would suggest to test it out for yourself though.

Sagar KapoorOP•3w ago

I did solve this issue by the way, so to undestand what is actually going on, you should check this issue first: https://github.com/dword-design/nuxt-mail/issues/227

GitHub

Cannot find package '@dword-design/functions' · Issue #227 · dword-...

Hey guys! After I installed nuxt-mail on my project, I am not being able to run the project again because I get this error: [12:27:01 AM] ERROR [worker reload] [worker init] Cannot find package &#3...

Sagar KapoorOP•3w ago

And then this one (I am sharing my reply): https://github.com/dword-design/nuxt-mail/issues/227#issuecomment-2602231228

GitHub

Cannot find package '@dword-design/functions' · Issue #227 · dword-...

Sagar KapoorOP•3w ago

@Kairos This should solve the issue for the time being, as mentioned in my comment you will face this issue with other Nuxt modules as well when using pnpm

Kairos•3w ago

That's interesting cus I use pnpm with other Nuxt projects Do you use Volta on your machine?

Sagar KapoorOP•3w ago

nope

Kairos•3w ago

Hmm we use it at my company and when we recently migrated an Angular project to pnpm having a Volta and global install of pnpm caused issues for some people, I never encountered any as I was running Volta Have no idea if this could be related but might be worth a look

Kairos•3w ago

https://volta.sh/

Volta - The Hassle-Free JavaScript Tool Manager

Volta: Start your engines.

Gaming

Programming

nuxt-umami module not found during typecheck despite being installed

Did you find this page helpful?