Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

chore: @opencode-ai/core typecheck is red at HEAD (pre-existing, unrelated to v0.9.7)

Open
#1,144 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript

Research direction

Start by running bun turbo typecheck and inspect the reported failures in packages/core/test/tool-write.test.ts, test/util/effect-flock.test.ts, test/util/flock.test.ts, and test/util/which.test.ts. Check the repository's Bun and TypeScript type configuration for the missing bun:test types and ImportMeta.dir typing. Done means the full monorepo typecheck passes, not only scoped package checks.

Written by the indexing model from the issue text.

Description

Found during v0.9.7 release review (Tech Lead persona) while verifying typecheck cleanliness.

bun turbo typecheck fails on @opencode-ai/core:typecheck — errors in test/tool-write.test.ts, test/util/effect-flock.test.ts, test/util/flock.test.ts, test/util/which.test.ts (missing bun:test types, ImportMeta.dir not recognized on the type).

Confirmed via git diff v0.9.6..HEAD --stat -- packages/core/ that v0.9.7's changes to that package are limited to flag.ts, ripgrep.ts, ripgrep.test.ts — none of the failing files were touched by this release. This pre-dates v0.9.6 and does not block the v0.9.7 release, but individual commit messages in this release claim 'typecheck clean' based on scoped/partial runs, not the full turbo task — worth fixing so that claim is accurate again monorepo-wide.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 2h
Merged PRs (30d)
67

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.