ember-source 4.4.0-alpha.7 → 4.5.0-alpha.2

package/docs/data.json

@@ -3,7 +3,7 @@
     "name": "The Ember API",
     "description": "The Ember API: a framework for building ambitious web applications",
     "url": "https://emberjs.com/",
-    "version": "4.4.0-alpha.7"
+    "version": "4.5.0-alpha.2"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -1116,8 +1116,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/-internals/runtime/lib/system/namespace.js": {
-      "name": "packages/@ember/-internals/runtime/lib/system/namespace.js",
+    "packages/@ember/-internals/runtime/lib/system/namespace.ts": {
+      "name": "packages/@ember/-internals/runtime/lib/system/namespace.ts",
       "modules": {},
       "classes": {
         "Namespace": 1
@@ -1322,15 +1322,8 @@
         "Ember": 1
       }
     },
-    "packages/@ember/application/lib/application.d.ts": {
-      "name": "packages/@ember/application/lib/application.d.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
-    "packages/@ember/application/lib/application.js": {
-      "name": "packages/@ember/application/lib/application.js",
+    "packages/@ember/application/lib/application.ts": {
+      "name": "packages/@ember/application/lib/application.ts",
       "modules": {
         "@ember/application": 1
       },
@@ -1340,8 +1333,8 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/application/lib/lazy_load.js": {
-      "name": "packages/@ember/application/lib/lazy_load.js",
+    "packages/@ember/application/lib/lazy_load.ts": {
+      "name": "packages/@ember/application/lib/lazy_load.ts",
       "modules": {},
       "classes": {},
       "fors": {
@@ -1349,8 +1342,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/application/instance.js": {
-      "name": "packages/@ember/application/instance.js",
+    "packages/@ember/application/instance.ts": {
+      "name": "packages/@ember/application/instance.ts",
       "modules": {},
       "classes": {
         "ApplicationInstance": 1,
@@ -1474,8 +1467,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/engine/index.js": {
-      "name": "packages/@ember/engine/index.js",
+    "packages/@ember/engine/index.ts": {
+      "name": "packages/@ember/engine/index.ts",
       "modules": {},
       "classes": {
         "Engine": 1
@@ -1483,8 +1476,8 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/engine/instance.js": {
-      "name": "packages/@ember/engine/instance.js",
+    "packages/@ember/engine/instance.ts": {
+      "name": "packages/@ember/engine/instance.ts",
       "modules": {},
       "classes": {
         "EngineInstance": 1
@@ -1825,7 +1818,7 @@
       "namespaces": {},
       "tag": "main",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 43,
+      "line": 44,
       "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  name: 'Jill'\n});\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
       "itemtype": "main"
     },
@@ -2045,8 +2038,8 @@
         "ApplicationInstance": 1
       },
       "tag": "module",
-      "file": "packages/@ember/application/instance.js",
-      "line": 305
+      "file": "packages/@ember/application/instance.ts",
+      "line": 316
     },
     "@ember/array": {
       "name": "@ember/array",
@@ -2162,8 +2155,8 @@
       },
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@ember/engine/instance.js",
-      "line": 17
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 26
     },
     "@ember/error": {
       "name": "@ember/error",
@@ -2361,7 +2354,7 @@
       "module": "rsvp",
       "namespace": "",
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 55,
+      "line": 51,
       "description": "A container used to instantiate and cache objects.\n\nEvery `Container` must be associated with a `Registry`, which is referenced\nto determine the factory and options that should be used to instantiate\nobjects.\n\nThe public API for `Container` is still in flux and should not be considered\nstable.",
       "access": "private",
       "tagname": ""
@@ -2377,7 +2370,7 @@
       "module": "rsvp",
       "namespace": "",
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 59,
+      "line": 56,
       "description": "A registry used to store factory and option information keyed\nby type.\n\nA `Registry` stores the factory and option information needed by a\n`Container` to instantiate and cache objects.\n\nThe API for `Registry` is still in flux and should not be considered stable.",
       "access": "private",
       "tagname": "",
@@ -2556,7 +2549,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 43,
+      "line": 44,
       "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```app/templates/application.hbs\n<Cost @cents={{230}} />\n```\n\n```app/components/cost.hbs\n<div>{{format-currency @cents currency=\"$\"}}</div>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```handlebars\n{{if @showMoney (format-currency @cents currency=\"$\")}}\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```app/helpers/format-currency.js\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
       "extends": "CoreObject",
       "access": "public",
@@ -3281,7 +3274,7 @@
       "extensions": [],
       "plugin_for": [],
       "extension_for": [
-        "Application",
+        "Engine",
         "EngineInstance"
       ],
       "module": "ember",
@@ -3357,8 +3350,8 @@
       "extension_for": [],
       "module": "@ember/application",
       "namespace": "",
-      "file": "packages/@ember/-internals/runtime/lib/system/namespace.js",
-      "line": 19,
+      "file": "packages/@ember/-internals/runtime/lib/system/namespace.ts",
+      "line": 20,
       "description": "A Namespace is an object usually used to contain other objects or methods\nsuch as an application or framework. Create a namespace anytime you want\nto define one of these new containers.\n\n# Example Usage\n\n```javascript\nMyFramework = Ember.Namespace.create({\n  VERSION: '1.0.0'\n});\n```",
       "extends": "EmberObject",
       "access": "public",
@@ -3516,13 +3509,10 @@
       "extension_for": [],
       "module": "@ember/application",
       "namespace": "",
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 30,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 31,
       "description": "An instance of `Application` is the starting point for every Ember\napplication. It instantiates, initializes and coordinates the\nobjects that make up your app.\n\nEach Ember app has one and only one `Application` object. Although\nEmber CLI creates this object implicitly, the `Application` class\nis defined in the `app/app.js`. You can define a `ready` method on the\n`Application` class, which will be run by Ember when the application is\ninitialized.\n\n```app/app.js\nconst App = Application.extend({\n  ready() {\n    // your code here\n  }\n})\n```\n\nBecause `Application` ultimately inherits from `Ember.Namespace`, any classes\nyou create will have useful string representations when calling `toString()`.\nSee the `Ember.Namespace` documentation for more information.\n\nWhile you can think of your `Application` as a container that holds the\nother classes in your application, there are several other responsibilities\ngoing on under-the-hood that you may want to understand. It is also important\nto understand that an `Application` is different from an `ApplicationInstance`.\nRefer to the Guides to understand the difference between these.\n\n### Event Delegation\n\nEmber uses a technique called _event delegation_. This allows the framework\nto set up a global, shared event listener instead of requiring each view to\ndo it manually. For example, instead of each view registering its own\n`mousedown` listener on its associated element, Ember sets up a `mousedown`\nlistener on the `body`.\n\nIf a `mousedown` event occurs, Ember will look at the target of the event and\nstart walking up the DOM node tree, finding corresponding views and invoking\ntheir `mouseDown` method as it goes.\n\n`Application` has a number of default events that it listens for, as\nwell as a mapping from lowercase events to camel-cased view method names. For\nexample, the `keypress` event causes the `keyPress` method on the view to be\ncalled, the `dblclick` event causes `doubleClick` to be called, and so on.\n\nIf there is a bubbling browser event that Ember does not listen for by\ndefault, you can specify custom events and their corresponding view method\nnames by setting the application's `customEvents` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent Ember from setting up a listener for a default event,\nspecify the event name with a `null` value in the `customEvents`\nproperty:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // prevent listeners for mouseenter/mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```\n\nBy default, the application sets up these event listeners on the document\nbody. However, in cases where you are embedding an Ember application inside\nan existing page, you may want it to set up the listeners on an element\ninside the body.\n\nFor example, if only events inside a DOM element with the ID of `ember-app`\nshould be delegated, set your application's `rootElement` property:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  rootElement: '#ember-app'\n});\n```\n\nThe `rootElement` can be either a DOM element or a CSS selector\nstring. Note that *views appended to the DOM outside the root element will\nnot receive events.* If you specify a custom root element, make sure you only\nappend views inside it!\n\nTo learn more about the events Ember components use, see\n\n[components/handling-events](https://guides.emberjs.com/release/components/handling-events/#toc_event-names).\n\n### Initializers\n\nTo add behavior to the Application's boot process, you can define initializers in\nthe `app/initializers` directory, or with `ember generate initializer` using Ember CLI.\nThese files should export a named `initialize` function which will receive the created `application`\nobject as its first argument.\n\n```javascript\nexport function initialize(application) {\n  // application.inject('route', 'foo', 'service:foo');\n}\n```\n\nApplication initializers can be used for a variety of reasons including:\n\n- setting up external libraries\n- injecting dependencies\n- setting up event listeners in embedded apps\n- deferring the boot process using the `deferReadiness` and `advanceReadiness` APIs.\n\n### Routing\n\nIn addition to creating your application's router, `Application` is\nalso responsible for telling the router when to start routing. Transitions\nbetween routes can be logged with the `LOG_TRANSITIONS` flag, and more\ndetailed intra-transition logging can be logged with\nthe `LOG_TRANSITIONS_INTERNAL` flag:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create({\n  LOG_TRANSITIONS: true, // basic logging of successful transitions\n  LOG_TRANSITIONS_INTERNAL: true // detailed logging of all routing steps\n});\n```\n\nBy default, the router will begin trying to translate the current URL into\napplication state once the browser emits the `DOMContentReady` event. If you\nneed to defer routing, you can call the application's `deferReadiness()`\nmethod. Once routing can begin, call the `advanceReadiness()` method.\n\nIf there is any setup required before routing begins, you can implement a\n`ready()` method on your app that will be invoked immediately before routing\nbegins.",
       "extends": "Engine",
-      "uses": [
-        "RegistryProxyMixin"
-      ],
       "access": "public",
       "tagname": ""
     },
@@ -3536,8 +3526,8 @@
       "extension_for": [],
       "module": "@ember/application",
       "namespace": "",
-      "file": "packages/@ember/application/instance.js",
-      "line": 10,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 27,
       "description": "The `ApplicationInstance` encapsulates all of the stateful aspects of a\nrunning `Application`.\n\nAt a high-level, we break application boot into two distinct phases:\n\n* Definition time, where all of the classes, templates, and other\n  dependencies are loaded (typically in the browser).\n* Run time, where we begin executing the application once everything\n  has loaded.\n\nDefinition time can be expensive and only needs to happen once since it is\nan idempotent operation. For example, between test runs and FastBoot\nrequests, the application stays the same. It is only the state that we want\nto reset.\n\nThat state is what the `ApplicationInstance` manages: it is responsible for\ncreating the container that contains all application state, and disposing of\nit once the particular test run or FastBoot request has finished.",
       "access": "public",
       "tagname": "",
@@ -3553,8 +3543,8 @@
       "extension_for": [],
       "module": "@ember/application",
       "namespace": "ApplicationInstance",
-      "file": "packages/@ember/application/instance.js",
-      "line": 305,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 316,
       "description": "A list of boot-time configuration options for customizing the behavior of\nan `ApplicationInstance`.\n\nThis is an interface class that exists purely to document the available\noptions; you do not need to construct it manually. Simply pass a regular\nJavaScript object containing the desired options into methods that require\none of these options object:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\nNot all combinations of the supported options are valid. See the documentation\non `Application#visit` for the supported configurations.\n\nInternal, experimental or otherwise unstable flags are marked as private.",
       "access": "public",
       "tagname": ""
@@ -3650,12 +3640,12 @@
       "extension_for": [],
       "module": "@ember/engine",
       "namespace": "",
-      "file": "packages/@ember/engine/index.js",
-      "line": 30,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 39,
       "description": "The `Engine` class contains core functionality for both applications and\nengines.\n\nEach engine manages a registry that's used for dependency injection and\nexposed through `RegistryProxy`.\n\nEngines also manage initializers and instance initializers.\n\nEngines can spawn `EngineInstance` instances via `buildInstance()`.",
       "extends": "Ember.Namespace",
       "uses": [
-        "RegistryProxy"
+        "RegistryProxyMixin"
       ],
       "access": "public",
       "tagname": ""
@@ -3670,8 +3660,8 @@
       "extension_for": [],
       "module": "@ember/engine",
       "namespace": "",
-      "file": "packages/@ember/engine/instance.js",
-      "line": 17,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 26,
       "description": "The `EngineInstance` encapsulates all of the stateful aspects of a\nrunning `Engine`.",
       "access": "public",
       "tagname": "",
@@ -4494,7 +4484,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 95,
+      "line": 91,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4506,7 +4496,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 102,
+      "line": 98,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4517,7 +4507,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 108,
+      "line": 104,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4528,7 +4518,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 114,
+      "line": 110,
       "description": "Given a fullName return a corresponding instance.\n The default behavior is for lookup to return a singleton instance.\nThe singleton is scoped to the container, allowing multiple containers\nto all have their own locally scoped singletons.\n ```javascript\nlet registry = new Registry();\nlet container = registry.container();\n registry.register('api:twitter', Twitter);\n let twitter = container.lookup('api:twitter');\n twitter instanceof Twitter; // => true\n // by default the container will return singletons\nlet twitter2 = container.lookup('api:twitter');\ntwitter2 instanceof Twitter; // => true\n twitter === twitter2; //=> true\n```\n If singletons are not wanted, an optional flag can be provided at lookup.\n ```javascript\nlet registry = new Registry();\nlet container = registry.container();\n registry.register('api:twitter', Twitter);\n let twitter = container.lookup('api:twitter', { singleton: false });\nlet twitter2 = container.lookup('api:twitter', { singleton: false });\n twitter === twitter2; //=> false\n```",
       "access": "private",
       "tagname": "",
@@ -4543,16 +4533,8 @@
         {
           "name": "options",
           "description": "",
-          "type": "Object",
-          "optional": true,
-          "props": [
-            {
-              "name": "source",
-              "description": "The fullname of the request source (used for local lookup)",
-              "type": "String",
-              "optional": true
-            }
-          ]
+          "type": "TypeOptions",
+          "optional": true
         }
       ],
       "return": {
@@ -4564,7 +4546,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 154,
+      "line": 149,
       "description": "A depth first traversal, destroying the container, its descendant containers and all\ntheir managed objects.",
       "access": "private",
       "tagname": "",
@@ -4575,7 +4557,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 171,
+      "line": 166,
       "description": "Clear either the entire cache or just the cache for a particular key.",
       "access": "private",
       "tagname": "",
@@ -4593,7 +4575,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 188,
+      "line": 183,
       "description": "Returns an object that can be used to provide an owner to a\nmanually created instance.",
       "access": "private",
       "tagname": "",
@@ -4608,7 +4590,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/container.ts",
-      "line": 201,
+      "line": 196,
       "description": "Given a fullName, return the corresponding factory. The consumer of the factory\nis responsible for the destruction of any factory instances, as there is no\nway for the container to ensure instances are destroyed when it itself is\ndestroyed.",
       "access": "public",
       "tagname": "",
@@ -4630,7 +4612,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 100,
+      "line": 95,
       "description": "A backup registry for resolving registrations when no matches can be found.",
       "access": "private",
       "tagname": "",
@@ -4642,7 +4624,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 108,
+      "line": 103,
       "description": "An object that has a `resolve` method that resolves a name.",
       "access": "private",
       "tagname": "",
@@ -4654,7 +4636,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 116,
+      "line": 111,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4665,7 +4647,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 122,
+      "line": 117,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4676,7 +4658,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 129,
+      "line": 124,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4687,7 +4669,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 136,
+      "line": 131,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4698,7 +4680,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 143,
+      "line": 138,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4709,7 +4691,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 150,
+      "line": 145,
       "description": "Creates a container based on this registry.",
       "access": "private",
       "tagname": "",
@@ -4731,7 +4713,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 162,
+      "line": 157,
       "description": "Registers a factory for later injection.\n\nExample:\n\n```javascript\nlet registry = new Registry();\n\nregistry.register('model:user', Person, {singleton: false });\nregistry.register('fruit:favorite', Orange);\nregistry.register('communication:main', Email, {singleton: false});\n```",
       "access": "private",
       "tagname": "",
@@ -4759,7 +4741,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 198,
+      "line": 194,
       "description": "Unregister a fullName\n\n```javascript\nlet registry = new Registry();\nregistry.register('model:user', User);\n\nregistry.resolve('model:user').create() instanceof User //=> true\n\nregistry.unregister('model:user')\nregistry.resolve('model:user') === undefined //=> true\n```",
       "access": "private",
       "tagname": "",
@@ -4777,7 +4759,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 228,
+      "line": 222,
       "description": "Given a fullName return the corresponding factory.\n\nBy default `resolve` will retrieve the factory from\nthe registry.\n\n```javascript\nlet registry = new Registry();\nregistry.register('api:twitter', Twitter);\n\nregistry.resolve('api:twitter') // => Twitter\n```\n\nOptionally the registry can be provided with a custom resolver.\nIf provided, `resolve` will first provide the custom resolver\nthe opportunity to resolve the fullName, otherwise it will fallback\nto the registry.\n\n```javascript\nlet registry = new Registry();\nregistry.resolver = function(fullName) {\n   // lookup via the module system of choice\n };\n\n// the twitter factory is added to the module system\nregistry.resolve('api:twitter') // => Twitter\n```",
       "access": "private",
       "tagname": "",
@@ -4788,20 +4770,6 @@
           "name": "fullName",
           "description": "",
           "type": "String"
-        },
-        {
-          "name": "options",
-          "description": "",
-          "type": "Object",
-          "optional": true,
-          "props": [
-            {
-              "name": "source",
-              "description": "the fullname of the request source (used for local lookups)",
-              "type": "String",
-              "optional": true
-            }
-          ]
         }
       ],
       "return": {
@@ -4813,7 +4781,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 271,
+      "line": 263,
       "description": "A hook that can be used to describe how the resolver will\nattempt to find the factory.\n\nFor example, the default Ember `.describe` returns the full\nclass name (including namespace) where Ember's resolver expects\nto find the `fullName`.",
       "access": "private",
       "tagname": "",
@@ -4835,7 +4803,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 294,
+      "line": 286,
       "description": "A hook to enable custom fullName normalization behavior",
       "access": "private",
       "tagname": "",
@@ -4857,7 +4825,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 312,
+      "line": 304,
       "description": "Normalize a fullName based on the application's conventions",
       "access": "private",
       "tagname": "",
@@ -4879,7 +4847,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 327,
+      "line": 319,
       "itemtype": "method",
       "name": "makeToString",
       "access": "private",
@@ -4905,7 +4873,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 345,
+      "line": 337,
       "description": "Given a fullName check if the container is aware of its factory\nor singleton instance.",
       "access": "private",
       "tagname": "",
@@ -4941,7 +4909,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 364,
+      "line": 356,
       "description": "Allow registering options for all factories of a type.\n\n```javascript\nlet registry = new Registry();\nlet container = registry.container();\n\n// if all of type `connection` must not be singletons\nregistry.optionsForType('connection', { singleton: false });\n\nregistry.register('connection:twitter', TwitterConnection);\nregistry.register('connection:facebook', FacebookConnection);\n\nlet twitter = container.lookup('connection:twitter');\nlet twitter2 = container.lookup('connection:twitter');\n\ntwitter === twitter2; // => false\n\nlet facebook = container.lookup('connection:facebook');\nlet facebook2 = container.lookup('connection:facebook');\n\nfacebook === facebook2; // => false\n```",
       "access": "private",
       "tagname": "",
@@ -4964,7 +4932,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 405,
+      "line": 397,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -4986,14 +4954,14 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 448,
+      "line": 440,
       "description": "This is deprecated in favor of explicit injection of dependencies.\n\nReference: https://deprecations.emberjs.com/v3.x#toc_implicit-injections\n```\n\n@private\n@method injection\n@param {String} factoryName\n@param {String} property\n@param {String} injectionName\n@deprecated",
       "class": "Registry",
       "module": "rsvp"
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 478,
+      "line": 470,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -6180,13 +6148,13 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 107,
+      "line": 109,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 115,
+      "line": 117,
       "class": "Component",
       "module": "@ember/template"
     },
@@ -6432,7 +6400,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 89,
+      "line": 90,
       "description": "Override this function when writing a class-based helper.",
       "itemtype": "method",
       "name": "compute",
@@ -6456,7 +6424,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 109,
+      "line": 112,
       "description": "On a class-based helper, it may be useful to force a recomputation of that\nhelpers value. This is akin to `rerender` on a component.\n\nFor example, this component will rerender when the `currentUser` on a\nsession service changes:\n\n```app/helpers/current-user-email.js\nimport Helper from '@ember/component/helper'\nimport { service } from '@ember/service'\nimport { observer } from '@ember/object'\n\nexport default Helper.extend({\n  session: service(),\n\n  onNewUser: observer('session.currentUser', function() {\n    this.recompute();\n  }),\n\n  compute() {\n    return this.get('session.currentUser.email');\n  }\n});\n```",
       "itemtype": "method",
       "name": "recompute",
@@ -6468,7 +6436,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 247,
+      "line": 264,
       "description": "In many cases it is not necessary to use the full `Helper` class.\nThe `helper` method create pure-function helpers without instances.\nFor example:\n\n```app/helpers/format-currency.js\nimport { helper } from '@ember/component/helper';\n\nexport default helper(function([cents], {currency}) {\n  return `${currency}${cents * 0.01}`;\n});\n```",
       "static": 1,
       "params": [
@@ -7898,7 +7866,7 @@
     },
     {
       "file": "packages/@ember/-internals/owner/index.ts",
-      "line": 44,
+      "line": 31,
       "description": "Framework objects in an Ember application (components, services, routes, etc.)\nare created via a factory and dependency injection system. Each of these\nobjects is the responsibility of an \"owner\", which handled its\ninstantiation and manages its lifetime.\n\n`getOwner` fetches the owner object responsible for an instance. This can\nbe used to lookup or resolve other class instances, or register new factories\ninto the owner.\n\nFor example, this component dynamically looks up a service based on the\n`audioType` passed as an argument:\n\n```app/components/play-audio.js\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\nimport { getOwner } from '@ember/application';\n\n// Usage:\n//\n//   <PlayAudio @audioType={{@model.audioType}} @audioFile={{@model.file}}/>\n//\nexport default class extends Component {\n  get audioService() {\n    let owner = getOwner(this);\n    return owner.lookup(`service:${this.args.audioType}`);\n  }\n\n  @action\n  onPlay() {\n    let player = this.audioService;\n    player.play(this.args.audioFile);\n  }\n}\n```",
       "itemtype": "method",
       "name": "getOwner",
@@ -7922,7 +7890,7 @@
     },
     {
       "file": "packages/@ember/-internals/owner/index.ts",
-      "line": 92,
+      "line": 79,
       "description": "`setOwner` forces a new owner on a given object instance. This is primarily\nuseful in some testing cases.",
       "itemtype": "method",
       "name": "setOwner",
@@ -10289,7 +10257,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 549,
+      "line": 553,
       "description": "Initializes the current router instance and sets up the change handling\nevent listeners used by the instances `location` implementation.\n\nA property named `initialURL` will be used to determine the initial URL.\nIf no value is found `/` will be used.",
       "itemtype": "method",
       "name": "startRouting",
@@ -10300,7 +10268,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 672,
+      "line": 676,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:",
       "itemtype": "method",
       "name": "transitionTo",
@@ -10334,7 +10302,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 717,
+      "line": 721,
       "description": "Similar to `transitionTo`, but instead of adding the destination to the browser's URL history,\nit replaces the entry for the current route.\nWhen the user clicks the \"back\" button in the browser, there will be fewer steps.\nThis is most commonly used to manage redirects in a way that does not cause confusing additions\nto the user's browsing history.",
       "itemtype": "method",
       "name": "replaceWith",
@@ -10368,7 +10336,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 744,
+      "line": 748,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -10389,7 +10357,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 756,
+      "line": 760,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -10419,7 +10387,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 778,
+      "line": 782,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -10434,7 +10402,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 789,
+      "line": 793,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -10445,7 +10413,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 937,
+      "line": 941,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10472,7 +10440,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 967,
+      "line": 971,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -10495,7 +10463,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 985,
+      "line": 989,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10522,7 +10490,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1013,
+      "line": 1017,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -10545,7 +10513,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1034,
+      "line": 1038,
       "description": "Removes (prunes) any query params with default values from the given QP\nobject. Default values are determined from the QP meta information per key.",
       "access": "private",
       "tagname": "",
@@ -10572,7 +10540,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1115,
+      "line": 1119,
       "description": "Prepares the query params for a URL or Transition. Restores any undefined QP\nkeys/values, serializes all values, and then prunes any default values.",
       "access": "private",
       "tagname": "",
@@ -10609,7 +10577,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1142,
+      "line": 1146,
       "description": "Returns the meta information for the query params of a given route. This\nwill be overridden to allow support for lazy routes.",
       "access": "private",
       "tagname": "",
@@ -10631,7 +10599,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1156,
+      "line": 1160,
       "description": "Returns a merged query params meta object for a given set of routeInfos.\nUseful for knowing what query params are available for a given route hierarchy.",
       "access": "private",
       "tagname": "",
@@ -10653,7 +10621,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1218,
+      "line": 1222,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -10685,7 +10653,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1256,
+      "line": 1260,
       "description": "Hydrates (adds/restores) any query params that have pre-existing values into\nthe given queryParams hash. This is what allows query params to be \"sticky\"\nand restore their last known values for their scope.",
       "access": "private",
       "tagname": "",
@@ -10712,7 +10680,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1427,
+      "line": 1431,
       "description": "Handles updating the paths and notifying any listeners of the URL\nchange.\n\nTriggers the router level `didTransition` hook.\n\nFor example, to notify google analytics when the route changes,\nyou could use this hook.  (Note: requires also including GA scripts, etc.)\n\n```javascript\nimport config from './config/environment';\nimport EmberRouter from '@ember/routing/router';\nimport { service } from '@ember/service';\n\nlet Router = EmberRouter.extend({\n  location: config.locationType,\n\n  router: service(),\n\n  didTransition: function() {\n    this._super(...arguments);\n\n    ga('send', 'pageview', {\n      page: this.router.currentURL,\n      title: this.router.currentRouteName,\n    });\n  }\n});\n```",
       "itemtype": "method",
       "name": "didTransition",
@@ -10724,7 +10692,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1464,
+      "line": 1468,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
@@ -10736,7 +10704,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1477,
+      "line": 1481,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -10748,7 +10716,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1635,
+      "line": 1639,
       "description": "Finds the name of the substate route if it exists for the given route. A\nsubstate route is of the form `route_state`, such as `foo_loading`.",
       "access": "private",
       "tagname": "",
@@ -10773,7 +10741,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1656,
+      "line": 1660,
       "description": "Finds the name of the state route if it exists for the given route. A state\nroute is of the form `route.state`, such as `foo.loading`. Properly Handles\n`application` named routes.",
       "access": "private",
       "tagname": "",
@@ -10798,7 +10766,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1678,
+      "line": 1682,
       "description": "Determines whether or not a route has been defined by checking that the route\nis in the Router's map and the owner has a registration for that route.",
       "access": "private",
       "tagname": "",
@@ -12344,7 +12312,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.d.ts",
-      "line": 7,
+      "line": 13,
       "class": "ContainerProxyMixin",
       "module": "ember",
       "namespace": "Ember"
@@ -13189,7 +13157,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/registry_proxy.d.ts",
-      "line": 7,
+      "line": 30,
       "class": "RegistryProxyMixin",
       "module": "@ember/object"
     },
@@ -14395,7 +14363,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts",
-      "line": 8,
+      "line": 9,
       "class": "Ember.EventDispatcher",
       "module": "ember"
     },
@@ -14673,7 +14641,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 39,
+      "line": 35,
       "description": "If the view is currently inserted into the DOM of a parent view, this\nproperty will point to the parent of the view.",
       "itemtype": "property",
       "name": "parentView",
@@ -14687,7 +14655,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 78,
+      "line": 74,
       "description": "Override the default event firing from `Evented` to\nalso call methods with the given name.",
       "itemtype": "method",
       "name": "trigger",
@@ -14705,15 +14673,31 @@
       "namespace": "Ember"
     },
     {
-      "file": "packages/@ember/application/lib/application.d.ts",
-      "line": 17,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 185,
+      "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
+      "itemtype": "method",
+      "name": "buildRegistry",
+      "static": 1,
+      "params": [
+        {
+          "name": "namespace",
+          "description": "the application for which to\n  build the registry",
+          "type": "Application"
+        }
+      ],
+      "return": {
+        "description": "the built registry",
+        "type": "Ember.Registry"
+      },
+      "access": "private",
+      "tagname": "",
       "class": "Application",
-      "module": "ember",
-      "namespace": "Ember"
+      "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 185,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 220,
       "description": "The root DOM element of the Application. This can be specified as an\nelement or a [selector string](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Selectors#reference_table_of_selectors).\n\nThis is the element that will be passed to the Application's,\n`eventDispatcher`, which sets up the listeners for event delegation. Every\nview in your application should be a child of the element you specify here.",
       "itemtype": "property",
       "name": "rootElement",
@@ -14725,8 +14709,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 200,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 235,
       "itemtype": "property",
       "name": "_document",
       "type": "Document | null",
@@ -14737,8 +14721,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 209,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 244,
       "description": "The `Ember.EventDispatcher` responsible for delegating events to this\napplication's views.\n\nThe event dispatcher is created by the application at initialization time\nand sets up event listeners on the DOM element described by the\napplication's `rootElement` property.\n\nSee the documentation for `Ember.EventDispatcher` for more information.",
       "itemtype": "property",
       "name": "eventDispatcher",
@@ -14750,8 +14734,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 226,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 261,
       "description": "The DOM events for which the event dispatcher should listen.\n\nBy default, the application's `Ember.EventDispatcher` listens\nfor a set of standard DOM events, such as `mousedown` and\n`keyup`, and delegates them to your application's `Ember.View`\ninstances.\n\nIf you would like additional bubbling events to be delegated to your\nviews, set your `Application`'s `customEvents` property\nto a hash containing the DOM event name as the key and the\ncorresponding view method name as the value. Setting an event to\na value of `null` will prevent a default event listener from being\nadded for that event.\n\nTo add new events to be listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // add support for the paste event\n    paste: 'paste'\n  }\n});\n```\n\nTo prevent default events from being listened to:\n\n```app/app.js\nimport Application from '@ember/application';\n\nlet App = Application.extend({\n  customEvents: {\n    // remove support for mouseenter / mouseleave events\n    mouseenter: null,\n    mouseleave: null\n  }\n});\n```",
       "itemtype": "property",
       "name": "customEvents",
@@ -14763,8 +14747,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 274,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 309,
       "description": "Whether the application should automatically start routing and render\ntemplates to the `rootElement` on DOM ready. While default by true,\nother environments such as FastBoot or a testing harness can set this\nproperty to `false` and control the precise timing and behavior of the boot\nprocess.",
       "itemtype": "property",
       "name": "autoboot",
@@ -14776,8 +14760,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 288,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 323,
       "description": "Whether the application should be configured for the legacy \"globals mode\".\nUnder this mode, the Application object serves as a global namespace for all\nclasses.\n\n```javascript\nimport Application from '@ember/application';\nimport Component from '@ember/component';\n\nlet App = Application.create({\n  ...\n});\n\nApp.Router.reopen({\n  location: 'none'\n});\n\nApp.Router.map({\n  ...\n});\n\nApp.MyComponent = Component.extend({\n  ...\n});\n```\n\nThis flag also exposes other internal APIs that assumes the existence of\na special \"default instance\", like `App.__container__.lookup(...)`.\n\nThis option is currently not configurable, its value is derived from\nthe `autoboot` flag – disabling `autoboot` also implies opting-out of\nglobals mode support, although they are ultimately orthogonal concerns.\n\nSome of the global modes features are already deprecated in 1.x. The\nexistence of this flag is to untangle the globals mode code paths from\nthe autoboot code paths, so that these legacy features can be reviewed\nfor deprecation/removal separately.\n\nForcing the (autoboot=true, _globalsMode=false) here and running the tests\nwould reveal all the places where we are still relying on these legacy\nbehavior internally (mostly just tests).",
       "itemtype": "property",
       "name": "_globalsMode",
@@ -14789,21 +14773,20 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 337,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 372,
       "description": "An array of application instances created by `buildInstance()`. Used\ninternally to ensure that all instances get destroyed.",
       "itemtype": "property",
       "name": "_applicationInstances",
       "type": "Array",
-      "default": "null",
       "access": "private",
       "tagname": "",
       "class": "Application",
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 376,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 422,
       "description": "Create an ApplicationInstance for this application.",
       "access": "public",
       "tagname": "",
@@ -14817,8 +14800,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 399,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 447,
       "description": "Start tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is created.",
       "access": "private",
       "tagname": "",
@@ -14828,8 +14811,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 410,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 458,
       "description": "Stop tracking an ApplicationInstance for this application.\nUsed when the ApplicationInstance is about to be destroyed.",
       "access": "private",
       "tagname": "",
@@ -14839,8 +14822,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 421,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 471,
       "description": "Enable the legacy globals mode by allowing this application to act\nas a global namespace. See the docs on the `_globalsMode` property\nfor details.\n\nMost of these features are already deprecated in 1.x, so we can\nstop using them internally and try to remove them.",
       "access": "private",
       "tagname": "",
@@ -14850,8 +14833,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 465,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 518,
       "description": "Automatically kick-off the boot process for the application once the\nDOM has become ready.\n\nThe initialization itself is scheduled on the actions queue which\nensures that code-loading finishes before booting.\n\nIf you are asynchronously loading code, you should call `deferReadiness()`\nto defer booting, and then call `advanceReadiness()` once all of your code\nhas finished loading.",
       "access": "private",
       "tagname": "",
@@ -14861,8 +14844,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 492,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 547,
       "description": "This is the autoboot flow:\n\n1. Boot the app by calling `this.boot()`\n2. Create an instance (or use the `__deprecatedInstance__` in globals mode)\n3. Boot the instance by calling `instance.boot()`\n4. Invoke the `App.ready()` callback\n5. Kick-off routing on the instance\n\nIdeally, this is all we would need to do:\n\n```javascript\n_autoBoot() {\n  this.boot().then(() => {\n    let instance = (this._globalsMode) ? this.__deprecatedInstance__ : this.buildInstance();\n    return instance.boot();\n  }).then((instance) => {\n    App.ready();\n    instance.startRouting();\n  });\n}\n```\n\nUnfortunately, we cannot actually write this because we need to participate\nin the \"synchronous\" boot process. While the code above would work fine on\nthe initial boot (i.e. DOM ready), when `App.reset()` is called, we need to\nboot a new instance synchronously (see the documentation on `_bootSync()`\nfor details).\n\nBecause of this restriction, the actual logic of this method is located\ninside `didBecomeReady()`.",
       "access": "private",
       "tagname": "",
@@ -14872,8 +14855,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 537,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 592,
       "description": "Use this to defer readiness until some condition is true.\n\nExample:\n\n```javascript\nimport Application from '@ember/application';\n\nlet App = Application.create();\n\nApp.deferReadiness();\n\nfetch('/auth-token')\n.then(response => response.json())\n.then(data => {\n  App.token = data.token;\n  App.advanceReadiness();\n});\n```\n\nThis allows you to perform asynchronous setup logic and defer\nbooting your application until the setup has finished.\n\nHowever, if the setup requires a loading UI, it might be better\nto use the router for this purpose.",
       "itemtype": "method",
       "name": "deferReadiness",
@@ -14883,8 +14866,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 587,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 642,
       "description": "Call `advanceReadiness` after any asynchronous setup logic has completed.\nEach call to `deferReadiness` must be matched by a call to `advanceReadiness`\nor the application will never become ready and routing will not begin.",
       "itemtype": "method",
       "name": "advanceReadiness",
@@ -14897,8 +14880,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 624,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 681,
       "description": "Initialize the application and return a promise that resolves with the `Application`\nobject when the boot process is complete.\n\nRun any application initializers and run the application load hook. These hooks may\nchoose to defer readiness. For example, an authentication hook might want to defer\nreadiness until the auth token has been retrieved.\n\nBy default, this method is called automatically on \"DOM ready\"; however, if autoboot\nis disabled, this is automatically called when the first application instance is\ncreated via `visit`.",
       "access": "public",
       "tagname": "",
@@ -14912,8 +14895,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 662,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 723,
       "description": "Unfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
       "access": "private",
       "tagname": "",
@@ -14921,8 +14904,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 701,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 762,
       "description": "Reset the application. This is typically used only in tests. It cleans up\nthe application in the following order:\n\n1. Deactivate existing routes\n2. Destroy all objects in the container\n3. Create a new application container\n4. Re-route to the existing url\n\nTypical Example:\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    App.reset();\n  }\n});\n\ntest('first test', function() {\n  // App is freshly reset\n});\n\ntest('second test', function() {\n  // App is again freshly reset\n});\n```\n\nAdvanced Example:\n\nOccasionally you may want to prevent the app from initializing during\nsetup. This could enable extra configuration, or enable asserting prior\nto the app becoming ready.\n\n```javascript\nimport Application from '@ember/application';\nlet App;\n\nrun(function() {\n  App = Application.create();\n});\n\nmodule('acceptance test', {\n  setup: function() {\n    run(function() {\n      App.reset();\n      App.deferReadiness();\n    });\n  }\n});\n\ntest('first test', function() {\n  ok(true, 'something before app is initialized');\n\n  run(function() {\n    App.advanceReadiness();\n  });\n\n  ok(true, 'something after app is initialized');\n});\n```",
       "itemtype": "method",
       "name": "reset",
@@ -14932,8 +14915,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 804,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 866,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14942,8 +14925,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 854,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 919,
       "description": "Called when the Application has become ready, immediately before routing\nbegins. The call will be delayed until the DOM has become ready.",
       "itemtype": "event",
       "name": "ready",
@@ -14953,8 +14936,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 879,
+      "file": "packages/@ember/application/lib/application.ts",
+      "line": 944,
       "description": "Boot a new instance of `ApplicationInstance` for the current\napplication and navigate it to the given `url`. Returns a `Promise` that\nresolves with the instance when the initial routing and rendering is\ncomplete, or rejects with any error that occurred during the boot process.\n\nWhen `autoboot` is disabled, calling `visit` would first cause the\napplication to boot, which runs the application initializers.\n\nThis method also takes a hash of boot-time configuration options for\ncustomizing the instance's behavior. See the documentation on\n`ApplicationInstance.BootOptions` for details.\n\n`ApplicationInstance.BootOptions` is an interface class that exists\npurely to document the available options; you do not need to construct it\nmanually. Simply pass a regular JavaScript object containing of the\ndesired options:\n\n```javascript\nMyApp.visit(\"/\", { location: \"none\", rootElement: \"#container\" });\n```\n\n### Supported Scenarios\n\nWhile the `BootOptions` class exposes a large number of knobs, not all\ncombinations of them are valid; certain incompatible combinations might\nresult in unexpected behavior.\n\nFor example, booting the instance in the full browser environment\nwhile specifying a foreign `document` object (e.g. `{ isBrowser: true,\ndocument: iframe.contentDocument }`) does not work correctly today,\nlargely due to Ember's jQuery dependency.\n\nCurrently, there are three officially supported scenarios/configurations.\nUsages outside of these scenarios are not guaranteed to work, but please\nfeel free to file bug reports documenting your experience and any issues\nyou encountered to help expand support.\n\n#### Browser Applications (Manual Boot)\n\nThe setup is largely similar to how Ember works out-of-the-box. Normally,\nEmber will boot a default instance for your Application on \"DOM ready\".\nHowever, you can customize this behavior by disabling `autoboot`.\n\nFor example, this allows you to render a miniture demo of your application\ninto a specific area on your marketing website:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let options = {\n    // Override the router's location adapter to prevent it from updating\n    // the URL in the address bar\n    location: 'none',\n\n    // Override the default `rootElement` on the app to render into a\n    // specific `div` on the page\n    rootElement: '#demo'\n  };\n\n  // Start the app at the special demo URL\n  App.visit('/demo', options);\n});\n```\n\nOr perhaps you might want to boot two instances of your app on the same\npage for a split-screen multiplayer experience:\n\n```javascript\nimport MyApp from 'my-app';\n\n$(function() {\n  let App = MyApp.create({ autoboot: false });\n\n  let sessionId = MyApp.generateSessionID();\n\n  let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' });\n  let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' });\n\n  Promise.all([player1, player2]).then(() => {\n    // Both apps have completed the initial render\n    $('#loading').fadeOut();\n  });\n});\n```\n\nDo note that each app instance maintains their own registry/container, so\nthey will run in complete isolation by default.\n\n#### Server-Side Rendering (also known as FastBoot)\n\nThis setup allows you to run your Ember app in a server environment using\nNode.js and render its content into static HTML for SEO purposes.\n\n```javascript\nconst HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap);\n\nfunction renderURL(url) {\n  let dom = new SimpleDOM.Document();\n  let rootElement = dom.body;\n  let options = { isBrowser: false, document: dom, rootElement: rootElement };\n\n  return MyApp.visit(options).then(instance => {\n    try {\n      return HTMLSerializer.serialize(rootElement.firstChild);\n    } finally {\n      instance.destroy();\n    }\n  });\n}\n```\n\nIn this scenario, because Ember does not have access to a global `document`\nobject in the Node.js environment, you must provide one explicitly. In practice,\nin the non-browser environment, the stand-in `document` object only needs to\nimplement a limited subset of the full DOM API. The `SimpleDOM` library is known\nto work.\n\nSince there is no DOM access in the non-browser environment, you must also\nspecify a DOM `Element` object in the same `document` for the `rootElement` option\n(as opposed to a selector string like `\"body\"`).\n\nSee the documentation on the `isBrowser`, `document` and `rootElement` properties\non `ApplicationInstance.BootOptions` for details.\n\n#### Server-Side Resource Discovery\n\nThis setup allows you to run the routing layer of your Ember app in a server\nenvironment using Node.js and completely disable rendering. This allows you\nto simulate and discover the resources (i.e. AJAX requests) needed to fulfill\na given request and eagerly \"push\" these resources to the client.\n\n```app/initializers/network-service.js\nimport BrowserNetworkService from 'app/services/network/browser';\nimport NodeNetworkService from 'app/services/network/node';\n\n// Inject a (hypothetical) service for abstracting all AJAX calls and use\n// the appropriate implementation on the client/server. This also allows the\n// server to log all the AJAX calls made during a particular request and use\n// that for resource-discovery purpose.\n\nexport function initialize(application) {\n  if (window) { // browser\n    application.register('service:network', BrowserNetworkService);\n  } else { // node\n    application.register('service:network', NodeNetworkService);\n  }\n};\n\nexport default {\n  name: 'network-service',\n  initialize: initialize\n};\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\n// An example of how the (hypothetical) service is used in routes.\n\nexport default class IndexRoute extends Route {\n  @service network;\n\n  model(params) {\n    return this.network.fetch(`/api/posts/${params.post_id}.json`);\n  }\n\n  afterModel(post) {\n    if (post.isExternalContent) {\n      return this.network.fetch(`/api/external/?url=${post.externalURL}`);\n    } else {\n      return post;\n    }\n  }\n}\n```\n\n```javascript\n// Finally, put all the pieces together\n\nfunction discoverResourcesFor(url) {\n  return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => {\n    let networkService = instance.lookup('service:network');\n    return networkService.requests; // => { \"/api/posts/123.json\": \"...\" }\n  });\n}\n```",
       "access": "public",
       "tagname": "",
@@ -14980,30 +14963,7 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/application.js",
-      "line": 1100,
-      "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
-      "itemtype": "method",
-      "name": "buildRegistry",
-      "static": 1,
-      "params": [
-        {
-          "name": "namespace",
-          "description": "the application for which to\n  build the registry",
-          "type": "Application"
-        }
-      ],
-      "return": {
-        "description": "the built registry",
-        "type": "Ember.Registry"
-      },
-      "access": "private",
-      "tagname": "",
-      "class": "Application",
-      "module": "@ember/application"
-    },
-    {
-      "file": "packages/@ember/application/lib/lazy_load.js",
+      "file": "packages/@ember/application/lib/lazy_load.ts",
       "line": 14,
       "description": "Detects when a specific package of Ember (e.g. 'Application')\nhas fully loaded and is available for extension.\n\nThe provided `callback` will be called with the `name` passed\nresolved from a string into the object:\n\n``` javascript\nimport { onLoad } from '@ember/application';\n\nonLoad('Ember.Application' function(hbars) {\n  hbars.registerHelper(...);\n});\n```",
       "itemtype": "method",
@@ -15027,7 +14987,7 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/lib/lazy_load.js",
+      "file": "packages/@ember/application/lib/lazy_load.ts",
       "line": 47,
       "description": "Called when an Ember.js package (e.g Application) has finished\nloading. Triggers any callbacks registered for this event.",
       "itemtype": "method",
@@ -15051,8 +15011,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 36,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 53,
       "description": "The `Application` for which this is an instance.",
       "itemtype": "property",
       "name": "application",
@@ -15063,20 +15023,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 44,
-      "description": "The DOM events for which the event dispatcher should listen.\n\nBy default, the application's `Ember.EventDispatcher` listens\nfor a set of standard DOM events, such as `mousedown` and\n`keyup`, and delegates them to your application's `Ember.View`\ninstances.",
-      "access": "private",
-      "tagname": "",
-      "itemtype": "property",
-      "name": "customEvents",
-      "type": "Object",
-      "class": "ApplicationInstance",
-      "module": "@ember/application"
-    },
-    {
-      "file": "packages/@ember/application/instance.js",
-      "line": 57,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 61,
       "description": "The root DOM element of the Application as an element or a\nCSS selector.",
       "access": "private",
       "tagname": "",
@@ -15087,8 +15035,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 81,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 85,
       "description": "Overrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
       "access": "private",
       "tagname": "",
@@ -15096,8 +15044,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 133,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 145,
       "description": "This hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
       "params": [
         {
@@ -15113,8 +15061,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 150,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 162,
       "description": "Tells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
       "access": "private",
       "tagname": "",
@@ -15122,8 +15070,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 161,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 173,
       "description": "Sets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
       "access": "public",
       "tagname": "",
@@ -15131,8 +15079,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 182,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 194,
       "description": "Directs the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
       "params": [
         {
@@ -15147,16 +15095,16 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 194,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 206,
       "access": "private",
       "tagname": "",
       "class": "ApplicationInstance",
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 208,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 222,
       "description": "Returns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
       "access": "public",
       "tagname": "",
@@ -15168,8 +15116,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 223,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 237,
       "description": "Navigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transion was aborted due to an error.",
       "access": "public",
       "tagname": "",
@@ -15188,8 +15136,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 283,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 296,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15210,8 +15158,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 329,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 339,
       "description": "Interactive mode: whether we need to set up event delegation and invoke\nlifecycle callbacks on Components.",
       "itemtype": "property",
       "name": "isInteractive",
@@ -15224,8 +15172,8 @@
       "namespace": "ApplicationInstance"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 340,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 350,
       "itemtype": "property",
       "name": "_renderMode",
       "type": "string",
@@ -15237,8 +15185,8 @@
       "namespace": "ApplicationInstance"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 348,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 358,
       "description": "Run in a full browser environment.\n\nWhen this flag is set to `false`, it will disable most browser-specific\nand interactive features. Specifically:\n\n* It does not use `jQuery` to append the root view; the `rootElement`\n  (either specified as a subsequent option or on the application itself)\n  must already be an `Element` in the given `document` (as opposed to a\n  string selector).\n\n* It does not set up an `EventDispatcher`.\n\n* It does not run any `Component` lifecycle hooks (such as `didInsertElement`).\n\n* It sets the `location` option to `\"none\"`. (If you would like to use\n  the location adapter specified in the app's router instead, you can also\n  specify `{ location: null }` to specifically opt-out.)",
       "itemtype": "property",
       "name": "isBrowser",
@@ -15251,8 +15199,22 @@
       "namespace": "ApplicationInstance"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 383,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 384,
+      "description": "If present, overrides the router's `location` property with this\nvalue. This is useful for environments where trying to modify the\nURL would be inappropriate.",
+      "itemtype": "property",
+      "name": "location",
+      "type": "string",
+      "default": "null",
+      "access": "public",
+      "tagname": "",
+      "class": "ApplicationInstance.BootOptions",
+      "module": "@ember/application",
+      "namespace": "ApplicationInstance"
+    },
+    {
+      "file": "packages/@ember/application/instance.ts",
+      "line": 396,
       "description": "Disable rendering completely.\n\nWhen this flag is set to `false`, it will disable the entire rendering\npipeline. Essentially, this puts the app into \"routing-only\" mode. No\ntemplates will be rendered, and no Components will be created.",
       "itemtype": "property",
       "name": "shouldRender",
@@ -15265,8 +15227,8 @@
       "namespace": "ApplicationInstance"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 405,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 410,
       "description": "If present, render into the given `Document` object instead of the\nglobal `window.document` object.\n\nIn practice, this is only useful in non-browser environment or in\nnon-interactive mode, because Ember's `jQuery` dependency is\nimplicitly bound to the current document, causing event delegation\nto not work properly when the app is rendered into a foreign\ndocument object (such as an iframe's `contentDocument`).\n\nIn non-browser mode, this could be a \"`Document`-like\" object as\nEmber only interact with a small subset of the DOM API in non-\ninteractive mode. While the exact requirements have not yet been\nformalized, the `SimpleDOM` library's implementation is known to\nwork.",
       "itemtype": "property",
       "name": "document",
@@ -15279,8 +15241,8 @@
       "namespace": "ApplicationInstance"
     },
     {
-      "file": "packages/@ember/application/instance.js",
-      "line": 432,
+      "file": "packages/@ember/application/instance.ts",
+      "line": 433,
       "description": "If present, overrides the application's `rootElement` property on\nthe instance. This is useful for testing environment, where you\nmight want to append the root view to a fixture area.\n\nIn non-browser mode, because Ember does not have access to jQuery,\nthis options must be specified as a DOM `Element` object instead of\na selector string.\n\nSee the documentation on `Application`'s `rootElement` for\ndetails.",
       "itemtype": "property",
       "name": "rootElement",
@@ -15292,20 +15254,6 @@
       "module": "@ember/application",
       "namespace": "ApplicationInstance"
     },
-    {
-      "file": "packages/@ember/application/instance.js",
-      "line": 457,
-      "description": "If present, overrides the router's `location` property with this\nvalue. This is useful for environments where trying to modify the\nURL would be inappropriate.",
-      "itemtype": "property",
-      "name": "location",
-      "type": "string",
-      "default": "null",
-      "access": "public",
-      "tagname": "",
-      "class": "ApplicationInstance.BootOptions",
-      "module": "@ember/application",
-      "namespace": "ApplicationInstance"
-    },
     {
       "file": "packages/@ember/canary-features/index.ts",
       "line": 31,
@@ -15878,8 +15826,77 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 53,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 61,
+      "description": "The goal of initializers should be to register dependencies and injections.\nThis phase runs once. Because these initializers may load code, they are\nallowed to defer application readiness and advance it. If you need to access\nthe container or store you should use an InstanceInitializer that will be run\nafter all initializers and therefore after all code is loaded and the app is\nready.\n\nInitializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the initializer is registered.\nThis must be a unique name, as trying to register two initializers with the\nsame name will result in an error.\n\n```app/initializer/named-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running namedInitializer!');\n}\n\nexport default {\n  name: 'named-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\nAn example of ordering initializers, we create an initializer named `first`:\n\n```app/initializer/first.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('First initializer!');\n}\n\nexport default {\n  name: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: First initializer!\n```\n\nWe add another initializer named `second`, specifying that it should run\nafter the initializer named `first`:\n\n```app/initializer/second.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Second initializer!');\n}\n\nexport default {\n  name: 'second',\n  after: 'first',\n  initialize\n};\n```\n\n```\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nAfterwards we add a further initializer named `pre`, this time specifying\nthat it should run before the initializer named `first`:\n\n```app/initializer/pre.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Pre initializer!');\n}\n\nexport default {\n  name: 'pre',\n  before: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nFinally we add an initializer named `post`, specifying it should run after\nboth the `first` and the `second` initializers:\n\n```app/initializer/post.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Post initializer!');\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n// DEBUG: Post initializer!\n```\n\n* `initialize` is a callback function that receives one argument,\n  `application`, on which you can operate.\n\nExample of using `application` to register an adapter:\n\n```app/initializer/api-adapter.js\nimport ApiAdapter from '../utils/api-adapter';\n\nexport function initialize(application) {\n  application.register('api-adapter:main', ApiAdapter);\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```",
+      "itemtype": "method",
+      "name": "initializer",
+      "params": [
+        {
+          "name": "initializer",
+          "description": "",
+          "type": "Object"
+        }
+      ],
+      "access": "public",
+      "tagname": "",
+      "class": "Engine",
+      "module": "@ember/engine"
+    },
+    {
+      "file": "packages/@ember/engine/index.ts",
+      "line": 208,
+      "description": "Instance initializers run after all initializers have run. Because\ninstance initializers run after the app is fully set up. We have access\nto the store, container, and other items. However, these initializers run\nafter code has loaded and are not allowed to defer readiness.\n\nInstance initializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the instanceInitializer is\nregistered. This must be a unique name, as trying to register two\ninstanceInitializer with the same name will result in an error.\n\n```app/initializer/named-instance-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running named-instance-initializer!');\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\n* See Application.initializer for discussion on the usage of before\nand after.\n\nExample instanceInitializer to preload data into the store.\n\n```app/initializer/preload-data.js\n\nexport function initialize(application) {\n    var userConfig, userConfigEncoded, store;\n    // We have a HTML escaped JSON representation of the user's basic\n    // configuration generated server side and stored in the DOM of the main\n    // index.html file. This allows the app to have access to a set of data\n    // without making any additional remote calls. Good for basic data that is\n    // needed for immediate rendering of the page. Keep in mind, this data,\n    // like all local models and data can be manipulated by the user, so it\n    // should not be relied upon for security or authorization.\n\n    // Grab the encoded data from the meta tag\n    userConfigEncoded = document.querySelector('head meta[name=app-user-config]').attr('content');\n\n    // Unescape the text, then parse the resulting JSON into a real object\n    userConfig = JSON.parse(unescape(userConfigEncoded));\n\n    // Lookup the store\n    store = application.lookup('service:store');\n\n    // Push the encoded JSON into the store\n    store.pushPayload(userConfig);\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```",
+      "itemtype": "method",
+      "name": "instanceInitializer",
+      "params": [
+        {
+          "name": "instanceInitializer",
+          "description": ""
+        }
+      ],
+      "access": "public",
+      "tagname": "",
+      "class": "Engine",
+      "module": "@ember/engine"
+    },
+    {
+      "file": "packages/@ember/engine/index.ts",
+      "line": 284,
+      "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
+      "itemtype": "method",
+      "name": "buildRegistry",
+      "static": 1,
+      "params": [
+        {
+          "name": "namespace",
+          "description": "the application for which to\n  build the registry",
+          "type": "Application"
+        }
+      ],
+      "return": {
+        "description": "the built registry",
+        "type": "Ember.Registry"
+      },
+      "access": "private",
+      "tagname": "",
+      "class": "Engine",
+      "module": "@ember/engine"
+    },
+    {
+      "file": "packages/@ember/engine/index.ts",
+      "line": 324,
+      "description": "Set this to provide an alternate class to `DefaultResolver`",
+      "itemtype": "property",
+      "name": "resolver",
+      "access": "public",
+      "tagname": "",
+      "class": "Engine",
+      "module": "@ember/engine"
+    },
+    {
+      "file": "packages/@ember/engine/index.ts",
+      "line": 337,
       "description": "A private flag indicating whether an engine's initializers have run yet.",
       "access": "private",
       "tagname": "",
@@ -15889,8 +15906,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 61,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 345,
       "description": "Ensure that initializers are run once, and only once, per engine.",
       "access": "private",
       "tagname": "",
@@ -15900,8 +15917,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 74,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 358,
       "description": "Create an EngineInstance for this engine.",
       "access": "public",
       "tagname": "",
@@ -15915,8 +15932,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 87,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 370,
       "description": "Build and configure the registry for the current engine.",
       "access": "private",
       "tagname": "",
@@ -15930,8 +15947,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 100,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 383,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15940,8 +15957,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 108,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 391,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15950,8 +15967,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 116,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 399,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -15960,8 +15977,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 127,
+      "file": "packages/@ember/engine/index.ts",
+      "line": 413,
       "access": "private",
       "tagname": "",
       "since": "1.12.0",
@@ -15971,99 +15988,52 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 158,
-      "description": "The goal of initializers should be to register dependencies and injections.\nThis phase runs once. Because these initializers may load code, they are\nallowed to defer application readiness and advance it. If you need to access\nthe container or store you should use an InstanceInitializer that will be run\nafter all initializers and therefore after all code is loaded and the app is\nready.\n\nInitializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the initializer is registered.\nThis must be a unique name, as trying to register two initializers with the\nsame name will result in an error.\n\n```app/initializer/named-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running namedInitializer!');\n}\n\nexport default {\n  name: 'named-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\nAn example of ordering initializers, we create an initializer named `first`:\n\n```app/initializer/first.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('First initializer!');\n}\n\nexport default {\n  name: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: First initializer!\n```\n\nWe add another initializer named `second`, specifying that it should run\nafter the initializer named `first`:\n\n```app/initializer/second.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Second initializer!');\n}\n\nexport default {\n  name: 'second',\n  after: 'first',\n  initialize\n};\n```\n\n```\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nAfterwards we add a further initializer named `pre`, this time specifying\nthat it should run before the initializer named `first`:\n\n```app/initializer/pre.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Pre initializer!');\n}\n\nexport default {\n  name: 'pre',\n  before: 'first',\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n```\n\nFinally we add an initializer named `post`, specifying it should run after\nboth the `first` and the `second` initializers:\n\n```app/initializer/post.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Post initializer!');\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```\n\n```bash\n// DEBUG: Pre initializer!\n// DEBUG: First initializer!\n// DEBUG: Second initializer!\n// DEBUG: Post initializer!\n```\n\n* `initialize` is a callback function that receives one argument,\n  `application`, on which you can operate.\n\nExample of using `application` to register an adapter:\n\n```app/initializer/api-adapter.js\nimport ApiAdapter from '../utils/api-adapter';\n\nexport function initialize(application) {\n  application.register('api-adapter:main', ApiAdapter);\n}\n\nexport default {\n  name: 'post',\n  after: ['first', 'second'],\n  initialize\n};\n```",
-      "itemtype": "method",
-      "name": "initializer",
-      "params": [
-        {
-          "name": "initializer",
-          "description": "",
-          "type": "Object"
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Engine",
-      "module": "@ember/engine"
-    },
-    {
-      "file": "packages/@ember/engine/index.js",
-      "line": 305,
-      "description": "Instance initializers run after all initializers have run. Because\ninstance initializers run after the app is fully set up. We have access\nto the store, container, and other items. However, these initializers run\nafter code has loaded and are not allowed to defer readiness.\n\nInstance initializer receives an object which has the following attributes:\n`name`, `before`, `after`, `initialize`. The only required attribute is\n`initialize`, all others are optional.\n\n* `name` allows you to specify under which name the instanceInitializer is\nregistered. This must be a unique name, as trying to register two\ninstanceInitializer with the same name will result in an error.\n\n```app/initializer/named-instance-initializer.js\nimport { debug } from '@ember/debug';\n\nexport function initialize() {\n  debug('Running named-instance-initializer!');\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```\n\n* `before` and `after` are used to ensure that this initializer is ran prior\nor after the one identified by the value. This value can be a single string\nor an array of strings, referencing the `name` of other initializers.\n\n* See Application.initializer for discussion on the usage of before\nand after.\n\nExample instanceInitializer to preload data into the store.\n\n```app/initializer/preload-data.js\n\nexport function initialize(application) {\n    var userConfig, userConfigEncoded, store;\n    // We have a HTML escaped JSON representation of the user's basic\n    // configuration generated server side and stored in the DOM of the main\n    // index.html file. This allows the app to have access to a set of data\n    // without making any additional remote calls. Good for basic data that is\n    // needed for immediate rendering of the page. Keep in mind, this data,\n    // like all local models and data can be manipulated by the user, so it\n    // should not be relied upon for security or authorization.\n\n    // Grab the encoded data from the meta tag\n    userConfigEncoded = document.querySelector('head meta[name=app-user-config]').attr('content');\n\n    // Unescape the text, then parse the resulting JSON into a real object\n    userConfig = JSON.parse(unescape(userConfigEncoded));\n\n    // Lookup the store\n    store = application.lookup('service:store');\n\n    // Push the encoded JSON into the store\n    store.pushPayload(userConfig);\n}\n\nexport default {\n  name: 'named-instance-initializer',\n  initialize\n};\n```",
-      "itemtype": "method",
-      "name": "instanceInitializer",
-      "params": [
-        {
-          "name": "instanceInitializer",
-          "description": ""
-        }
-      ],
-      "access": "public",
+      "file": "packages/@ember/engine/index.ts",
+      "line": 447,
+      "description": "This function defines the default lookup rules for container lookups:\n\n* templates are looked up on `Ember.TEMPLATES`\n* other names are looked up on the application after classifying the name.\n  For example, `controller:post` looks up `App.PostController` by default.\n* if the default lookup fails, look for registered classes on the container\n\nThis allows the application to register default injections in the container\nthat could be overridden by the normal naming convention.",
+      "access": "private",
       "tagname": "",
-      "class": "Engine",
-      "module": "@ember/engine"
-    },
-    {
-      "file": "packages/@ember/engine/index.js",
-      "line": 378,
-      "description": "This creates a registry with the default Ember naming conventions.\n\nIt also configures the registry:\n\n* registered views are created every time they are looked up (they are\n  not singletons)\n* registered templates are not factories; the registered value is\n  returned directly.\n* the router receives the application as its `namespace` property\n* all controllers receive the router as their `target` and `controllers`\n  properties\n* all controllers receive the application as their `namespace` property\n* the application view receives the application controller as its\n  `controller` property\n* the application view receives the application template as its\n  `defaultTemplate` property",
       "itemtype": "method",
-      "name": "buildRegistry",
-      "static": 1,
+      "name": "resolverFor",
       "params": [
         {
           "name": "namespace",
-          "description": "the application for which to\n  build the registry",
-          "type": "Application"
+          "description": "the namespace to look for classes",
+          "type": "Ember.Enginer"
         }
       ],
       "return": {
-        "description": "the built registry",
-        "type": "Ember.Registry"
+        "description": "the resolved value for a given lookup",
+        "type": "*"
       },
-      "access": "private",
-      "tagname": "",
-      "class": "Engine",
-      "module": "@ember/engine"
-    },
-    {
-      "file": "packages/@ember/engine/index.js",
-      "line": 418,
-      "description": "Set this to provide an alternate class to `DefaultResolver`",
-      "itemtype": "property",
-      "name": "resolver",
-      "access": "public",
-      "tagname": "",
       "class": "Engine",
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/index.js",
-      "line": 427,
-      "description": "This function defines the default lookup rules for container lookups:\n\n* templates are looked up on `Ember.TEMPLATES`\n* other names are looked up on the application after classifying the name.\n  For example, `controller:post` looks up `App.PostController` by default.\n* if the default lookup fails, look for registered classes on the container\n\nThis allows the application to register default injections in the container\nthat could be overridden by the normal naming convention.",
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 39,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
-      "name": "resolverFor",
+      "name": "setupRegistry",
       "params": [
         {
-          "name": "namespace",
-          "description": "the namespace to look for classes",
-          "type": "Ember.Namespace"
+          "name": "registry",
+          "description": "",
+          "type": "Registry"
+        },
+        {
+          "name": "options",
+          "description": "",
+          "type": "BootOptions"
         }
       ],
-      "return": {
-        "description": "the resolved value for a given lookup",
-        "type": "*"
-      },
-      "class": "Engine",
+      "class": "EngineInstance",
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 29,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 47,
       "description": "The base `Engine` for which this is an instance.",
       "itemtype": "property",
       "name": "engine",
@@ -16074,8 +16044,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 62,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 84,
       "description": "Initialize the `EngineInstance` and return a promise that resolves\nwith the instance itself when the boot process is complete.\n\nThe primary task here is to run any registered instance initializers.\n\nSee the documentation on `BootOptions` for the options it takes.",
       "access": "public",
       "tagname": "",
@@ -16096,8 +16066,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 85,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 109,
       "description": "Unfortunately, a lot of existing code assumes booting an instance is\nsynchronous – specifically, a lot of tests assume the last call to\n`app.advanceReadiness()` or `app.reset()` will result in a new instance\nbeing fully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this\nassumption, so we created the asynchronous version above that returns a\npromise. But until we have migrated all the code, we would have to expose\nthis method for use *internally* in places where we need to boot an instance\nsynchronously.",
       "access": "private",
       "tagname": "",
@@ -16105,8 +16075,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 124,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 150,
       "description": "Unregister a factory.\n\nOverrides `RegistryProxy#unregister` in order to clear any cached instances\nof the unregistered factory.",
       "access": "public",
       "tagname": "",
@@ -16123,8 +16093,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 139,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 167,
       "description": "Build a new `EngineInstance` that's a child of this instance.\n\nEngines must be registered by name with their parent engine\n(or application).",
       "access": "private",
       "tagname": "",
@@ -16150,8 +16120,8 @@
       "module": "@ember/engine"
     },
     {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 167,
+      "file": "packages/@ember/engine/instance.ts",
+      "line": 197,
       "description": "Clone dependencies shared between an engine instance and its parent.",
       "access": "private",
       "tagname": "",
@@ -16160,28 +16130,6 @@
       "class": "EngineInstance",
       "module": "@ember/engine"
     },
-    {
-      "file": "packages/@ember/engine/instance.js",
-      "line": 200,
-      "access": "private",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "setupRegistry",
-      "params": [
-        {
-          "name": "registry",
-          "description": "",
-          "type": "Registry"
-        },
-        {
-          "name": "options",
-          "description": "",
-          "type": "BootOptions"
-        }
-      ],
-      "class": "EngineInstance",
-      "module": "@ember/engine"
-    },
     {
       "file": "packages/@ember/helper/index.ts",
       "line": 5,
@@ -18464,7 +18412,7 @@
   "warnings": [
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/container/lib/container.ts:188"
+      "line": " packages/@ember/-internals/container/lib/container.ts:183"
     },
     {
       "message": "unknown tag: internal",
@@ -18516,7 +18464,7 @@
     },
     {
       "message": "Missing item type\nThis is deprecated in favor of explicit injection of dependencies.\n\nReference: https://deprecations.emberjs.com/v3.x#toc_implicit-injections\n```\n\n@private\n@method injection\n@param {String} factoryName\n@param {String} property\n@param {String} injectionName\n@deprecated",
-      "line": " packages/@ember/-internals/container/lib/registry.ts:448"
+      "line": " packages/@ember/-internals/container/lib/registry.ts:440"
     },
     {
       "message": "Missing item type\nThe `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
@@ -18580,11 +18528,11 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:107"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:109"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:115"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:117"
     },
     {
       "message": "Missing item type",
@@ -18844,19 +18792,19 @@
     },
     {
       "message": "Missing item type\nFinds the name of the substate route if it exists for the given route. A\nsubstate route is of the form `route_state`, such as `foo_loading`.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1635"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1639"
     },
     {
       "message": "Missing item type\nFinds the name of the state route if it exists for the given route. A state\nroute is of the form `route.state`, such as `foo.loading`. Properly Handles\n`application` named routes.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1656"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1660"
     },
     {
       "message": "Missing item type\nDetermines whether or not a route has been defined by checking that the route\nis in the Router's map and the owner has a registration for that route.",
-      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1678"
+      "line": " packages/@ember/-internals/routing/lib/system/router.ts:1682"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.d.ts:7"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.d.ts:13"
     },
     {
       "message": "Missing item type\nThis mixin allows for Ember objects to subscribe to and emit events.",
@@ -18932,7 +18880,7 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.d.ts:7"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.d.ts:30"
     },
     {
       "message": "Missing item type",
@@ -18952,47 +18900,43 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts:8"
-    },
-    {
-      "message": "Missing item type",
-      "line": " packages/@ember/application/lib/application.d.ts:17"
+      "line": " packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts:9"
     },
     {
       "message": "Missing item type\nUnfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
-      "line": " packages/@ember/application/lib/application.js:662"
+      "line": " packages/@ember/application/lib/application.ts:723"
     },
     {
       "message": "Missing item type\nOverrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
-      "line": " packages/@ember/application/instance.js:81"
+      "line": " packages/@ember/application/instance.ts:85"
     },
     {
       "message": "Missing item type\nThis hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
-      "line": " packages/@ember/application/instance.js:133"
+      "line": " packages/@ember/application/instance.ts:145"
     },
     {
       "message": "Missing item type\nTells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
-      "line": " packages/@ember/application/instance.js:150"
+      "line": " packages/@ember/application/instance.ts:162"
     },
     {
       "message": "Missing item type\nSets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
-      "line": " packages/@ember/application/instance.js:161"
+      "line": " packages/@ember/application/instance.ts:173"
     },
     {
       "message": "Missing item type\nDirects the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
-      "line": " packages/@ember/application/instance.js:182"
+      "line": " packages/@ember/application/instance.ts:194"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/application/instance.js:194"
+      "line": " packages/@ember/application/instance.ts:206"
     },
     {
       "message": "Missing item type\nReturns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
-      "line": " packages/@ember/application/instance.js:208"
+      "line": " packages/@ember/application/instance.ts:222"
     },
     {
       "message": "Missing item type\nNavigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transion was aborted due to an error.",
-      "line": " packages/@ember/application/instance.js:223"
+      "line": " packages/@ember/application/instance.ts:237"
     },
     {
       "message": "Missing item type",
@@ -19000,7 +18944,7 @@
     },
     {
       "message": "Missing item type\nUnfortunately, a lot of existing code assumes booting an instance is\nsynchronous – specifically, a lot of tests assume the last call to\n`app.advanceReadiness()` or `app.reset()` will result in a new instance\nbeing fully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this\nassumption, so we created the asynchronous version above that returns a\npromise. But until we have migrated all the code, we would have to expose\nthis method for use *internally* in places where we need to boot an instance\nsynchronously.",
-      "line": " packages/@ember/engine/instance.js:85"
+      "line": " packages/@ember/engine/instance.ts:109"
     },
     {
       "message": "Missing item type",