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

Support Vitest workspace feature #376

Closed
xeho91 opened this issue Jun 20, 2024 · 0 comments · Fixed by #377
Closed

Support Vitest workspace feature #376

xeho91 opened this issue Jun 20, 2024 · 0 comments · Fixed by #377

Comments

@xeho91
Copy link
Contributor

xeho91 commented Jun 20, 2024

In my repository which uses this action I get the following warning annotation:

Warning

Test / TestFailed to read vite config file at any default location in "./". Make sure you provide the vite-config-path option if you're using a non-default location or name of your config file. Will not include thresholds in the final report.

For the reference - Vitest workspace

I think it can be solved by adding more entries vitest.workspace.(c|m)(j|t)s to default paths:

const defaultPaths = [
"vitest.config.ts",
"vitest.config.mts",
"vitest.config.cts",
"vitest.config.js",
"vitest.config.mjs",
"vitest.config.cjs",
"vite.config.ts",
"vite.config.mts",
"vite.config.cts",
"vite.config.js",
"vite.config.mjs",
"vite.config.cjs",
];

xeho91 added a commit to xeho91/vitest-coverage-report-action that referenced this issue Jun 20, 2024
github-actions bot pushed a commit that referenced this issue Jun 25, 2024
# [2.5.0](v2.4.0...v2.5.0) (2024-06-25)

### Bug Fixes

* **deps:** bump braces from 3.0.2 to 3.0.3 ([#374](#374)) ([1ae9c3f](1ae9c3f))

### Features

* Add support for Vitest workspace ([#377](#377)) ([0b20990](0b20990)), closes [#376](#376)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant