Public API for 3rd party integration

[lifeart]

At the moment ember-inspector has bunch of initialization magic (checking for some special props to exist). It would be great to have minimal public API to avoid hacking it around. It allow us to bring ember inspector to wider community.

I had few experiments for minimal script to boot ember inspector in custom environments:

• Vite & Ember (modules) environment without amd, works with this compat file: https://github.com/lifeart/demo-ember-vite/blob/master/src/config/inspector.ts
• Glimmer like runtime, with created from scratch boot logic: https://github.com/lifeart/glimmer-next/blob/master/src/utils/ember-inspector.ts

No call to action here, just leaving some documentation (code references) how to deal with ember-inspector in 3rd party environments.

[patricklx]

I think it should just better integrate with ember core in an independent way.
An idea here:
emberjs/ember.js#20580

[rtablada]

I think that 3rd party or packagization is really big improvement and decouples a lot of ability for even Ember internals to be able to break up utilities.

Vue DevTools >6 follow this pattern.

In particular this allows teams to also configure which panes are/aren't initialized. The Ember dev tools for data and even container can become a problem for some larger applications or can vary drastically depending on the Ember version.

Also tools like ember-provide-consume-context could have context providers shown in a debugger.

On a more specific use case, my current project really would benefit in being able to author tools within the inspector for debugging and integration with base information like "owner" and basic services. But, I have found that a simple authorship model similar to that of the Vue debug tools was also valuable for my last two companies as well and has been missing in Ember inspector