compilerOptions.plugins accepts missing plugins without any logging or error information

🔎 Search Terms

compilerOptions, plugins, missing, module, plugin

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about missing plugins

⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAHjAvDAjAbiA

💻 Code

tsconfig.json:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "missing"
      }
    ]
  }
}

🙁 Actual behavior

TypeScript doesn't produce any debugging hints, or an error, if compilerOptions.plugins includes a reference to a missing plugin.

🙂 Expected behavior

When a tsconfig contains a compilerOptions.plugins entry that points to a plugin that could not be found, TypeScript should log or produce an error saying that it couldn't be found.

Additional information about the issue

No response

Start with the tsconfig.json example and the compilerOptions.plugins handling, then use the linked Playground case to reproduce the missing-plugin behavior. Done means a missing plugin reference produces the requested logging or error information without silently being ignored.