Build seems to finnish, deployment never starts. Build logs give no error. Project used to deploy with no issues

mgoeloe · September 19, 2024, 5:18pm

[18:47:52.503] Running build in Washington, D.C., USA (East) – iad1
[18:47:52.591] Cloning ######
[18:47:53.151] Cloning completed: 560.021ms
[18:47:55.864] Restored build cache from previous deployment (######)
[18:47:55.916] Running “vercel build”
[18:47:56.630] Vercel CLI 37.4.2
[18:47:57.311] Running “install” command: yarn install…
[18:47:57.611] yarn install v1.22.19
[18:47:57.721] [1/4] Resolving packages…
[18:48:01.746] [2/4] Fetching packages…
[18:48:27.416] warning vscode-languageclient@7.0.0: The engine “vscode” appears to be invalid.
[18:48:27.437] [3/4] Linking dependencies…
[18:48:27.441] warning “@nuxtjs/robots > @nuxt/devtools-kit@1.4.2” has unmet peer dependency “vite@“.
[18:48:27.442] warning " > @nuxt/devtools@1.4.2” has unmet peer dependency "vite@”.
[18:48:27.443] warning “nuxt > @nuxt/devtools > vite-plugin-inspect@0.8.7” has unmet peer dependency “vite@^3.1.0 || ^4.0.0 || ^5.0.0-0”.
[18:48:27.443] warning “nuxt > @nuxt/devtools > vite-plugin-vue-inspector@5.2.0” has unmet peer dependency “vite@^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0”.
[18:48:27.444] warning “nuxt > @nuxt/devtools > @vue/devtools-core > vite-hot-client@0.2.3” has unmet peer dependency “vite@^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0”.
[18:48:27.447] warning " > vite-plugin-vuetify@2.0.4" has unmet peer dependency “vite@>=5”.
[18:48:36.646] [4/4] Building fresh packages…
[18:48:48.467] success Saved lockfile.
[18:48:48.470] $ nuxt prepare
[18:48:50.305] [info] [nuxt-aos] Setting up nuxt-aos
[18:48:53.362] [info] Compiled plugins/client.mjs in 917.36ms
[18:48:53.463] [info] Compiled types/plugins.d.ts in 1017.33ms
[18:48:53.463] [info] Compiled plugins/server.mjs in 1017.3ms
[18:48:53.548] [success] Types generated in .nuxt
[18:48:53.583] Done in 55.98s.
[18:48:54.040] [warn] Changing NODE_ENV from testing to production, to avoid unintended behavior.
[18:48:54.045] [log] Nuxt 3.13.2 with Nitro 2.9.7
[18:48:55.379] [info] [nuxt-aos] Setting up nuxt-aos
[18:48:58.164] [info] Building client…
[18:48:58.344] [info] e[36mvite v5.4.6 e[32mbuilding for production…e[36me[39m
[18:48:58.388] [info] transforming…
[18:48:59.104] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:48:59.105]
[18:49:07.950] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:07.950]
[18:49:08.080] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:08.080]
[18:49:08.185] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:08.186]
[18:49:08.401] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:08.401]
[18:49:10.194] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:10.196]
[18:49:10.197] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:10.197]
[18:49:18.336] [info] e[32m✓e[39m 1588 modules transformed.
[18:49:18.819] [info] rendering chunks…
[18:49:19.323] [info] computing gzip size…

…

[18:49:19.395] [warn] e[33m
[18:49:19.395] (!) Some chunks are larger than 500 kB after minification. Consider:
[18:49:19.395] - Using dynamic import() to code-split the application
[18:49:19.395] - Use build.rollupOptions.output.manualChunks to improve chunking: Configuration Options | Rollup
[18:49:19.395] - Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.e[39m
[18:49:19.396] [info] e[32m✓ built in 21.05se[39m
[18:49:19.396] [success] Client built in 21227ms
[18:49:19.396] [info] Building server…
[18:49:19.398] [info] e[36mvite v5.4.6 e[32mbuilding SSR bundle for production…e[36me[39m
[18:49:19.439] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:19.439]
[18:49:19.663] [info] transforming…
[18:49:24.457] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:24.457]
[18:49:27.869] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:27.869]
[18:49:27.874] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:27.874]
[18:49:27.953] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:27.953]
[18:49:27.956] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:27.956]
[18:49:28.014] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:28.015]
[18:49:28.043] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:28.043]
[18:49:29.881] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:29.881]
[18:49:29.884] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:29.884]
[18:49:29.928] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:29.928]
[18:49:29.931] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:29.931]
[18:49:31.483] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:31.483]
[18:49:31.663] DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.
[18:49:31.663]
[18:49:33.147] [info] e[32m✓e[39m 1010 modules transformed.
[18:49:33.554] [info] rendering chunks…

…

[18:49:34.747] [info] e[32m✓ built in 15.35se[39m
[18:49:34.751] [success] Server built in 15356ms
[18:49:34.774] [info] [nitro] Initializing prerenderer
[18:49:51.887] [info] [nitro] Prerendering 5 initial routes with crawler
[18:49:52.317] [log] [nitro] ├─ /api/_content/cache.1726764536197.json (330ms)
[18:49:53.134] [log] [nitro] ├─ / (543ms)
[18:49:53.143] [log] [nitro] ├─ /about (1108ms)
[18:49:53.151] [log] [nitro] ├─ /blogs (992ms)
[18:49:53.203] [log] [nitro] ├─ /_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (51ms) (skipped)
[18:49:53.204] [log] [nitro] ├─ /about/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (21ms) (skipped)
[18:49:53.205] [log] [nitro] ├─ /blogs/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (16ms) (skipped)
[18:49:53.213] [log] [nitro] ├─ /blogs/** (757ms)
[18:49:53.223] [log] [nitro] ├─ /blogs//_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (7ms) (skipped)
[18:49:53.269] [log] [nitro] ├─ /about/_payload.json (19ms)
[18:49:53.269] [log] [nitro] ├─ /_payload.json (25ms)
[18:49:53.270] [log] [nitro] ├─ /blogs/_payload.json (14ms)
[18:49:53.872] [log] [nitro] ├─ /blogs//_payload.json (4ms)
[18:49:53.885] [log] [nitro] ├─ /logout (256ms)
[18:49:53.901] [log] [nitro] ├─ /login (172ms)
[18:49:53.914] [log] [nitro] ├─ /logout/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (26ms) (skipped)
[18:49:53.928] [log] [nitro] ├─ /pricing (356ms)
[18:49:53.936] [log] [nitro] ├─ /workshop (593ms)
[18:49:53.936] [log] [nitro] ├─ /login/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (22ms) (skipped)
[18:49:53.985] [log] [nitro] ├─ /quotation (514ms)
[18:49:53.986] [log] [nitro] ├─ /pricing/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (48ms) (skipped)
[18:49:53.986] [log] [nitro] ├─ /workshop/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (44ms) (skipped)
[18:49:54.087] [log] [nitro] ├─ /quotation/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (18ms) (skipped)
[18:49:54.099] [log] [nitro] ├─ /logout/_payload.json (23ms)
[18:49:54.100] [log] [nitro] ├─ /login/_payload.json (19ms)
[18:49:54.100] [log] [nitro] ├─ /pricing/_payload.json (46ms)
[18:49:54.100] [log] [nitro] ├─ /workshop/_payload.json (42ms)
[18:49:54.111] [log] [nitro] ├─ /admin (834ms)
[18:49:54.111] [log] [nitro] ├─ /quotation/_payload.json (16ms)
[18:49:54.119] [log] [nitro] ├─ /admin/_payload.json?cc57baf2-7523-4658-8d04-8af0a504ba81 (6ms) (skipped)
[18:49:54.119] [log] [nitro] ├─ /admin/payload.json (4ms)
[18:50:10.646] [info] [nitro] Running link inspections…
[18:50:10.646] [info] [nitro] Prerendered 21 routes in 35.822 seconds
[18:50:10.821] [success] [nitro] Generated public .vercel/output/static
[18:50:10.860] [info] [nitro] Building Nuxt Nitro server (preset: vercel)
[18:50:28.612] Export “useNitroApp” of module “node_modules/nitropack/dist/runtime/app.mjs” was reexported through module “node_modules/nitropack/dist/runtime/index.mjs” while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
[18:50:28.613] Either change the import in “node_modules/nuxt-og-image/dist/runtime/nitro/og-image/context.js” to point directly to the exporting module or reconfigure “output.manualChunks” to ensure these modules end up in the same chunk.
[18:50:36.685] [success] [nitro] Nuxt Nitro server built
[18:50:38.270] ├─ .vercel/output/functions/__nitro.func/chunks//empty.mjs (125 B) (134 B gzip)
…
[18:50:38.309] └─ .vercel/output/functions/__nitro.func/package.json (9.04 kB) (2.85 kB gzip)
[18:50:38.309] Σ Total size: 23 MB (8.02 MB gzip)

amyegan · September 19, 2024, 10:39pm

Hey @mgoeloe. Does your project use the Nuxt.js Framework Preset or custom Build and Development Settings?

mgoeloe · September 20, 2024, 8:25am

@amyegan Yes, I do use the Nuxt.js framework preset, with “nuxi build” as build command and “yarn install” as install command. This has worked perfectly before.

amyegan · September 20, 2024, 2:22pm

Thanks for sharing the build settings with me! I tried with a Nuxt boilerplate project using the default Nuxt preset along with the build and install overrides your project uses.

I did get a successful deployment, but I noticed a difference in the build logs.Both your build and mine say Building Nuxt Nitro server (preset: vercel), but they differ in what happens after that.

My minimal example reports Nuxt Nitro server built on the next line and proceeds with the deployment. Then a list of .vercel/output/functions/ functions are printed, Build Completed in /vercel/output and Deployment completed

Successful deployment partial build log

[success] Server built in 855ms
[success] [nitro] Generated public .vercel/output/static
[info] [nitro] Building Nuxt Nitro server (preset: `vercel`)
[success] [nitro] Nuxt Nitro server built
  ├─ .vercel/output/functions/__nitro.func/chunks/_/error-500.mjs (4.77 kB) (2.02 kB gzip)
    ...
  └─ .vercel/output/functions/__nitro.func/package.json (586 B) (290 B gzip)
Σ Total size: 1.77 MB (422 kB gzip)
Build Completed in /vercel/output [11s]
Deploying outputs...

Deployment completed
Uploading build cache [30.72 MB]...
Build cache uploaded: 593.853ms

Your build seems to run into problems with useNitroApp and nuxt-og-image at this point, though it also eventually reports Nuxt Nitro server built.

Skipped deployment partial build log

[18:50:10.821] [success] [nitro] Generated public .vercel/output/static
[18:50:10.860] [info] [nitro] Building Nuxt Nitro server (preset: `vercel`)
[18:50:28.612] Export “useNitroApp” of module “node_modules/nitropack/dist/runtime/app.mjs” was reexported through module “node_modules/nitropack/dist/runtime/index.mjs” while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
[18:50:28.613] Either change the import in “node_modules/nuxt-og-image/dist/runtime/nitro/og-image/context.js” to point directly to the exporting module or reconfigure “output.manualChunks” to ensure these modules end up in the same chunk.
[18:50:36.685] [success] [nitro] Nuxt Nitro server built
[18:50:38.270] ├─ .vercel/output/functions/__nitro.func/chunks/</em> /empty.mjs (125 B) (134 B gzip)
…
[18:50:38.309] └─ .vercel/output/functions/__nitro.func/package.json (9.04 kB) (2.85 kB gzip)
[18:50:38.309] Σ Total size: 23 MB (8.02 MB gzip)

I suspect those warnings/errors are causing the skipped deployment.

mgoeloe · September 21, 2024, 12:10pm

I’m aware of the circular dependency warning within Nitro and Nuxt-og-image, but that doesn’t seem to be the cause of this issue. Removing nuxt-og-image, @nuxtjs/seo (which contains nuxt-og-image) and all related code, removes the warning, but the deployment issue still persists.

amyegan · September 22, 2024, 8:02pm

It could be a configuration difference. I used the very basic Nuxt.js starter, and the only settings I changed were the build and install command overrides.

Is your repo public, or do you have a minimal reproducible example I could use to help investigate the problem?

mgoeloe · September 29, 2024, 12:49pm

Thanks for reaching out, I think this topic can be closed. When building locally I get the same behaviour, so this issue isn’t related to Vercel.

system · October 1, 2024, 12:49pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Build works on "main" but fails on other branch Help nuxt	4	21	December 10, 2024
React app i created using vite has refused to deploy despite it working fine on local host and run build Help	2	19	November 22, 2024
I'm having issues with deployment Help	11	66	January 7, 2025
Build errors with Vercel CLI 39.1.1 Help	3	15	December 25, 2024
404 on deployed site Help	7	131	August 5, 2024

Build seems to finnish, deployment never starts. Build logs give no error. Project used to deploy with no issues

Related topics