Skip to content

Migrate from ESLint to Oxlint and update build tooling to vite-plus #551

Migrate from ESLint to Oxlint and update build tooling to vite-plus

Migrate from ESLint to Oxlint and update build tooling to vite-plus #551

Triggered via pull request March 26, 2026 18:20
Status Failure
Total duration 43s
Artifacts

build.yml

on: pull_request
deploy docs
0s
deploy docs
cypress
0s
cypress
deploy the-vue-point
0s
deploy the-vue-point
crawl docs
0s
crawl docs
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
tests
Process completed with exit code 1.
packages/iles/tests/build.spec.ts > building docs site > html files: packages/iles/tests/build.spec.ts#L101
Error: Snapshot `building docs site > html files 5` mismatched - Expected + Received @@ -62,8 +62,8 @@ <li><del>Vue 3 IE 11 Compatibility Build (estimated Q2)</del></li> <li>Vue 2.7 (estimated Q2/3)</li> <li>SSR support in Vite</li> <li>Vuex 5 (TBD)</li> </ul> - <p>In addition, we are excited about other frameworks and libraries in the ecosystem making progress towards Vue 3 support. And of course, we can’t wait to see what new ideas and tools you all have as we embark on a new chapter in the Vue.js roadmap.</p></div></div><footer class="text-sm font-medium leading-5 divide-y divide-gray-200 xl:col-start-1 xl:row-start-2"><div class="py-8"><h2 class="text-xs tracking-wide uppercase text-gray-500"> Next Article </h2><div class="link"><a href="/posts/vue-3-2.html">Vue 3.2 Released!</a></div></div><div class="py-8"><h2 class="text-xs tracking-wide uppercase text-gray-500"> Previous Article </h2><div class="link"><a href="/posts/vue-3-one-piece.html">Announcing Vue 3.0 &quot;One Piece&quot;</a></div></div><ile-root id="ile-2" class="block pt-8"><a data-hk=ile-200 class="link" href="/">← <!--$-->Back to the blog<!--/--></a></ile-root></footer></div></article><footer class="w-full xl:grid xl:grid-cols-4"><div class="pb-12 text-center text-sm xl:col-start-2 xl:col-span-3"><a class="inline-block" href="https://iles-docs.netlify.app"> Built with <img class="iles inline-block h-6 ml-0.5 -mt-3" height="28" alt="logo" src="/iles.svg"></a></div></footer></main></div></div> + <p>In addition, we are excited about other frameworks and libraries in the ecosystem making progress towards Vue 3 support. And of course, we can’t wait to see what new ideas and tools you all have as we embark on a new chapter in the Vue.js roadmap.</p></div></div><footer class="text-sm font-medium leading-5 divide-y divide-gray-200 xl:col-start-1 xl:row-start-2"><div class="py-8"><h2 class="text-xs tracking-wide uppercase text-gray-500"> Next Article </h2><div class="link"><a href="/posts/vue-3-2.html">Vue 3.2 Released!</a></div></div><div class="py-8"><h2 class="text-xs tracking-wide uppercase text-gray-500"> Previous Article </h2><div class="link"><a href="/posts/vue-3-one-piece.html">Announcing Vue 3.0 &quot;One Piece&quot;</a></div></div><ile-root id="ile-2" class="block pt-8"><a class="link" href="/">← <!--$-->Back to the blog<!--/--></a></ile-root></footer></div></article><footer class="w-full xl:grid xl:grid-cols-4"><div class="pb-12 text-center text-sm xl:col-start-2 xl:col-span-3"><a class="inline-block" href="https://iles-docs.netlify.app"> Built with <img class="iles inline-block h-6 ml-0.5 -mt-3" height="28" alt="logo" src="/iles.svg"></a></div></footer></main></div></div> </body> </html>" ❯ createMismatchError node_modules/.pnpm/@voidzero-dev+vite-plus-test@0.1.14_@types+node@20.14.12_jiti@2.6.1_terser@5.36.0_tsx@4.19.2__dnuu724vsm4dcxluo4h2i2g4x4/node_modules/@voidzero-dev/vite-plus-test/dist/@vitest/snapshot/index.js:799:17 ❯ SnapshotClient.assert node_modules/.pnpm/@voidzero-dev+vite-plus-test@0.1.14_@types+node@20.14.12_jiti@2.6.1_terser@5.36.0_tsx@4.19.2__dnuu724vsm4dcxluo4h2i2g4x4/node_modules/@voidzero-dev/vite-plus-test/dist/@vitest/snapshot/index.js:882:13 ❯ Proxy.<anonymous> node_modules/.pnpm/@voidzero-dev+vite-plus-test@0.1.14_@types+node@20.14.12_jiti@2.6.1_terser@5.36.0_tsx@4.19.2__dnuu724vsm4dcxluo4h2i2g4x4/node_modules/@voidzero-dev/vite-plus-test/dist/chunks/test.CBQUpOM3.js:177:25 ❯ Proxy.<anonymous> node_modules/.pnpm/@voidzero-dev+vite-plus-test@0.1.14_@types+node@20.14.12_jiti@2.6.1_terser@5.36.0_tsx@4.19.2__dnuu724vsm4dcxluo4h2i2g4x4/node_modules/@voidzero-dev/vite-plus-test/dist/@vitest/expect/index.js:1155:19 ❯ Proxy.methodWrapper node_modules/.pnpm/@voidzero-dev+vite-plus-test@0.1.14_@types+node@20.14.12_jiti@2.6.1_terser@5.36.0_tsx@4.19.2__dnuu724vsm4dcxluo4h2i2g4x4/node_modules/@voidzero-dev/vite-plus-test/dist/vendor/chai.mjs:1234:23 ❯ assertHTML packages/iles/tests/build.spec.ts:101:17 ❯ packages/iles/tests/build.spec.ts:43:5 ❯ node_modules/.pnpm/@voidzero-dev+vite-plus
tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/