Clarifiying the purpose

[tolzhabayev]

Afaik this package is internal only. If that is the case - it should be labeled as such here and on npmjs to avoid confusion.

[tolzhabayev]

@scottlepp @jackw review please?
My goal is to reduce confusion until we have a clear direction.

[scottlepp]

@tolzhabayev we do use this in open source plugins. We can't use newer components from Grafana UI since they aren't compatible with older versions of Grafana that we have to support with plugins. So we put those components we want to share between plugins here.

[scottlepp]

Not sure this is accurate since we use it in open source plugins.

[tolzhabayev]

Is this package used in any community plugins?

I mainly want to avoid confusion for the plugin developers in terms of:

• How does it differ from @grafana/ui
• Can I use this package to build a plugin as a plugin author in our community? <- we will most likely not accept any community plugin that is currently using this package and ask them to use @grafana/ui instead.
• Will this package be supported in the same way as other packages we offer to plugin authors?

To me it feels like the discussion on the future of how to handle what / which components should be where and when, etc. is still ongoing.

My intention is to reduce spread of this package to plugins that are created by grafana (even if open source, if it helps think about signatureType) until we have alignment on the future.