diff --git a/.github/workflows/issue-close-require.yml b/.github/workflows/issue-close-require.yml index 91076b680741..292cdfb20f7f 100644 --- a/.github/workflows/issue-close-require.yml +++ b/.github/workflows/issue-close-require.yml @@ -11,7 +11,7 @@ jobs: issues: write # for actions-cool/issues-helper to update issues steps: - name: needs reproduction - uses: actions-cool/issues-helper@9861779a695cf1898bd984c727f685f351cfc372 # v3.7.2 + uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5 with: actions: close-issues token: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/issue-labeled.yml b/.github/workflows/issue-labeled.yml index 421eb32dc212..86f90125d60f 100644 --- a/.github/workflows/issue-labeled.yml +++ b/.github/workflows/issue-labeled.yml @@ -12,7 +12,7 @@ jobs: steps: - name: needs reproduction if: github.event.label.name == 'needs reproduction' - uses: actions-cool/issues-helper@9861779a695cf1898bd984c727f685f351cfc372 # v3.7.2 + uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5 with: actions: create-comment token: ${{ secrets.GITHUB_TOKEN }} diff --git a/.gitignore b/.gitignore index 5a6e9c76cbe4..996a288e10e9 100644 --- a/.gitignore +++ b/.gitignore @@ -21,7 +21,6 @@ bench/test/*/*/ **/bench.json **/browser/browser.json docs/public/user-avatars -docs/public/sponsors .eslintcache docs/.vitepress/cache/ !test/cli/fixtures/dotted-files/**/.cache diff --git a/README.md b/README.md index 14b8fefe91ea..c81727a02711 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,16 @@
-
-
-
+
+
+
+
+
+
+
+ Reuse Vite's config and plugins - consistent across your app and tests.
+ But it's not required to use Vitest!
+
+ Expect, snapshot, coverage, and more - migrating from Jest is
+ straightforward.
+
+ + Only rerun the related changes, just like HMR for tests! +
+
+
+ Out-of-box ESM, TypeScript and JSX support powered by Oxc.
+
+ A Vite-native testing framework. It's fast! +
+ +
+
+ Vitest was created to make testing just work for Vite apps. By building on top of Vite, Vitest
+ natively
+ understands your Vite config and is able to reuse the same resolve and
+ transform pipelines.
+
+ You can also use Vitest even if you are not using Vite. It is Jest-comptible + and works for backend code too. +
+ Learn more +