Function maybeExecBuildCommand

packages/backends/src/utils.ts:78–119

(
  args: Parameters<BuildV2>[0],
  {
    spawnEnv,
  }: {
    spawnEnv: {
      [x: string]: string | undefined;
    };
  }
)

}

export async function maybeExecBuildCommand(
  args: Parameters<BuildV2>[0],
  {
    spawnEnv,
  }: {
    spawnEnv: {
      [x: string]: string | undefined;
    };
  }
) {
  const projectBuildCommand = args.config.projectSettings?.buildCommand;
  if (projectBuildCommand) {
    // Add node_modules/.bin to PATH so commands like 'cervel' can be found
    const repoRoot = args.repoRootPath || args.workPath;
    const nodeBinPaths = getNodeBinPaths({
      base: repoRoot,
      start: args.workPath,
    });
    const nodeBinPath = nodeBinPaths.join(delimiter);
    const env = {
      ...spawnEnv,
      PATH: `${nodeBinPath}${delimiter}${spawnEnv?.PATH || process.env.PATH}`,
    };

    return execCommand(projectBuildCommand, {
      env,
      cwd: args.workPath,
    });
  }

  // I don't think we actually want to support vercel-build or now-build because those are hacks for controlling api folder builds
  const possibleScripts = ['build'];

  // Run from the app root (workPath), not dirname(entrypoint), so `turbo build` /
  // monorepo scripts match what users run locally and align with explicit buildCommand.
  return runPackageJsonScript(
    args.workPath,
    possibleScripts,
    { env: spawnEnv },
    args.config.projectSettings?.createdAt
  );
}