Skip to content

Actions: vitest-dev/vscode

Actions

Issue Labeled

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue-labeled.yml
108 workflow runs
108 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Error: The extension could not load any config. Issue Labeled #402: Issue #789 labeled by bluelovers
7s
7s
Loading spinner is not rounded Issue Labeled #401: Issue #788 labeled by bastiendmt
10s
10s
Worker shadows onUserConsoleLog with undefined, crashing vitest's logFailedTask when silent: 'passed-only' Issue Labeled #400: Issue #786 labeled by rhwinter
7s
7s
Monorepo shared tools package TypeScript config file Issue Labeled #399: Issue #785 labeled by soconnor-seeq
12s
12s
Swap the "Expected" and "Actual" tabs in the test results panel Issue Labeled #398: Issue #783 labeled by GoodbyeNJN
15s
15s
False Positive Annoyance Issue Labeled #397: Issue #781 labeled by CodeSmith32
13s
13s
silent option is being ignored Issue Labeled #396: Issue #780 labeled by mattjohnsonpint
17s
17s
vitest.rootConfig (and other path settings) don't resolve ${workspaceFolder} Issue Labeled #395: Issue #778 labeled by whme
8s
8s
Phantom tests appearing in test explorer based on variable name Issue Labeled #394: Issue #776 labeled by zoltanium
6s
6s
Copy Error and Copy Test Errors appear on non-Vitest test results Issue Labeled #393: Issue #774 labeled by alexchexes
5s
5s
ReferenceError: exports is not defined in ES module scope Issue Labeled #392: Issue #773 labeled by aminya
5s
5s
Coverage in vscode is no longer displayed in the gutters of the file with v1.50.0 Issue Labeled #391: Issue #770 labeled by versak
8s
8s
Updating to WSL v2.7.1 Prevents Config from Loading - EADDRINUSE Issue Labeled #390: Issue #766 labeled by D1g1talEntr0py
11s
11s
Fixture nodes from test.extend() shown as separate entries in test explorer tree Issue Labeled #389: Issue #763 labeled by sheremet-va
6s
6s
Fixture nodes from test.extend() shown as separate entries in test explorer tree Issue Labeled #388: Issue #763 labeled by kvet
7s
7s
Option to hide fixture nodes from test explorer tree Issue Labeled #387: Issue #762 labeled by kvet
7s
7s
[BUG]vitest plugin reports errors in vsocode Issue Labeled #386: Issue #759 labeled by bd-dxg
8s
8s
Custom fixture missing in gutter and test explorer Issue Labeled #385: Issue #756 labeled by aaronzhongg
7s
7s
describe.concurrent.each() behaves differently than describe.each() Issue Labeled #384: Issue #752 labeled by mikeharder
8s
8s
I don't have a node, only a bun, and now vitest doesn't work. Issue Labeled #383: Issue #741 labeled by bd-dxg
8s
8s
Allow on the fly toggling of configs Issue Labeled #382: Issue #739 labeled by andyearnshaw
8s
8s
Version 1.24.7 stuck at "Resolving Vitest..." when shell type is terminal Issue Labeled #381: Issue #636 labeled by sheremet-va
7s
7s
vscode plugin does not respect vitest onConsoleLog configuration Issue Labeled #380: Issue #736 labeled by sheremet-va
7s
7s
.gitignore not respected Issue Labeled #379: Issue #737 labeled by vkozio
10s
10s
vscode plugin does not respect vitest onConsoleLog configuration Issue Labeled #378: Issue #736 labeled by brokenmass
7s
7s