#@payloadcms/next-payload fails on vercel
simple coyote
junior vesselBOT
half cradle
Same issue:
zenith lichen
outputFileTracingExcludes: {
'*': [
'node_modules/@swc/core-linux-x64-gnu',
'node_modules/@swc/core-linux-x64-musl',
],
},
},
This worked for me, you'll need to replace those modules with your paths.
simple coyote
I added this but it looks like it doesn' seem to work for me,
outputFileTracingExcludes: {
"*": [
"node_modules/.pnpm/@[email protected]",
"node_modules/.pnpm/@[email protected]",
],
},
I give up, at this point I've encountered too many issues to continue using this cms. Probably just going to migrate to something better
zenith lichen
I was using it with workspaces, and I had to add that setting to both the my frontend next.config.js as well as my cms next.config.js.
This is the github thread from vercel that I was working from - https://github.com/vercel/next.js/issues/42641
You might want to have a quick run through that thread, this person https://github.com/vercel/next.js/issues/42641#issuecomment-1488845116 is using pnpm like you and had to use ** but seems to be a difficult issue to fix and track down.
half cradle
Still doesn't work for me. I use pnpm and turborepo and tried all of these with no success. experimental: { outputFileTracingExcludes: { "*": [ "./**/node_modules/@swc/core-linux-x64-gnu", "./**/node_modules/@swc/core-linux-x64-musl", "./**/node_modules/@swc/core", "./**/node_modules/esbuild/linux", "./**/node_modules/webpack", "./**/node_modules/rollup", "./**/node_modules/terser", "../../**/node_modules/@swc/core-linux-x64-gnu", "../../**/node_modules/@swc/core-linux-x64-musl", "../../**/node_modules/@swc/core", "../../**/node_modules/esbuild/linux", "../../**/node_modules/webpack", "../../**/node_modules/rollup", "../../**/node_modules/terser", "../../**/node_modules/@swc/core/**/*", "./**/node_modules/@swc/core/**/*", ], }, }, outputFileTracing: true,
Noone else seems to have 'node_modules/@swc/core' as a large dependency except for me. Now I am just lost.
ionic temple
I added this but it looks like it doesn' seem to work for me,
```
outputFile...
I'd love to talk through what issues you ran into and see if we can get you on a productive path.
simple coyote
Sean appreciate it mate but I think I just don't have the bandwidth to go through each of them and fix it. I spent almost whole of last week working through and around gotchas with payload, most important issue for me was that payload cloud didn't work and elliot said that there's no better way to fix it right now 😦
Anyways, I've mentioned few of those issues here and some on github. I can probably give better feedback later but I've to ship something this week haha
ionic temple
Sean appreciate it mate but I think I just don't have the bandwidth to go throug...
Completely understand that. If you do have some bandwidth after your project, I would love to walk through everything you ran into in an effort to streamline the process in the future. Best of luck with your current project!
zenith lichen
@half cradle https://nextjs.org/docs/pages/api-reference/next-config-js/output#caveats - without knowing how your turborepo is setup, you might also need to include the outputFileTracingRoot ?
half cradle
Nope still doesn't work. I've created ~30 vercel builds trying different things. outputFileTracingExcludes: { "*": [ "./**/node_modules/@swc/core-linux-x64-gnu", "./**/node_modules/@swc/core-linux-x64-musl", "./**/node_modules/esbuild/linux", "./**/node_modules/webpack", "./**/node_modules/rollup", "./**/node_modules/terser", "**swc/core**", ], }, outputFileTracingRoot: path.join(__dirname, "../../"), Heres my current config and image of dependencies. Got my dependencies to look like this as I stopped hoisting my node_modules (necessary for expo).
half cradle
Idk what else to do