Add a typecheck script and CI step
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, nextjs, typescript
- Domain
- build-system, ci-cd
Research direction
Start in the scripts block of package.json and in the build job of .github/workflows/ci.yml, which the issue names. Add a typecheck script that runs tsc --noEmit, then run npm run typecheck locally to see whether the repository currently compiles cleanly. Done means the script runs locally and a CI step runs it before the tests. If the check reports existing errors, the CI step will fail, so confirm with a maintainer how to handle them.
Written by the indexing model from the issue text.
Description
Description
Type errors are only caught by next build, late in CI. During the last contribution wave 345 type errors were merged unnoticed.
Location
package.json scripts; .github/workflows/ci.yml.
Task
Add "typecheck": "tsc --noEmit" and run it in the CI build job before tests.
Acceptance criteria
-
npm run typecheckworks - CI runs it
Good for contributors because
Small, high-value CI improvement.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 144
- Avg merge
- 13h 50m
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FlowwStar/FlowStar
-
Add a Storybook section to CONTRIBUTING.mdPossibly taken @ChanakyaG2004 claimed this today. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#995 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation good first issue testing
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
FlowwStar/FlowStar#994 · 2 comments ·
Maintainers usually reply within 1 day
-
Document how Playwright visual baselines are generatedPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
devops documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
FlowwStar/FlowStar#991 · 2 comments ·
Maintainers usually reply within 1 day
-
frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
juice-shop/juice-shop#3686 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dsh-market/dsh-market#877 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ScottKirvan/GOMAC#61 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stellar/stellar-dev-skill#151 ·
Maintainers usually reply within 1 day