When building a plugin, webpack will typically chose to name the javascript entry file as `plugin-entry.min.js`, however it is valid under our build configurations for it to create a plugin entry file with any name, such as `plugin-entry.656f1eb7b0b32d1aa0fa.min.js`.

When it creates a plugin entry file with a different name, it will append the following information into the `plugin-manifest.json` file:

{
  "name": "logging-view-plugin",
  ...
  "registrationMethod": "callback",
  "baseURL": "/api/plugins/logging-view-plugin/",
  "loadScripts": ["plugin-entry.656f1eb7b0b32d1aa0fa.min.js"],
  "buildHash": "656f1eb7b0b32d1aa0fab058998b5b9f"
}
 

In order to inject the appropriate extension points while having  the `console-extensions.json` file keep all of the extension points for simple development, a separate hardcoded `plugin-manifest.json` file is used to add the extensions onto.

However, this will then lose the information created by the webpack build in the generated `plugin-manifest.json` leading to the plugin being unable to load it's entrypoint and failing to load.