oracle-gaps: support oracles in a package other than the one they own (--source outside --package)
Maintainers usually reply within 1 day
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
- Domain
- cli, testing-qa, tooling
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--sourceoutside--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
- 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 TanStack/oracles
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TanStack/oracles#120 · 1 comment ·
Maintainers usually reply within 1 day
-
windows
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TanStack/oracles#118 · 1 comment ·
Maintainers usually reply within 1 day
All issues in TanStack/oracles
Similar issues
-
Edit: Telemante [YT]Openchannels:edit check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
fix
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
idean3885/claude-ops-agent#1083 ·
Maintainers usually reply within 1 day
-
入群码过期Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
aliyun/ai-agent-handbook#29 · 1 comment ·
-
docs documentation need-triage SaaS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/cloudstack#14719 ·
Maintainers usually reply within 1 day