Jake Leventhal

Having this issue as well

@smaeda-ks this isn't really a true solution to the problem though. If you are in a monorepo, this implies you can only have a single project linked at a time....

> @jamiter my very hacky and ugly workaround is to run a second "normal" next.js build with standalone output then moving the node_modules folder the correct places. I can confirm...

https://github.com/vercel/next.js/discussions/39432#discussioncomment-6080594 Check this out. Turbo is unrelated

@dlehmhus I made a Vercel support request with this issue, referencing the provided example, and here is the response I got: > Hi, > > https://github.com/dlehmhus/vercel-deploy-prebuilt-monorepo-example > This repro is...

I opened a broader discussion for context: https://github.com/orgs/vercel/discussions/2845

This issue is resolved for me after talking with @TooTallNate Fix for me was the following: 1. Update vercel to `30.2.2` 2. Set each client application rootDirectory to the real...

Which part(s) specifically? Also make sure you are on the newer versions of the Vercel CLI

Had a similar issue. Adding this to my next config fixed it: ```ts webpack: (config) => ({ ...config, externals: [ ...config.externals, { sharp: 'commonjs sharp' } ] }) ```

Does anyone have a repro of this?