Use dedicated "plugins" property in package.json for plugin loading

[Copilot]

The generator currently scans all dependencies in package.json to discover plugins. This prevents throwing errors when plugin DLLs are missing since regular dependencies can't be distinguished from plugins.

Changes

• GeneratorHandler.cs: Modified GetOrderedPluginDlls to:

  • Read from plugins property instead of dependencies
  • Throw InvalidOperationException when plugin dist directory or DLLs are not found
  • Return empty list when no plugins property exists (backward compatible)

• GeneratorHandlerTests.cs: Added tests for:

  • Missing plugin directory error case
  • Missing plugin DLL error case
  • Backward compatibility with no plugins property

Migration

Projects using plugins must move plugin entries from dependencies to a top-level plugins property. Regular dependencies remain in dependencies.

[!WARNING]

Original prompt

---

This section details on the original issue you should resolve

<filter_complete></filter_complete>

<issue_title>Plugin loading should use a special property rather than just dependencies</issue_title>
<issue_description>Currently, we look under dependencies in package.json for any plugins. This is problematic because the plugins need to be built, and the generator doesn't know what dep is supposed to be a plugin so it can't throw if there is no dll found. We should instead adopt a new convention where we add a top-level property, called "plugins" and look there for any plugins. This would allow us to throw if we don't find a dll for the specified by plugin preventing downstream bugs.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Plugin loading should use a special property rather than just dependencies #8885

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Plugin loading should use a special property rather than just dependencies</issue_title>
<issue_description>Currently, we look under dependencies in package.json for any plugins. This is problematic because the plugins need to be built, and the generator doesn't know what dep is supposed to be a plugin so it can't throw if there is no dll found. We should instead adopt a new convention where we add a top-level property, called "plugins" and look there for any plugins. This would allow us to throw if we don't find a dll for the specified by plugin preventing downstream bugs.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Plugin loading should use a special property rather than just dependencies #8885

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[JoshLove-msft]

@copilot revert thsi change

[Copilot]

Reverted in 9d7debf. The SampleService package.json now retains the original structure with logging-plugin in dependencies.