✅ Deploy Preview for docs-eslint ready!

Name	Link
🔨 Latest commit	edecb67
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/67d82f662505400008e9f2f3
😎 Deploy Preview	https://deploy-preview-19431--docs-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

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

@JoshuaKGoldberg, I have a question: once this feature will be released, does it mean that ESLint could support the TypeScript linting out-of-box without any extra plugins or projects like typescript-eslint?

Depends what you mean by "TypeScript linting".

For syntax-only linting with just ESLint core rules, technically yes. See #19173 (comment) -> #19173 (comment) for a list of what will switch from needing a typescript-eslint extension rule to working out-of-the-box in ESLint core.

Typed linting, however, will not be supported in ESLint core. You'll still need typescript-eslint or an equivalent for that. See #19173 -> #19173 (comment).

ESLint core also presently doesn't have any plans that I know of to support TypeScript-specific rules that don't need typed linting. Example: @typescript-eslint/no-empty-object-type.

tl;dr: no, the strong recommendation from typescript-eslint going forward will still be to use typescript-eslint when linting TypeScript code.

We discussed today and we're at least going to start with this:

• meta.language = "javascript" - to indicate that this rule is meant for JavaScript or a derivative of it
• meta.dialects = ["javascript", "typescript"] - to indicate that this rule is known to work with both plain JavaScript and TypeScript.

For now, I think this is enough and we don't need to get to deep into the difference between being syntax-aware and type-aware. We're not planning on displaying this info anywhere so in the short-term it will be mostly for our own edification but we are also looking at how we can use this info to, for example, automatically disable JavaScript-specific rules when linting JSON.

Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.

Not stale! waiting for a review.

@JoshuaKGoldberg did you intended to include updates to check-rule-examples.js in this PR?

Ah, yes, and never mentioned this in the OP - editing it in now. Without the changes:

docs/src/rules/default-param-last.md
  56:4   error  Nonstandard language tag 'ts': use one of 'javascript', 'js' or 'jsx'
  59:20  error  Unexpected lint error found: Parsing error: Unexpected token :
  68:4   error  Nonstandard language tag 'ts': use one of 'javascript', 'js' or 'jsx'
  71:20  error  Unexpected lint error found: Parsing error: Unexpected token ?

Sorry! closed it accidentally.

Coming over from https://github.com/eslint/eslint/pull/19431/files#r1991932318: this PR is accumulating more and more TypeScript support changes. Would it be preferable to split them out once everything is working into their own PR?

I see #19529 was also sent with some of the same changes.

I think if we hide "Open in Playground" for now, that's enough to merge this. The playground changes may take a bit to get working and we can always iterate on the error location in a separate PR.

I think if we hide "Open in Playground" for now, that's enough to merge this. The playground changes may take a bit to get working and we can always iterate on the error location in a separate PR.

Agreed.