This repository was archived by the owner on Jun 10, 2026. It is now read-only.
chore(config): upgrade eslint, ci, and vscode tasks to match backend template - #3
Merged
Merged
Conversation
added 2 commits
May 29, 2026 11:21
…template The template repo's tooling config had drifted from the backend template's conventions: ESLint only ignored uppercase-named unused vars, the CI pipeline ran a single job serially, and the VS Code task runner had no way to mirror CI locally. This brings the three config files in sync — stricter unused-var coverage including caught errors and underscore-prefixed args, four parallel CI jobs (test, lint, format-check, build) with Supabase placeholder env vars for the build step, and a new CI: Verify All compound task in the task runner that runs all four jobs in parallel locally.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades ESLint rules, CI pipeline, and VS Code task runner to match
the conventions established in the backend template, then cleans up
all lint and format errors the stricter config surfaced.
What Changed
eslint.config.js— stricterno-unused-vars(args, caught errors);react-refreshandreact-hooksoverrides for providers and effects.github/workflows/ci.yml— single serial job → four parallel jobs(test, lint, format-check, build); Supabase placeholder env vars added
to the build step
.vscode/tasks.json— addedFormat: Checktask andCI: Verify Allcompound task that mirrors all four CI jobs locally
Screenshots / Demo
What
This PR brings the template repo's tooling config into parity with
the backend template across ESLint, GitHub Actions CI, and VS Code tasks.
Why
The frontend template had drifted from the backend template's conventions,
making it harder to apply the same workflow habits across both repos —
particularly around catching more categories of unused variables and
being able to verify CI locally before pushing.
How
no-unused-varswas extended withargsIgnorePattern,caughtErrors: 'all', andcaughtErrorsIgnorePatternto matchthe backend template's stricter stance without requiring changes
to existing code patterns
so failures are isolated and pipelines run faster
VITE_SUPABASE_*placeholder env vars soVite doesn't fail when
import.meta.envreferences are presentbut no
.envfile exists in CI@supabase/supabase-jswas added topackage.jsondependenciesin anticipation of Supabase integration
npm run lint:fixandnpm run formatwere run to clean up all errors surfaced by the stricter rules
Testing
npm run test:run— all tests passnpm run lint— no errorsnpm run format:check— no errorsnpm run build— succeeds with placeholder Supabase env vars set✅ CI: Verify Allrunsall four jobs in parallel
Pre-Merge Checklist
mainbefore opening this PR (git fetch origin && git merge origin/main)npm test)console.logleft in production codenpm run lint)