ember-cli
feat: adds the strict resolver as an option
Summary
Originally from https://github.com/stefanpenner/ember-strict-resolver we have been using this in production for a few years! It is faster and less prone to errors as it doesn't allow configuration.
It would be great to support this as a first class resolver.
Details
When debugging how often we call into the resolver to access values from the registry, on an initial page load of linkedin feed we access the registry ~11,800 times.
When running linked.com feed using the ember-strict resolver we see in the experiment over ~300ms faster The differences are:
boot phase estimated difference -188ms [-195ms to -181ms] transition phase estimated difference -42ms [-57ms to -27ms] render phase estimated difference -23ms [-37ms to -9ms]
Shoutout to @stefanpenner for making this library and making it all possible!
