#Trouble with nuxtjs/medusa module
4 messages · Page 1 of 1 (latest)
Hi @clear kraken. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
I apologize, but I don't have any specific information about a @nuxtjs/medusa module in the provided knowledge sources. However, the error you're encountering seems similar to some issues that have been reported with Nuxt 3.15.3.
Based on the information available, this appears to be a module resolution issue that has affected several Nuxt users after upgrading to version 3.15.3. While I don't have a specific solution for the medusa module, there is a general workaround that has helped with similar issues:
You can try adding the problematic module to the noExternal list in your Nuxt configuration. Here's how you might do it:
// nuxt.config.ts
export default defineNuxtConfig({
vite: {
ssr: {
noExternal: ['qs']
}
}
})
This workaround was suggested for similar issues in this GitHub issue.
If this doesn't resolve the issue, you might want to try:
- Clearing your Nuxt cache by running
npx nuxi cleanup - Ensuring all your dependencies are up to date
- If possible, try downgrading to Nuxt 3.15.2 to see if the issue persists
If the problem continues, I recommend creating a minimal reproduction of the issue and reporting it on the Nuxt GitHub repository. The Nuxt team is usually quick to address such problems, especially if they're regressions in a recent version.
Remember to always check the official Nuxt documentation and GitHub issues for the most up-to-date information on known issues and their solutions.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@clear kraken Kapa.ai is still learning and improving, please let me know how I did by reacting below.