Can't enable besides tseslint recommended

[NomarCub]

I have an existing config that has some recommended tseslint rules enabled. When I try to add this plugin, my config is always invalid. I tried tseslint.config, eslint's defineConfig, and putting this one in any order, but it always screws up the parser options and results in an error. How can I do it?

A common error:

Oops! Something went wrong! :(

ESLint: 9.39.2

Error: Error while loading rule '@typescript-eslint/await-thenable': You have used a rule which requires type information, but don't have parserOptions set to generate type information for this file. See https://typescript-eslint.io/getting-started/typed-linting for enabling linting with type information.
Parser: typescript-eslint/parser

[mnaoumov]

@NomarCub if you send a link to your repo, I will show how to modify the config to fix the issue

[NomarCub]

Here it is: https://github.com/NomarCub/obsidian-open-vscode/blob/main/eslint.config.mjs

[mnaoumov]

@NomarCub , unfortunately the fixed version wasn't published yet. For the published version (0.1.9) the workaround is

import eslint from "@eslint/js";
import tseslint from "typescript-eslint";
import obsidianmd from "eslint-plugin-obsidianmd";

/* eslint-disable-next-line @typescript-eslint/no-deprecated --
   TODO: fix, see https://typescript-eslint.io/packages/typescript-eslint/#config-deprecated */
export default tseslint.config({
    files: ["**/*.{ts,mts,mjs}"],
    extends: [
        eslint.configs.recommended,
        tseslint.configs.strictTypeChecked,
        tseslint.configs.stylisticTypeChecked,
    ],
    plugins: {
        obsidianmd,
    },
    languageOptions: {
        parserOptions: { projectService: true },
    },
    rules: {
        // eslint-disable-next-line @typescript-eslint/no-misused-spread -- Temporary fix for v0.1.9.
        ...obsidianmd.configs.recommended,
        "@typescript-eslint/explicit-function-return-type": ["error", { allowExpressions: true }],
        "@typescript-eslint/restrict-template-expressions": ["error", { allowNumber: true }],
        "@typescript-eslint/no-non-null-assertion": "off",
    },
});

[NomarCub]

I see, thanks!
How would this look like for defineConfig, like in this plugin's readme? I'd wanna switch eventually, and tried it for the Obsidian plugin too before posting this.
Also, do you know when can a new version be expected?

[mnaoumov]

import { defineConfig } from "eslint/config";
import eslint from "@eslint/js";
import tseslint from "typescript-eslint";
import obsidianmd from "eslint-plugin-obsidianmd";

export default defineConfig({
    files: ["**/*.{ts,mts,mjs}"],
    extends: [
        eslint.configs.recommended,
        ...tseslint.configs.strictTypeChecked,
        ...tseslint.configs.stylisticTypeChecked,
    ],
    plugins: {
        obsidianmd,
    },
    languageOptions: {
        parserOptions: { projectService: true },
    },
    rules: {
        // eslint-disable-next-line @typescript-eslint/no-misused-spread -- Temporary fix for v0.1.9.
        ...obsidianmd.configs.recommended,
        "@typescript-eslint/explicit-function-return-type": ["error", { allowExpressions: true }],
        "@typescript-eslint/restrict-template-expressions": ["error", { allowNumber: true }],
        "@typescript-eslint/no-non-null-assertion": "off",
    },
});

Improved config PRs were merged a while ago, but the Obsidian team didn't make a release yet (since November 2025). I can't provide an ETA.

[NomarCub]

Both of the configs worked perfectly, thanks!
My personal issue is solved, but I'll keep this open, cause better official documentation for this would be nice.

I also type-check my ESLint config, those interested can see my final config with type-check suppressions in my repo.

@mnaoumov How did you arrive at these configs BTW? I looked through some typescript-eslint docs before and couldn't figure it out, their starter packs are structured differently.

[mnaoumov]

How did you arrive at these configs BTW

I also struggled to enable the plugin properly. So I had to do some reverse engineering. I even made PRs to improve the config part. Once they are released, the usage will be more obvious