Docs: How to use in JS-only projects?

[rakleed]

Before You File a Documentation Request Please Confirm You Have Done The Following...

• I have looked for existing open or closed documentation requests that match my proposal.
• I have read the FAQ and my problem is not listed.

Suggested Changes

There are some rules that can be useful in a JavaScript project (no-deprecated, naming-convention, maybe more). Especially no-deprecated, since now a separate plugin for this is no longer supported.

But nowhere in the documentation is it explained how they can be used in a JS project. It seems like this should be enough:

/* eslint.config.js */

import tsEslint from 'typescript-eslint';

export defualt [
  {
    files: ['**/*.js', '**/*.jsx'],
    languageOptions: {
      parser: tsEslint.parser,
      parserOptions: {
        projectService: true,
      },
    },
    plugins: {
      '@typescript-eslint': tsEslint.plugin,
    },
    rules: {
      '@typescript-eslint/no-deprecated': 'error',
    },
  },
];

Affected URL(s)

https://typescript-eslint.io/getting-started/

Additional Info

No response

[JoshuaKGoldberg]

Duplicate of #10166, I think. Agreed this would be good to have. 🙂

[rakleed]

@JoshuaKGoldberg it seems to me that this issue #10166 is about something else, it just has a slightly inaccurate title.

If you read the description of the issue and what page the author is writing about, then this is a question about how to disable the rules for JS files in a TS project. I’m talking about how to initially set up typescript-eslint for a JS-only project.

[JoshuaKGoldberg]

Oh, sure. You're right. In my mind I was thinking of #10166 as the blanket "working with JS files in general" - but that's not actually what's in the issues. Thanks for the pushback 🙂