-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when building with a module for Edge Network services (cloudflare pages, vercel): RollupError: "toPath" is not exported. #24738
Comments
This is due to globby: sindresorhus/globby#260 Unfortunately, due to the response of the package author, I doubt this will get fixed anytime soon: sindresorhus/unicorn-magic#1 Is this dependency really necessary? |
If, like me, you are using optimizeDeps: {
exclude: ["@nuxt/kit"],
} Further details are explained here: storyblok/storyblok-nuxt#662 |
The issue here is that your code (or a module you use) is importing In this case it is here: https://github.com/megapossy/nuxt-tawing-supabase/blob/main/src/runtime/server/services/index.ts#L1 |
wow it works now. @nuxt/kit should not be imported. Thank you so much! |
@danielroe I quite dont understand the fix here? In the example, https://github.com/megapossy/nuxt-tawing-supabase/blob/main/src/runtime/server/services/index.ts#L1, its importing the |
You can log with |
Environment
Working directory: /home/tawing-ubuntu/work/aceeagle/nuxt-tawing-supabase 5:50:11 AM
Nuxt project info: 5:50:11 AM
Reproduction
https://github.com/megapossy/nuxt-tawing-supabase
Will work.
Will have
RollupError: "toPath" is not exported.
errorsDescribe the bug
Error Output:
Error occurs only if I preset nitro to edge rendering.
I created a module that is used on the nitro server only. Whenever I build a project using that module for edge rendering preset that error occurs., but no errors when building for a normal node server.
This module is using "@supabase/supabase-js"
Additional context
Tried to downgrade nitro and nuxt to 2.7.0 and 3.8.0 respectively as suggested in #24387.
Logs
No response
The text was updated successfully, but these errors were encountered: