Module integration troubles #340
Replies: 2 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Closing as outdated — significant module + bundling changes since this was filed and no clear repro of the build error. If you can still reproduce on the latest |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hello there!
I recently installed the @nuxt/scripts module to embed a Vimeo player into my Nuxt 3 application. However, after running npx nuxi@latest module add scripts, I started experiencing issues that appear to break my application during the build process. Specifically, errors are triggered during the nuxt prepare call, and the following modules are implicated:
Here’s a screenshot of the errors:

Initially, I suspected the issue was related to @nuxt/ui and nuxt-graphql-codegen. I spent significant time debugging these packages during the build phase but later identified that the root cause appears to involve the require API in Node.js.
Observed Behavior:
It seems that require() no longer directly imports default exports. Instead, it wraps the imported module as follows:
{ default: importedModule }This causes failures in modules expecting the default export directly.
I prefer to use @nuxt/scripts since I plan to integrate additional APIs offered by this module in the future. However, I’d like to better understand what’s causing the integration failure and whether a solution exists.
Thank you for your support!
Beta Was this translation helpful? Give feedback.
All reactions