Final build is broken when using pnpm #22205
Unanswered
Nick-Mazuk
asked this question in
Help
Replies: 1 comment 1 reply
-
|
--shamefully-hoist not working for me.. is there another solution? |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Issue
I just recently switched from using npm to pnpm workspaces in a monorepo with a Next.js project. However, since the switch, the final builds are broken.
When you visit the homepage of the website, the following error message appears in the "Functions" tab on the Vercel dashboard.
I can confirm that the package
@hapi/acceptis in thepnpm-lock.yaml. Next.js is the only package that requires@hapi/accept.Debug steps
@hapi/acceptis not in thepnpm-lock.yaml, it ispnpmworkspacepnpmis strict about making sure your dependencies are declared inpackage.json(and all of your dependency's dependencies). So I created a build on my local machine with everything installed. The build has the same issues (and still works in development)resolveRequestto compare symlinks, rather thanfs.realpathSync(fix pnpm on Vercel) #20949Metadata
next: 10.0.7
Beta Was this translation helpful? Give feedback.
All reactions