You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am following the Training Wheels guide. After I've linked Vercel with Github and imported the project, Vercel is unable to deploy my league page. I get the following error:
BUILD_UTILS_SPAWN_1: Command "npm run build" exited with 1
I've tried to deploy via a PC running Windows 10 and an iPad running iOS 15.5 with the same results.
Your League ID
931316844051456000
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected Vercel to deploy the project
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows 10
Browser Firefox
Version 102.7.0esr
Smartphone (please complete the following information):
Device: iPad Air 4th Gen
OS: iOS 15.5
Browser: Chrome
Version: 111.0.5563.101
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I just made an update that I think should fix your issue. Try following the update instructions and see if that resolves the error. If not, re-open and I'll keep investigating.
Describe the bug
I am following the Training Wheels guide. After I've linked Vercel with Github and imported the project, Vercel is unable to deploy my league page. I get the following error:
BUILD_UTILS_SPAWN_1: Command "npm run build" exited with 1
I've tried to deploy via a PC running Windows 10 and an iPad running iOS 15.5 with the same results.
Your League ID
931316844051456000
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected Vercel to deploy the project
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: