add tracked utilities for ember-inspector

[patricklx]

so we do not need to do this hack:
https://github.com/emberjs/ember-inspector/blob/8c4cd42a50b614981f8b863dfe07e116ced04953/ember_debug/object-inspector.js#L41

[patricklx]

@NullVoxPopuli can we have this?

[NullVoxPopuli]

Maybe, i'm behind an getting the VM integrated in to ember, so that's blocking me actually reviewing all these prs.

At first glance though, does this need to be in production? Can we instead wrap all the behavior in meta.env?

[patricklx]

i think it would be nice to have it in prod as well.
or when window.EmberENV = { _DEBUG_RENDER_TREE: true }; is set? or some other key?
https://github.com/emberjs/ember-inspector/blob/main/skeletons/web-extension/scripts/boot.js#L1C21-L1C39

[patricklx]

@chancancode can you have a look at this? At least i would like the object/property info on the tag for inspector

[NullVoxPopuli]

artifact-1.pdf

[NullVoxPopuli]

Is there a way to make it faster?

[patricklx]

Is there a way to make it faster?

Maybe, nodejs creates a new hidden class whenever a new property is added to an object... Lets see if thats the cause

[NullVoxPopuli]

artifact-1.pdf

[NullVoxPopuli]

thanks for the tests!! 🎉

[NullVoxPopuli]

since we export * here, should we do anything in the function implementations themselves to no-op in production?

[NullVoxPopuli]

👍 looks good to me.

I don't really know what to do about production debugging, because it is handy to have a good debugging experience in production -- which we already have -- I wonder if that would be more of an opt-out in the future to have all the meta and stuff stripped in prod.

[NullVoxPopuli]

Approving, as this is mostly moving code out of the inspector