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
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Describe the bug
I am running my app through a CI/CD pipeline and I'm expecting it to build as normal, but it can't find vite.
I am using Google Cloud Build and I install all packages including dev in a step prior.
Reproduction
N/A
System Info
Used Package Manager
yarn
Logs
Step #4: Already have image: node:16
Step #4: yarn run v1.19.0
Step #4: $ turbo run build --filter=@vidstep/vidstep-web-app
Step #4: • Packages in scope: @vidstep/vidstep-web-app
Step #4: • Running build in 1 packages
ep #4: @vidstep/vidstep-web-app:build: cache miss, executing 686fe4e4713c805c
Step #4: @vidstep/vidstep-web-app:build: $ tsc && vite build
Step #4: @vidstep/vidstep-web-app:build: /bin/sh: 1: vite: not found
Step #4: @vidstep/vidstep-web-app:build: error Command failed with exit code 127.
Step #4: @vidstep/vidstep-web-app:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Step #4:
Step #4: Tasks: 0 successful, 1 total
Step #4: Cached: 0 cached, 1 total
Step #4: Time: 33.034s
Step #4:
Step #4: @vidstep/vidstep-web-app:build: ERROR: command finished with error: command (/workspace/apps/web) yarn run build exited (127)
Step #4: command (/workspace/apps/web) yarn run build exited (127)
Step #4: ERROR run failed: command exited (127)
Step #4: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Step #4: error Command failed with exit code 127.
Finished Step #4
ERROR
ERROR: build step 4 "node:16" failed: step exited with non-zero status: 127
Validations
The text was updated successfully, but these errors were encountered: