I have literally no clue how to fix this

The preview for my application was working perfectly fine right up until I added angular fire to the project and suddenly I get the following below

[17:13:34.315] Running build in Washington, D.C., USA (East) – iad1
[17:13:34.417] Cloning gitlab.com/rare-learning/registration (Branch: Admin, Commit: f735ee5)
[17:13:34.425] Skipping build cache, deployment was triggered without cache.
[17:13:35.323] Cloning completed: 904.912ms
[17:13:35.654] Running “vercel build”
[17:13:36.086] Vercel CLI 37.5.4
[17:13:36.763] Installing dependencies…
[17:14:43.696] 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.
[17:14:44.052] npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
[17:14:44.089] npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
[17:14:56.711]
[17:14:56.712] added 1126 packages in 1m
[17:14:56.713]
[17:14:56.713] 144 packages are looking for funding
[17:14:56.713] run npm fund for details
[17:14:56.747] Running “npm run build”
[17:14:56.988]
[17:14:56.988] > frontend@0.0.0 build
[17:14:56.988] > npm install --legacy-peer-deps && vercel build
[17:14:56.989]
[17:14:59.036]
[17:14:59.036] added 1 package, and audited 1128 packages in 2s
[17:14:59.036]
[17:14:59.036] 144 packages are looking for funding
[17:14:59.036] run npm fund for details
[17:14:59.054]
[17:14:59.054] 2 moderate severity vulnerabilities
[17:14:59.054]
[17:14:59.055] To address all issues (including breaking changes), run:
[17:14:59.055] npm audit fix --force
[17:14:59.055]
[17:14:59.055] Run npm audit for details.
[17:14:59.070] sh: line 1: vercel: command not found
[17:14:59.079] Error: Command “npm run build” exited with 127
[17:14:59.477]

Current versus Expected behavior

Code, configuration, and steps that reproduce this issue

simply deploying triggers this

Project information

Environment (local, preview, production):Preview
Operating System:Mac
Node/Runtime Version:20.x
Package Manager:Npm
Project Framework:Angular

Hey @ilikeapple10. It looks like install succeeds but the build step fails. I wasn’t able to reproduce the error with a fresh Angular boilerplate project. I tried that just to rule out a general Angular build issue. But my setup might be different from yours.

If you try to redeploy a previous successful build, does that work? I want to make sure there’s not some other bug causing a build issue unrelated to Angular Fire.

1 Like

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