[Compatibility] Some package want to use it's community driven plugin

[njfamirm]

I've looked at the docs resources you shared about compatibility.

My compatibility question is: Logically, a package shouldn't list community-created plugins as its own peerDependencies. A plugin depends on the core package, not the other way around.

Do these changes also need to be made to this file?

The issue was resolved using a package extension.

packageExtensions:
  "typedoc@*":
    peerDependencies:
      typedoc-plugin-markdown: "*"

[clemyan]

Logically, a package shouldn't list community-created plugins as its own peerDependencies

Generally, yes. Unless that ecosystem has some "blessed" plugins that the core explicitly requires to function or the core itself provides additional functionality when a that plugin is install.

The issue was resolved using a package extension

What issue? Am I missing some context here?

[njfamirm]

What issue? Am I missing some context here?

No, that's fine