Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Repo(eslint-plugin): resolve remaining issues fromvitest migration #11099

Closed
Labels
accepting prsGo ahead, send a pull request that resolves this issuelocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.repo maintenancethings to do with maintenance of the repo, and not with code/docs
@aryaemami59

Description

@aryaemami59

Suggestion

Post-Vitest Migration: Fixes & Improvements

  • Use the@nx/vite:test executor inproject.json to align with other workspaces.
  • Fix path-related issues that causevitest --project=eslint-plugin to fail.
  • Replace.each with the new.for syntax to allow running the tests concurrently viavitest --sequence.concurrent=true, which does speed up local testing.
  • Replacefs withfs/promises to take advantage ofvitest’s better support for async/ESM code (vs.jest's preference for sync/CJS).
  • Remove the manual__dirname indocs.test.mts.vitestbackportsimport.meta.dirname,import.meta.filename as well asimport.meta.resolve() for older versions of Node.js.
  • Convert manually thrown errors in unit tests to standardvitest assertions.
  • Fix issue related toinvalidCases inno-unnecessary-template-expression.test.ts.
  • Refactor remaining loops to use.for syntax.
  • Add atest-single target toproject.json.
  • Correct theoutDir path intsconfig.spec.json.

Additional Info

I will submit a draft PR for this shortly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuelocked due to agePlease open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.repo maintenancethings to do with maintenance of the repo, and not with code/docs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp