Troubleshooting build command issues
You may run into an error during your build process that prevents the deployment from continuing. Please see some information below about common errors that you might come across:
- 404 not found during NPM build
- Build completes locally but shows an error in DeployHQ
- Built assets not uploading to server
- Cannot find package.json file
- Command not found
- JavaScript heap out of memory on Build Pipeline
- Using PNPM in the Build Pipeline
- Using Bun in the Build Pipeline
- Using Webpack in the Build Pipeline
- Using Pip in the Build Pipeline (Python)
- Dependency or package not found
- Grunt not found
- Installing Ruby and Sass
- Using Yarn 4 in the Build Pipeline
- No gulpfile found
- Node Sass does not yet support your current environment
- Cannot install SASS globally
- Unable to connect to third party services during a build
- Input required during a Build or SSH command
- Running Maven, a popular build tool for Java
- Using the latest composer version in the Build Pipeline
- Use a specific version of Gulp in the Build Pipeline
- Running Out of Memory with Composer During Deployments?
- Using Flutter in the Build Pipeline