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

test: type-check Drive test sources

Open
  • Is something wrong?
#97 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
build-system, testing, tooling

Research direction

Start with packages/drive/tsconfig.json and the existing scripts, then inspect the reported errors in test/driver/index.test.ts, test/tool/producer.test.ts, test/instance/proxy.test.ts, test/tool/controller.test.ts, and test/fixtures/**. Add the diagnostic test configuration and script, resolve the file-scoped type errors, and confirm production and test checks pass without changing runtime assertions.

Written by the indexing model from the issue text.

Description

enhancement

Problem

packages/drive/tsconfig.json checks src, examples, compile fixtures, and manual probes, but excludes ordinary test/**/*.test.ts and test/fixtures/**. Vitest strips types, so test API drift can stay invisible until a line happens to fail at runtime.

A diagnostic config including the full test tree currently reports roughly 50 errors. Examples include stale Effect APIs, unchecked indexed access, scope requirements, overly broad error unions, and fixture contract drift.

Proposed sequence

  1. Add tsconfig.test.json and a typecheck:test script, but keep it out of required CI initially.
  2. Fix errors in small file-scoped commits, starting with:
    • test/driver/index.test.ts
    • test/tool/producer.test.ts
    • test/instance/proxy.test.ts
    • test/tool/controller.test.ts
    • test/fixtures/**
  3. Add typecheck:test to check once the diagnostic config is clean.

Done when

  • Production and test TypeScript checks both pass.
  • Script fixtures are covered, since start --script compiles them as user programs.
  • Runtime test behavior and assertions remain unchanged.
Dominant language
TypeScript
Stars
32
Forks
4
Avg merge
11m
Merged PRs (30d)
14

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 anomalyco/opencode-drive

All issues in anomalyco/opencode-drive

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.