Add build:vercel script to package.json

[swimming987]

No description provided.

[vercel]

@swimming987 is attempting to deploy a commit to the umami-software Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

• Adds a new build:vercel script to package.json that runs only essential build steps (build-tracker and build-app) for Vercel deployment
• Streamlines the build process by omitting environment checks, database operations, and geo data generation that may not be compatible with Vercel's platform
• Creates a deployment-specific build variant that focuses on core application assets needed for the web analytics functionality

Important Files Changed

Filename	Overview
package.json	Added new build:vercel script that executes simplified build pipeline for Vercel deployment compatibility

Confidence score: 4/5

• This PR is safe to merge with minimal risk as it only adds a new npm script without modifying existing functionality
• Score reflects the straightforward nature of adding a deployment-specific script that doesn't impact current build processes
• No files require special attention as this is a simple script addition without complex logic changes

Sequence Diagram

sequenceDiagram
    participant User
    participant NPM as "npm run build:vercel"
    participant Rollup as "rollup.tracker.config.js"
    participant Tracker as "src/tracker/index.js"
    participant Next as "Next.js Build"
    participant Output as "Build Output"

    User->>NPM: "Execute build:vercel"
    NPM->>Rollup: "Run build-tracker"
    Rollup->>Tracker: "Bundle tracker script"
    Tracker->>Rollup: "Return processed JS"
    Rollup->>Output: "Generate public/script.js"
    NPM->>Next: "Run build-app"
    Next->>Output: "Generate .next/standalone"
    Next->>Output: "Generate static assets"
    Output->>User: "Vercel-ready build complete"

Loading

[greptile-apps]

Greptile found no issues!

From now on, if a review finishes and we haven't found any issues, we will not post anything, but you can confirm that we reviewed your changes in the status check section.

_{This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR".}

[mikecao]

We deploy to Vercel so those steps are required. Also, If you don't run check-db then migrations would never run.