Edward Faulkner

A followup to my last point: if you want to just access `.value` immediately without worrying about the state, that case is better served by a variant that accepts the...

And if somebody wants immediate access to `.value` and they want their placeholder to be `undefined`, that's also fine because they can say so explicitly like `TrackedPromise`.

> We can have the types behave strictly without throwing hard runtime errors. I could probably live with that as a compromise, and as a TS user it wouldn't matter...

> so there are lot more states than just a single promise, and we don't want to prevent users from modelling those states Then how is this difference from Resource?...

We need to address at least the outstanding bugs in https://github.com/ember-cli/ember-cli/issues/10814 like - `ember test` hanging

I think we should land this. Can we make it not a draft?

To be clear, this is an issue under embroider builds on ember > 6.1. We were careful not to destabilize the default build and the inspector should work fine in...

It would be helpful if somebody wants to clean up and centralize all the ways inspector is accessing modules from ember. I see `require`, `requireModule`, `this.require`, `EmberLoader.require`, and `emberSafeRequire` scattered...

In my previous comment I deliberately didn't go into the implementation details of how ember can provide the debug APIs, but we already have the infrastructure to support that and...

I would add that Embroider can easily polyfill this feature on ember versions that lack it.