Questions around files not being included in their nearesttsconfig.json (e.g..js files withoutallowJs/checkJs)
You can't use non-tsconfig.json files as the main file path; if you're using TSConfigs to build with a separate system, building should be the custom non-tsconfig.json paths (e.g.tsconfig.build.json)

💖

docs: add more project service docs and FAQs

ac94652

Copy link

Contributor

typescript-eslintbot commentedAug 23, 2024

Thanks for the PR,@JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

Copy link

netlifybot commentedAug 23, 2024•
edited
Loading

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	`ef44301`
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/66c8b08740f8fa000981c741
😎 Deploy Preview	https://deploy-preview-9871--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (🔴 down 4 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 90 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to yourNetlify site configuration.

Copy link

nx-cloudbot commentedAug 23, 2024•
edited
Loading

☁️ Nx Cloud Report

CI is running/has finished running commands for commitef44301. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

✅ Successfully ran 2 targets

Sent with 💌 fromNxCloud.

JoshuaKGoldberg commented

Aug 23, 2024

View reviewed changes

docs/troubleshooting/typed-linting/index.mdx


		See [issue #2094 discussing project references](https://github.com/typescript-eslint/typescript-eslint/issues/2094) for more details.

		## Project Service Issues

		<HiddenHeading id="allowdefaultproject-glob-too-wide" />
		<HiddenHeading id="allowdefaultprojectforfiles-glob-too-wide" />

Copy link

MemberAuthor

JoshuaKGoldbergAug 23, 2024•
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This second heading is a holdover from the experimental/v7 name. I think anybody newly configuring the service should reasonably be on v8 now. Our docs don't still hold true for the old experimental way of holding the project service.

JoshuaKGoldberg commented

Aug 23, 2024

View reviewed changes

docs/packages/Parser.mdx

		@@ -320,38 +321,49 @@ module.exports = {
		This option brings two main benefits over the older `project`:

		- Simpler configurations: most projects shouldn't need to explicitly configure `project` paths or create `tsconfig.eslint.json`s
		- Improved performance: this API is optimized on the TypeScript side for speed
		- Initial versions of this option demonstrated performance changes in subsets of the typescript-eslint monorepo ranging from 11% slower to 70% faster

Copy link

MemberAuthor

JoshuaKGoldbergAug 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We're still working on performance & filling in the gaps on edge cases. IMO we should stop bragging about it until we can be very, very certain it's better the vast majority of the time.