An architecture that doesn't require using the resolver

[NullVoxPopuli]

authenticators, services, etc, all require being on the resolver.

When trying to use the same auth in many apps, I don't want to have to make sure this is all wired up correctly -- by using the module graph, and singleton keys based off the owner, it should be doable to ditch the resolver requirements altogether.

[johanrd]

yes. for anyone stumbling on this, and for context for migrating an app from ember-resolver + @embroider/virtual/compat-modules to ember-strict-application-resolver (the RFC polyfill):

What ESA required from the resolver, in the order we hit it:

1. config:environment must be in the module map.

The initializer calls registry.resolveRegistration('config:environment') directly. Without it: TypeError: Cannot read properties of undefined (reading 'ember-simple-auth').
Fix: Add './config/environment': { default: config } explicitly to modules.

2. The initializer must be registered manually.

ESA ships ./initializers/ember-simple-auth via app-js. Without loadInitializers, it is never called. There is no mechanism in ember-strict-application-resolver to auto-discover and run addon-contributed initializers.

Fix: add App.initializer(emberSimpleAuthInitializer) after the class definition.

3. session-store:application must be in the module map.

InternalSession.init() calls getOwner(this).lookup('session-store:application') by string key. The app has app/session-stores/application.ts but session-stores/ wasn't in any glob.

Fix: add ...import.meta.glob('./session-stores/**/*.{js,ts}', { eager: true }).

4. authenticator:firebase (or whatever authenticator) must be in the module map.

_lookupAuthenticator(authenticatorFactory) calls owner.lookup(authenticatorName) by string.

Fix: add ..import.meta.glob('./authenticators/**/*.{js,ts}', { eager: true }).

session-store:application and authenticators seems to be looked up purely by string key through the owner — there's no static import path