Fix a failed build on seenode | Seenode Docs
seenode™
Deploy
Fix a failed build on seenode

Fix a failed build on seenode

Common causes of a failed seenode build (missing requirements.txt, package.json, or Go module) and how to fix them.

The error

Your deployment stops during the build stage. The Logs tab (Build) shows an error such as:

  • Could not open requirements file: requirements.txt
  • npm error enoent Could not read package.json
  • go: cannot find main module
  • no such file or directory: ./app

Quick fix

The build command couldn’t find or produce what it expected. Check, in order:

  1. The dependency manifest is committed: requirements.txt (Python), package.json (Node.js), or go.mod (Go) must be in the repository, at the root directory you configured.
  2. The build command matches your project: for example pip install -r requirements.txt, npm ci, or go build -o app.
  3. The start command points at the build output: if you build a binary with go build -o app, the start command is ./app; if the binary name or path differs, update the start command.
  4. The root directory is correct: for a monorepo, set the service’s Root directory to the subfolder that contains the manifest. See Deploy from a monorepo.

Why this happens

seenode runs your build command from the configured root directory, then your start command. If a manifest is missing, in a different folder, or the build produced a file the start command doesn’t reference, the deploy fails.

Checklist

  • The manifest file is committed and in the root directory you set.
  • Build and start commands match your project layout.
  • The build succeeds locally with the same commands.