Skip to content

fix: remove dead HomeTriggerDevBanner import that breaks the lint gate#218

Open
simon-vincent wants to merge 1 commit into
triggerdotdev:mainfrom
simon-vincent:bug/remove-dead-trigger-banner-import
Open

fix: remove dead HomeTriggerDevBanner import that breaks the lint gate#218
simon-vincent wants to merge 1 commit into
triggerdotdev:mainfrom
simon-vincent:bug/remove-dead-trigger-banner-import

Conversation

@simon-vincent

Copy link
Copy Markdown

What

Removes a dangling import in app/routes/index.tsx:

-import { HomeTriggerDevBanner } from "~/components/Home/HomeTriggerDevBanner";

Why

The HomeTriggerDevBanner component no longer exists in the repo (only HomeApiHeroBanner and HomeGithubBanner remain under app/components/Home/). The import was left behind and the symbol is never rendered in the page's JSX, so it is pure dead code.

Because the file is still imported, tsc fails on a clean checkout of main:

app/routes/index.tsx(16,38): error TS2307: Cannot find module '~/components/Home/HomeTriggerDevBanner' or its corresponding type declarations.

This breaks npm run lint — the exact gate that CONTRIBUTING.md asks every contributor to run ("Make sure to run the npm lint command to ensure there are no Typescript compile-time errors"). The esbuild dev/prod bundles tree-shake the unused import, so the app itself is unaffected — only the type-check fails.

Verification

On this branch, all gates pass:

  • npm run lint ✅ (was failing on main)
  • npm test ✅ (20/20)
  • npm run build

No behaviour change — the homepage renders identically.

The HomeTriggerDevBanner component was removed from the repo but its
import in app/routes/index.tsx remained. The symbol is never rendered,
so this is a dangling import that breaks `tsc` (and therefore the
`npm run lint` gate that CONTRIBUTING.md asks every contributor to run)
on a clean checkout of main.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant