Build Fails Without Workflow Configuration
During the Turbo build process, multiple applications (like next-app, adonis, and vite-project) were failing to build. The issue occurred because there was no automated CI workflow (build.yml) to ensure each project builds correctly in an isolated environment.
Observed Error:
next-app:build: ERROR: command finished with error: command exited (1) adonis:build: ELIFECYCLE Command failed with exit code 1. vite-project:build: ELIFECYCLE Command failed with exit code 1.
Do you wanna work on this @amankamlesh ?
Yeah, I have started working on it. Can you please come on discord and check thread which I have started
@amankamlesh Do you have any screenshots or links to these failing builds? I can't reproduce this issue. Often times, the builds fail when someone has made breaking changes in the code or hasn't properly set up the repository. In such cases, the build should fail.
@The-Best-Codes actually build is running fine but problem is if error occurs then we can't identify where it occurred,for that i have created new workflow (https://github.com/amankamlesh/lingo.dev/blob/main/.github/workflows/build.yml)
@amankamlesh What does that workflow do that the PR Tests workflow doesn't already do? You can already view the specific errors on failure by looking at the workflow run in a PR!
@The-Best-Codes sir, the thing is it parallely runs react build, sdk build and cli build execution so that you can specifically find where error is occuring and in which file, though currently my workflow is not passing every test in github action but you can see that it will definitely help (https://github.com/amankamlesh/lingo.dev/actions/runs/19060178590) <- please see this
@amankamlesh Okay but Lingo.dev is already using Turborepo for builds... what does this do which Turbo does not do?
@amankamlesh please provide a reproduction scenario, step by step.
My guess so far is that you don't have Lingo.dev API key configured in your local environment and that's why it fails to build those demo apps.