Succesful Bun Run Deploy in Console, deployment fails in Dashboard
Account id: 2681f1ed7639ad2477706a492ad7d1c5
projecturl: nextproject.pages.dev
Console says it sucesfully compiles with
but I just see deployment failed in the dashboard, I have no idea where to find the logs or errors for it.
https://prnt.sc/sqntOfmHQx2Q
https://prnt.sc/sqntOfmHQx2Q
8 Replies
There's a known issue right now where deploying via CLI will not show you functions failures, where Git Integration will.
CF Employees can pull the logs for you, I'd check first if you're over 1 MiB total script size if on free or have any other obvious script issues, new depends, etc
ah okay yes it's definitely over 1MiB i can't tell what it's coming form though just the generic dist__/webpack/id.js
you say git integration will, do you mean it will for me or for CF employees only?
If you were using the Git Integration, either Github or Gitlab, which uses Pages CI/CD to do the builds, you'd get full errors and it'd tell you of the exact issue. It's just wrangler direct upload which has that issue of not telling you why it failed.
but I mean all it'd say is "Functions over limit", it wouldn't tell you why it bundled such a big function. Prob a dependency though
ahh okay i just created a new pages app with the git integration and i get this now: ⚡️ Detected Package Manager: bun (1.0.1)
13:29:34.427 ⚡️ Preparing project...
13:29:34.475 ⚡️ Project is ready
13:29:34.475 ⚡️ Building project...
13:29:34.928 ▲ Vercel CLI 33.6.1
13:29:35.167 ▲ Error: Importing "@vercel/next": require() of ES Module /opt/buildhome/repo/node_modules/string-width/index.js from /opt/buildhome/repo/node_modules/wide-align/align.js not supported.
13:29:35.167 ▲ Instead change the require of index.js in /opt/buildhome/repo/node_modules/wide-align/align.js to a dynamic import() which is available in all CommonJS modules.
13:29:35.254 ▲ error: "vercel" exited with code 1 (SIGHUP)
13:29:35.259
13:29:35.259 ⚡️ The Vercel build (
13:29:35.259 ⚡️ The Vercel build (
bunx vercel build) command failed. For more details see the Vercel logs above.
13:29:35.259 ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
ugh seems to be a bun compatibility issue i'm guessing
Fixed that error by adding: {
"name": "@package/name",
"resolutions": { "string-width": "4.2.3" }
...
}
@Chaika thank you for your help, using the log errors provided by the Git integration i was able to solve all the dependency issues, thanks again!no problem! Yea hopefully they fix that direct upload issue in the future. Employees can pull logs for you, if you really needed it, and we can escalate those issues, but I try not to/try solving them directly first
i was too presumptious function size over 1 MiB 😭 still thank you for your help at least i can see errors now. I assume a CF employees is the only one able to determine which function(s) are too large?
They all get bundled into one function
so it's the total size
not like each path has a different limit or anything
ah okay, so i ran @next/bundle-analyzer, it gives client, edge and node. Which one do I need to trim for this error? only the edge or does that also mean node?
Seems the issue is react-email components.