oracle-gaps: a Vitest that won't resolve for the generated wrapper is blamed on the user's config
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- testing-qa
Research direction
The wrong blame comes from check.mjs around lines 557-562, where the user's Vitest config name is printed in place of the generated wrapper path (<pkg>/.oracle-gaps-<pid>/vitest-N.config.mts). Start by reading that refusal and the wrapper's vitest/config import, then reproduce by running the gap check with --package where vitest does not resolve. Done means the refusal names the wrapper and says vitest >= 4.1 must resolve from --package, with a constructed history case added to the gap report oracle's tests.
Written by the indexing model from the issue text.
Description
Reported from an adopter's first session, at c58b0c2. Not yet reproduced here.
Problem. The generated wrapper (<pkg>/.oracle-gaps-<pid>/vitest-N.config.mts) imports mergeConfig from vitest/config. When vitest doesn't resolve from --package, the refusal blames the user's config: "the package's Vitest config (tests/realtime-oracles/vitest.config.ts) failed to load: Cannot find package 'vitest'". Its fix line says "Make load under Vitest", but the user's config was fine. The cause is check.mjs:557-562, which puts the user's config name in place of the wrapper's path.
Proposal. When the missing package is vitest or vite, the refusal should name the wrapper and say "vitest >= 4.1 must resolve from --package". Add a constructed history for this refusal to the gap report oracle.
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