Build failure notification noise from lint errors in Glitch project alerts

Glitch does not provide native, severity-based filtering for build notifications. The project settings offer only an all-or-nothing toggle for alerts, and there are no built-in per-file or per-module suppression rules regardless of the subscription tier.

Why Lint Errors Trigger Alerts

Glitch triggers a build failure notification based on the exit code of the build process. If your linting tool (such as ESLint) is configured to return a non-zero exit code upon finding errors or warnings, Glitch interprets this as a total build failure. Because the platform does not parse the internal logs to distinguish between a syntax error and a linting warning, any process that fails the build triggers the alert.

Resolution: Decoupling Linting from Build Status

To stop lint errors from triggering notifications while still retaining alerts for genuine deployment failures, you must ensure the linting process does not return a non-zero exit code to the Glitch environment. Use one of the following methods in your package.json or build script:

• Force a Zero Exit Code: Append || true to your lint command. This ensures the build continues and is marked as successful even if the linter finds issues.

  "lint": "eslint . || true"

• Use Linter-Specific Flags: Configure your linter to treat errors as warnings or to ignore warnings entirely so they do not trigger a failure state. For example, using --quiet in ESLint suppresses warnings.

  "lint": "eslint . --quiet"

Handling Webhook Filtering

Glitch webhooks send raw event data regarding the build status. They do not provide a mechanism to filter by error severity within the Glitch dashboard. To achieve granular control via webhooks, you must implement the filtering logic on your receiving server. The receiving application should parse the payload and the associated build logs to determine if the failure was caused by a linter or a critical system error before sending a notification to your team.

Verification Step

To confirm the cause of the noise, check your package.json scripts. If your build command is npm run build and that script sequentially calls a linting command that fails, the entire build is marked as failed. Try running the lint command locally; if it returns a non-zero exit code, it will trigger a Glitch alert.

Diagnostic Detail Needed: Are you using a custom build script in package.json, or are you relying on Glitch's default environment detection?