oracle-gaps: support oracles in a package other than the one they own (--source outside --package)

Open
#64 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@KyleAMathews is already working on this.

Since Nov 13, 2026.

  • #70 by @KyleAMathews — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, node.js, vite

Research direction

Start in oracle-gaps/args.mjs near line 251, where --source is required to sit inside --package, and in oracle-gaps/check.mjs around lines 254, 396 and 600, where vite and vitest are resolved from --package. Decide how the package boundary is defined for a separate oracle package, and resolve Vitest from the oracle config directory. Done means a layout with oracles in tests/realtime-oracles importing packages/realtime/src runs the gap check, with keys and paths stable across OSes.

Written by the indexing model from the issue text.

Description

Reported from an adopter's first session (a pnpm 10 workspace, Vitest 4.1, Node 26), at c58b0c2. Not yet reproduced here.

Problem. --source must be inside --package (oracle-gaps/args.mjs:251), and the CLI resolves vite and vitest from --package (oracle-gaps/check.mjs:254, :396, :600). Some workspaces keep their oracles in a separate package. For example, tests/realtime-oracles has its own Vitest 4.1 and imports packages/realtime/src. Neither choice of --package works there:

  • the oracle package doesn't contain the source;
  • the repo root has no Vitest.

Proposal.

  • Add a separate --root, or allow --source outside --package, still within one workspace.
  • Resolve Vitest from the directory of the oracle config.

Constraints. P6 says ownership stops at the package boundary, so define the boundary explicitly for this layout. Keys and paths must stay stable across OSes (see the Windows work in #58).

This issue was written by Isaac.

Dominant language
JavaScript
Stars
5
Forks
1
Avg merge
6h
Merged PRs (30d)
56

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 TanStack/oracles

All issues in TanStack/oracles

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.