-
Notifications
You must be signed in to change notification settings - Fork 21
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
[BUG] [ERROR] Could not resolve "uuid" #223
Comments
gethassaan
changed the title
[BUG] [ERROR] Build failed with 1 error: [ERROR] Could not resolve "uuid"
[BUG] [ERROR] Could not resolve "uuid"
Jan 3, 2025
Running into the same problem too. Hence the upvote |
including a repro as a github repo that we can clone and investigate would help speed up the investigation. |
Thanks, I'll take a look this week. |
hey @vicb, unfortunately I couldn’t follow your instructions. And I wanted to ask you
|
dario-piotrowicz
moved this to Todo
in `@opennextjs/cloudflare` prioritization and tracking
Jan 16, 2025
dario-piotrowicz
moved this from Todo
to P1 - need to be addressed
in `@opennextjs/cloudflare` prioritization and tracking
Jan 16, 2025
I didn't get a chance to at the issue yet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
.open-next/.next/standalone/node_modules/@smithy/middleware-retry/dist-cjs/index.js:51:26: 51 │ var import_uuid = require("uuid");
The module "./dist/commonjs-browser/index.js" was not found on the file system:
.open-next/.next/standalone/node_modules/@smithy/middleware-retry/node_modules/uuid/package.json:34:19: 34 │ "require": "./dist/commonjs-browser/index.js"
The text was updated successfully, but these errors were encountered: