Skip to content

chore: switch to typescript-eslint projectService setting #13839

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

benmccann
Copy link
Member

The typescript-eslint docs recommend using projectService over project: https://typescript-eslint.io/packages/parser/#project

My own testing shows projectService to be slightly faster.

With project:

real 0m36.047s
user 1m10.914s

real 0m29.111s
user 0m56.673s

real 0m29.084s
user 0m53.078s

real 0m31.287s
user 1m3.867s

real 0m28.033s
user 0m53.280s

With projectService:

real 0m36.333s
user 1m10.211s

real 0m29.553s
user 0m56.994s

real 0m27.674s
user 0m53.531s

real 0m27.125s
user 0m49.013s

real 0m26.967s
user 0m49.587s

Copy link

changeset-bot bot commented May 28, 2025

⚠️ No Changeset found

Latest commit: d45d72d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@svelte-docs-bot
Copy link

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 this pull request may close these issues.

1 participant