Is there any way to force NodeBB to see a plugin that doesn't match the
nodebb-plugin- name structure?
My organization is using scopes to have 'private' packages published to our private registry. (Our private registry is still public so this still meet's NodeBB's GPL 3 license)
This means the plugin name comes through as
@acmecorp/nodebb-plugin-pluginname. This in turn means the plugin isn't seen by NodeBB and not listed in the admin installed packages and therefore can't be activated.
Though a little less common, scoped packages are a standard part of npm. NodeBB should be able to handle this use case.