PerBundleAddonCache

The default implementation here is to indicate if the original addon entry point has the allowCachingPerBundle flag set either on itself or on its prototype.

If a consuming application specifies a relative path to a custom utility via the ember-addon.perBundleAddonCacheUtil configuration, we prefer the custom implementation provided by the consumer.

An optimization we support from lazy engines is the following:

If an addon instance is supposed to be bundled with a particular lazy engine, and same addon is also to be bundled by a common LCA host, prefer the one bundled by the host (since it's ultimately going to be deduped later by ember-engines).

NOTE: this only applies if this.engineAddonTransitiveDedupeEnabled is truthy. If it is not, the bundle host always "owns" the addon instance.

If deduping is enabled and the LCA host also depends on the same addon, the lazy-engine instances of the addon will all be proxies to the one in the LCA host. This function indicates whether the bundle host passed in (either the project or a lazy engine) is really the bundle host to "own" the new addon.

Create a cache entry object for a given (non-bundle-host) addon to put into an addon cache.

Creates a cache entry for the bundleHostCache. Because we want to use the same sort of proxy for both bundle hosts and for 'regular' addon instances (though their cache entries have slightly different structures) we'll use the Symbol from getAddonProxy.

Given a parent object of a potential addon (another addon or the project), go up the 'parent' chain to find the potential addon's bundle host object (i.e. lazy engine or project.) Because Projects are always bundle hosts, this should always pass, but we'll throw if somehow it doesn't work.

Called from PackageInfo.getAddonInstance(), return an instance of the requested addon or a Proxy, based on the type of addon and its bundle host.

Returns a proxy to a target with specific handling for the parent property, as well has to handle the app property; that is, the proxy should maintain correct local state in closure scope for the app property if it happens to be set by ember-cli. Other than parent & app, this function also proxies almost everything to target[TARGET_INSTANCE] with a few exceptions: we trap & return[]foraddons, and we don't return the originalincluded(it's already called on the "real" addon byember-cli`).

Note: the target is NOT the per-bundle cacheable instance of the addon. Rather, it is a cache entry POJO from PerBundleAddonCache.

Resolves the perBundleAddonCacheUtil; this prefers the custom provided version by the consuming application, and defaults to an internal implementation here.

Validates that a new cache key for a given tree type matches the previous cache key for the same tree type. To opt-in to bundle addon caching for a given addon it's assumed that it returns stable cache keys; specifically this is because the interplay between bundle addon caching and ember-engines when transitive deduplication is enabled assumes stable cache keys, so we validate for this case here.