Errors during Vercel deployment

I am trying to deploy my app but it’s getting errors. It works fine when I build it locally, but errors when deploying on vercel. (don’t mind the warnings)

[11:54:49.344] Running build in Washington, D.C., USA (East) – iad1
[11:54:49.485] Cloning github.com/Yuvraj3102/bundlink (Branch: master, Commit: d53dffa)
[11:54:49.497] Skipping build cache, deployment was triggered without cache.
[11:54:49.947] Cloning completed: 463.447ms
[11:54:50.262] Running "vercel build"
[11:54:50.689] Vercel CLI 39.2.0
[11:54:51.093] Installing dependencies...
[11:54:55.447] npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
[11:54:55.448] npm warn deprecated
[11:54:55.448] npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
[11:54:55.595] npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
[11:54:56.081] npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[11:54:56.504] npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
[11:54:57.041] npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
[11:54:57.111] npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
[11:55:00.366] npm warn deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
[11:55:09.968] 
[11:55:09.969] added 587 packages in 19s
[11:55:09.969] 
[11:55:09.969] 152 packages are looking for funding
[11:55:09.970]   run `npm fund` for details
[11:55:09.998] Detected Next.js version: 14.2.22
[11:55:10.005] Running "npm run build"
[11:55:10.141] 
[11:55:10.141] > part@0.1.0 build
[11:55:10.142] > NEXT_TELEMETRY_DISABLED=1 next build
[11:55:10.142] 
[11:55:10.851]   ▲ Next.js 14.2.22
[11:55:10.852] 
[11:55:10.865]    Creating an optimized production build ...
[11:55:13.464] (node:226) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[11:55:13.464] (Use `node --trace-deprecation ...` to show where the warning was created)
[11:55:30.690] (node:318) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[11:55:30.691] (Use `node --trace-deprecation ...` to show where the warning was created)
[11:55:37.278]  ✓ Compiled successfully
[11:55:37.279]    Linting and checking validity of types ...
[11:55:42.118] 
[11:55:42.119] ./app/components/HeroSection.tsx
[11:55:42.119] 20:13  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
[11:55:42.120] 26:13  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
[11:55:42.120] 32:13  Warning: Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element  @next/next/no-img-element
[11:55:42.120] 
[11:55:42.120] info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
[11:55:45.745]    Collecting page data ...
[11:55:46.315] (node:417) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
[11:55:46.315] (Use `node --trace-deprecation ...` to show where the warning was created)
[11:55:53.417] Error: 2 UNKNOWN: Getting metadata from plugin failed with error: error:1E08010C:DECODER routines::unsupported
[11:55:53.417]     at callErrorFromStatus (/vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
[11:55:53.417]     at Object.onReceiveStatus (/vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/client.js:359:73)
[11:55:53.417]     at Object.onReceiveStatus (/vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
[11:55:53.417]     at /vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/resolving-call.js:129:78
[11:55:53.418]     at process.processTicksAndRejections (node:internal/process/task_queues:85:11)
[11:55:53.418] for call at
[11:55:53.418]     at ServiceClientImpl.makeServerStreamRequest (/vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/client.js:342:32)
[11:55:53.418]     at ServiceClientImpl.<anonymous> (/vercel/path0/node_modules/google-gax/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
[11:55:53.418]     at /vercel/path0/node_modules/@google-cloud/firestore/build/src/v1/firestore_client.js:237:29
[11:55:53.418]     at /vercel/path0/node_modules/google-gax/build/src/streamingCalls/streamingApiCaller.js:38:28
[11:55:53.418]     at /vercel/path0/node_modules/google-gax/build/src/normalCalls/timeout.js:44:16
[11:55:53.418]     at Object.request (/vercel/path0/node_modules/google-gax/build/src/streamingCalls/streaming.js:376:40)
[11:55:53.418]     at Timeout.makeRequest [as _onTimeout] (/vercel/path0/node_modules/retry-request/index.js:159:28)
[11:55:53.418]     at listOnTimeout (node:internal/timers:594:17)
[11:55:53.418]     at process.processTimers (node:internal/timers:529:7)
[11:55:53.418] Caused by: Error
[11:55:53.418]     at QueryUtil._getResponse (/vercel/path0/node_modules/@google-cloud/firestore/build/src/reference/query-util.js:44:23)
[11:55:53.418]     at CollectionReference._getResponse (/vercel/path0/node_modules/@google-cloud/firestore/build/src/reference/query.js:784:32)
[11:55:53.418]     at CollectionReference._get (/vercel/path0/node_modules/@google-cloud/firestore/build/src/reference/query.js:777:35)
[11:55:53.418]     at /vercel/path0/node_modules/@google-cloud/firestore/build/src/reference/query.js:745:43
[11:55:53.418]     at /vercel/path0/node_modules/@google-cloud/firestore/build/src/telemetry/enabled-trace-util.js:110:30
[11:55:53.418]     at NoopContextManager.with (/vercel/path0/node_modules/@opentelemetry/api/build/src/context/NoopContextManager.js:25:19)
[11:55:53.418]     at ContextAPI.with (/vercel/path0/node_modules/@opentelemetry/api/build/src/api/context.js:60:46)
[11:55:53.418]     at NoopTracer.startActiveSpan (/vercel/path0/node_modules/@opentelemetry/api/build/src/trace/NoopTracer.js:65:31)
[11:55:53.418]     at ProxyTracer.startActiveSpan (/vercel/path0/node_modules/@opentelemetry/api/build/src/trace/ProxyTracer.js:36:24)
[11:55:53.418]     at EnabledTraceUtil.startActiveSpan (/vercel/path0/node_modules/@google-cloud/firestore/build/src/telemetry/enabled-trace-util.js:102:28) {
[11:55:53.418]   code: 2,
[11:55:53.418]   details: 'Getting metadata from plugin failed with error: error:1E08010C:DECODER routines::unsupported',
[11:55:53.418]   metadata: Metadata { internalRepr: Map(0) {}, options: {} }
[11:55:53.418] }
[11:55:53.425] 
[11:55:53.425] > Build error occurred
[11:55:53.425] Error: Failed to collect page data for /[username]/[key]
[11:55:53.425]     at /vercel/path0/node_modules/next/dist/build/utils.js:1269:15
[11:55:53.425]     at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
[11:55:53.425]   type: 'Error'
[11:55:53.425] }
[11:55:53.451] Error: Command "npm run build" exited with 1
[11:55:53.888] 

Please help me.

It sounds like your app isn’t compatible with latest version of Node. You can try switching to Node 16 or 18 and see if it helps. The best step to move forward would be updating your outdated dependencies.

2 Likes

Thanks for replying. And let me try that

1 Like

still same errors, even chatgpt isn’t giving proper solutions

What is the repo link ? Did you update all dependencies to latest one?

I made a new nextjs app, copied all the code and now when deploying I just get this error:

[Error: 2 UNKNOWN: Getting metadata from plugin failed with error: error:1E08010C:DECODER routines::unsupported] {
  code: 2,
  details: 'Getting metadata from plugin failed with error: error:1E08010C:DECODER routines::unsupported',
  metadata: [Metadata]

it got solved, by the way thanks for replying.

1 Like

Curious what was the solution

2 Likes

Hi @yuvduderat3102-gmail, glad to see you got it solved.

Could you share the solution here so other community members can benefit from it in future?

I got rid of the starting and ending double quotes for the Firebase_admin_private_key and also remove the code for replacing the \n. And it worked.

2 Likes

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