oracle-gaps: a Vitest that won't resolve for the generated wrapper is blamed on the user's config

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

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

  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.