Dear Railway Support Team,

I am experiencing a persistent issue with the deployment of my Node.js backend application on Railway.

Repository Link: https://github.com/KubriakZahoor107/Art-Beckend/
Railway Username: kubriakzahoor107
Contact Email: konstantin.kubriak@gmail.com
Application URL: https://web-production-2730f.up.railway.app

**Problem Description:**

Our application requires copying local 'uploads' files from `server/uploads` to `[repo_root]/.nixpacks/files/uploads` during the build phase. We utilize a custom script, `server/scripts/sync-uploads.mjs`, which is invoked via `nixpacks.toml`. However, despite correct configuration of `nixpacks.toml` at the repository root, the `sync-uploads.mjs` script does not appear to execute, and its expected output is absent from the build logs. Consequently, the target directory (`/app/.nixpacks/files/uploads`) remains empty in the running container, leading to 404 errors when attempting to access uploaded files (e.g., `https://web-production-2730f.up.railway.app/uploads/1733248835049-824543928.jpg`).

**Configuration Details:**

1.  **Repository Structure (relevant parts):**

    ```
    Art-Beckend/
    ├── nixpacks.toml (located at the repository root)
    └── server/
        ├── package.json (defines "build" and "sync:uploads" scripts)
        ├── uploads/ (source directory for files to be copied)
        └── scripts/
            └── sync-uploads.mjs (the custom copying script)
    ```

2.  **`nixpacks.toml` content (at repository root):**

    ```toml
    [phases.install]
    cmds = [
      "npm ci --prefix server"
    ]

    [phases.build]
    cmds = [
      "npm run build --prefix server",
      "npm run sync:uploads --prefix server" # This command appears not to be executed
    ]

    [start]
    cmd = "npm run start:prod --prefix server"
    ```

3.  **Relevant scripts in `server/package.json`:**

    ```json
    {
      "name": "server",
      "scripts": {
        "build": "tsc -p tsconfig.json", // This TypeScript build also seems to be skipped
        "sync:uploads": "node scripts/sync-uploads.mjs",
        "start:prod": "prisma migrate deploy && node dist/index.js"
      }
    }
    ```

**Observed Behavior in Railway Deployment Logs (Example Snippet):**

**Crucially, there is no output in the logs indicating the execution of `npm run build --prefix server` or `npm run sync:uploads --prefix server` during any build phase. The logs directly transition from "Starting Container" to the application's `start:prod` command output.**

**Steps Taken So Far:**

1.  Ensured `nixpacks.toml` is correctly placed at the repository root.
2.  Removed all comments from `nixpacks.toml`.
3.  Updated `server/scripts/sync-uploads.mjs` to include extensive logging (which is not visible in logs).
4.  Committed and pushed all changes to the GitHub repository.
5.  Attempted forced redeployment/rebuilds with cache clearing via the Railway dashboard multiple times.
6.  Verified local Git status is clean and reflects only intended changes.

**Our Hypothesis:**
It appears that Nixpacks on Railway is either not recognizing or not executing the commands defined within the `[phases.build]` section of our `nixpacks.toml`. We expect these commands (including `npm run build` for TypeScript compilation and `npm run sync:uploads`) to run prior to the application's startup.

Could you please investigate why the `build` phase, as specified in our `nixpacks.toml`, is being skipped or not fully processed by Nixpacks during deployment? Any insights or guidance on resolving this would be greatly appreciated.

Thank you for your time and assistance.

Sincerely,

Konstantin Kubriak