Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

injectConfigValues is not a function when passing --no-api + api in config #4222

Closed
6 tasks done
posva opened this issue Oct 3, 2023 · 0 comments · Fixed by #5386
Closed
6 tasks done

injectConfigValues is not a function when passing --no-api + api in config #4222

posva opened this issue Oct 3, 2023 · 0 comments · Fixed by #5386
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)

Comments

@posva
Copy link
Contributor

posva commented Oct 3, 2023

Describe the bug

I found this while upgrading versions. I use --no-api to disable the api when running on CI. This page in the docs currently has an example like this: https://vitest.dev/guide/cli.html#options

Reproduction

https://stackblitz.com/edit/but-report-no-api

System Info

(stackblitz)

Used Package Manager

npm

Validations

@sheremet-va sheremet-va added bug p3-minor-bug An edge case that only affects very specific usage (priority) and removed pending triage labels Oct 3, 2023
@sheremet-va sheremet-va removed the bug label Feb 16, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)
Projects
Archived in project
2 participants