ember-source 4.4.0-alpha.2 → 4.4.0-alpha.5

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.2"
+    "version": "4.4.0-alpha.5"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -202,8 +202,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js": {
-      "name": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
+    "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts": {
+      "name": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
       "modules": {},
       "classes": {
         "ContainerDebugAdapter": 1
@@ -211,8 +211,8 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/extension-support/lib/data_adapter.js": {
-      "name": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
+    "packages/@ember/-internals/extension-support/lib/data_adapter.ts": {
+      "name": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
       "modules": {},
       "classes": {
         "DataAdapter": 1
@@ -414,6 +414,15 @@
       },
       "namespaces": {}
     },
+    "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts": {
+      "name": "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {
+        "Ember.Templates.helpers": 1
+      },
+      "namespaces": {}
+    },
     "packages/@ember/-internals/glimmer/lib/modifiers/on.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/modifiers/on.ts",
       "modules": {},
@@ -468,6 +477,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@ember/-internals/glimmer/lib/utils/managers.ts": {
+      "name": "packages/@ember/-internals/glimmer/lib/utils/managers.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@ember/-internals/glimmer/lib/utils/outlet.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
       "modules": {},
@@ -914,6 +930,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@ember/-internals/runtime/lib/mixins/-proxy.d.ts": {
+      "name": "packages/@ember/-internals/runtime/lib/mixins/-proxy.d.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@ember/-internals/runtime/lib/mixins/-proxy.js": {
       "name": "packages/@ember/-internals/runtime/lib/mixins/-proxy.js",
       "modules": {},
@@ -1127,8 +1150,8 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/runtime/lib/compare.js": {
-      "name": "packages/@ember/-internals/runtime/lib/compare.js",
+    "packages/@ember/-internals/runtime/lib/compare.ts": {
+      "name": "packages/@ember/-internals/runtime/lib/compare.ts",
       "modules": {},
       "classes": {},
       "fors": {
@@ -1136,8 +1159,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/-internals/runtime/lib/is-equal.js": {
-      "name": "packages/@ember/-internals/runtime/lib/is-equal.js",
+    "packages/@ember/-internals/runtime/lib/is-equal.ts": {
+      "name": "packages/@ember/-internals/runtime/lib/is-equal.ts",
       "modules": {},
       "classes": {},
       "fors": {
@@ -1145,8 +1168,8 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/-internals/runtime/lib/type-of.js": {
-      "name": "packages/@ember/-internals/runtime/lib/type-of.js",
+    "packages/@ember/-internals/runtime/lib/type-of.ts": {
+      "name": "packages/@ember/-internals/runtime/lib/type-of.ts",
       "modules": {},
       "classes": {},
       "fors": {
@@ -1270,6 +1293,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts": {
+      "name": "packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@ember/-internals/views/lib/system/event_dispatcher.js": {
       "name": "packages/@ember/-internals/views/lib/system/event_dispatcher.js",
       "modules": {},
@@ -1288,8 +1318,8 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/views/lib/views/core_view.js": {
-      "name": "packages/@ember/-internals/views/lib/views/core_view.js",
+    "packages/@ember/-internals/views/lib/views/core_view.ts": {
+      "name": "packages/@ember/-internals/views/lib/views/core_view.ts",
       "modules": {},
       "classes": {
         "Ember.CoreView": 1
@@ -1299,6 +1329,13 @@
         "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",
       "modules": {
@@ -1562,8 +1599,19 @@
       },
       "namespaces": {}
     },
-    "packages/@ember/runloop/index.js": {
-      "name": "packages/@ember/runloop/index.js",
+    "packages/@ember/renderer/index.ts": {
+      "name": "packages/@ember/renderer/index.ts",
+      "modules": {
+        "@ember/renderer": 1
+      },
+      "classes": {
+        "Renderer": 1
+      },
+      "fors": {},
+      "namespaces": {}
+    },
+    "packages/@ember/runloop/index.ts": {
+      "name": "packages/@ember/runloop/index.ts",
       "modules": {
         "@ember/runloop": 1
       },
@@ -1771,8 +1819,8 @@
       },
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 125,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 158,
       "access": "public",
       "tagname": ""
     },
@@ -1795,7 +1843,7 @@
       "namespaces": {},
       "tag": "main",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 37,
+      "line": 43,
       "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"
     },
@@ -1899,7 +1947,7 @@
       "tag": "module",
       "file": "packages/@ember/-internals/glimmer/lib/glimmer-component-docs.ts",
       "line": 1,
-      "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Template-only and Glimmer components. If you\nare looking for the API documentation for Classic components, it is\n[available here](/ember/release/classes/Component). The source code for\nGlimmer components can be found in [`@glimmer/component`](https://github.com/glimmerjs/glimmer.js/tree/master/packages/%40glimmer/component).\n\n## Defining a Template-only Component\n\nThe simplest way to create a component is to create a template file in\n`app/templates/components`. For example, if you name a template\n`app/templates/components/person-profile.hbs`:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n<img src={{@person.avatar}}>\n<p class='signature'>{{@person.signature}}</p>\n```\n\nYou will be able to use `<PersonProfile />` to invoke this component elsewhere\nin your application:\n\n```app/templates/application.hbs\n<PersonProfile @person={{this.currentUser}} />\n```\n\nNote that component names are capitalized here in order to distinguish them\nfrom regular HTML elements, but they are dasherized in the file system.\n\nWhile the angle bracket invocation form is generally preferred, it is also\npossible to invoke the same component with the `{{person-profile}}` syntax:\n\n```app/templates/application.hbs\n{{person-profile person=this.currentUser}}\n```\n\nNote that with this syntax, you use dashes in the component name and\narguments are passed without the `@` sign.\n\nIn both cases, Ember will render the content of the component template we\ncreated above. The end result will be something like this:\n\n```html\n<h1>Tomster</h1>\n<img src=\"https://emberjs.com/tomster.jpg\">\n<p class='signature'>Out of office this week</p>\n```\n\n## File System Nesting\n\nComponents can be nested inside sub-folders for logical groupping. For\nexample, if we placed our template in\n`app/templates/components/person/short-profile.hbs`, we can invoke it as\n`<Person::ShortProfile />`:\n\n```app/templates/application.hbs\n<Person::ShortProfile @person={{this.currentUser}} />\n```\n\nOr equivalently, `{{person/short-profile}}`:\n\n```app/templates/application.hbs\n{{person/short-profile person=this.currentUser}}\n```\n\n## Using Blocks\n\nYou can use `yield` inside a template to include the **contents** of any block\nattached to the component. For instance, if we added a `{{yield}}` to our\ncomponent like so:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield}}\n```\n\nWe could then invoke it like this:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <p>Admin mode</p>\n</PersonProfile>\n```\n\nor with curly syntax like this:\n\n```handlebars\n{{#person-profile person=this.currentUser}}\n  <p>Admin mode</p>\n{{/person-profile}}\n```\n\nAnd the content passed in between the brackets of the component would be\nrendered in the same place as the `{{yield}}` within it, replacing it.\n\nBlocks are executed in their original context, meaning they have access to the\nscope and any in-scope variables where they were defined.\n\n### Passing parameters to blocks\n\nYou can also pass positional parameters to `{{yield}}`, which are then made\navailable in the block:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield @person.signature}}\n```\n\nWe can then use this value in the block like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n```\n\n### Passing multiple blocks\n\nYou can pass multiple blocks to a component by giving them names, and\nspecifying which block you are yielding to with `{{yield}}`. For instance, if\nwe wanted to add a way for users to customize the title of our\n`<PersonProfile>` component, we could add a named block inside of the header:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield to=\"title\"}}</h1>\n{{yield}}\n```\n\nThis component could then be invoked like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title>{{this.currentUser.name}}</:title>\n  <:default>{{this.currentUser.signature}}</:default>\n</PersonProfile>\n```\n\nWhen passing named blocks, you must name every block, including the `default`\nblock, which is the block that is defined if you do not pass a `to` parameter\nto `{{yield}}`. Whenever you invoke a component without passing explicitly\nnamed blocks, the passed block is considered the `default` block.\n\n### Passing parameters to named blocks\n\nYou can also pass parameters to named blocks:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield @person.name to=\"title\"}}</h1>\n{{yield @person.signature}}\n```\n\nThese parameters can then be used like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n```\n\n### Checking to see if a block exists\n\nYou can also check to see if a block exists using the `(has-block)` keyword,\nand conditionally use it, or provide a default template instead.\n\n```app/templates/components/person-profile.hbs\n<h1>\n  {{#if (has-block \"title\")}}\n    {{yield @person.name to=\"title\"}}\n  {{else}}\n    {{@person.name}}\n  {{/if}}\n</h1>\n\n{{#if (has-block)}}\n  {{yield @person.signature}}\n{{else}}\n  {{@person.signature}}\n{{/if}}\n```\n\nWith this template, we can then optionally pass in one block, both blocks, or\nnone at all:\n\n```handlebars\n{{! passing both blocks }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n\n{{! passing just the title block }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n</PersonProfile>\n\n{{! passing just the default block }}\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n\n{{! not passing any blocks }}\n<PersonProfile @person={{this.currentUser}}/>\n```\n\n### Checking to see if a block has parameters\n\nWe can also check if a block receives parameters using the `(has-block-params)`\nkeyword, and conditionally yield different values if so.\n\n```app/templates/components/person-profile.hbs\n{{#if (has-block-params)}}\n  {{yield @person.signature}}\n{{else}}\n  {{yield}}\n{{/if}}\n```\n\n## Customizing Components With JavaScript\n\nTo add JavaScript to a component, create a JavaScript file in the same\nlocation as the template file, with the same name, and export a subclass\nof `Component` as the default value. For example, to add Javascript to the\n`PersonProfile` component which we defined above, we would create\n`app/comopnents/person-profile.js` and export our class as the default, like\nso:\n\n```app/components/person-profile.js\nimport Component from '@glimmer/component';\n\nexport default class PersonProfileComponent extends Component {\n  get displayName() {\n    let { title, firstName, lastName } = this.args.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n}\n```\n\nYou can add your own properties, methods, and lifecycle hooks to this\nsubclass to customize its behavior, and you can reference the instance of the\nclass in your template using `{{this}}`. For instance, we could access the\n`displayName` property of our `PersonProfile` component instance in the\ntemplate like this:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## `constructor`\n\nparams: `owner` object and `args` object\n\nConstructs a new component and assigns itself the passed properties. The\nconstructor is run whenever a new instance of the component is created, and\ncan be used to setup the initial state of the component.\n\n```javascript\nimport Component from '@glimmer/component';\n\nexport default class SomeComponent extends Component {\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.displayMode === 'list') {\n      this.items = [];\n    }\n  }\n}\n```\n\nService injections and arguments are available in the constructor.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.fadeIn === true) {\n      this.myAnimations.register(this, 'fade-in');\n    }\n  }\n}\n```\n\n## `willDestroy`\n\n`willDestroy` is called after the component has been removed from the DOM, but\nbefore the component is fully destroyed. This lifecycle hook can be used to\ncleanup the component and any related state.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  willDestroy() {\n    super.willDestroy(...arguments);\n\n    this.myAnimations.unregister(this);\n  }\n}\n```\n\n## `args`\n\nThe `args` property of Glimmer components is an object that contains the\n_arguments_ that are passed to the component. For instance, the\nfollowing component usage:\n\n```handlebars\n<SomeComponent @fadeIn={{true}} />\n```\n\nWould result in the following `args` object to be passed to the component:\n\n```javascript\n{ fadeIn: true }\n```\n\n`args` can be accessed at any point in the component lifecycle, including\n`constructor` and `willDestroy`. They are also automatically marked as tracked\nproperties, and they can be depended on as computed property dependencies:\n\n```javascript\nimport Component from '@glimmer/component';\nimport { computed } from '@ember/object';\n\nexport default class SomeComponent extends Component {\n\n  @computed('args.someValue')\n  get computedGetter() {\n    // updates whenever args.someValue updates\n    return this.args.someValue;\n  }\n\n  get standardGetter() {\n    // updates whenever args.anotherValue updates (Ember 3.13+)\n    return this.args.anotherValue;\n  }\n}\n```\n\n## `isDestroying`\n\nA boolean flag to tell if the component is in the process of destroying. This is set to\ntrue before `willDestroy` is called.\n\n## `isDestroyed`\nA boolean to tell if the component has been fully destroyed. This is set to true\nafter `willDestroy` is called.",
+      "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default components for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Template-only and Glimmer components. If you\nare looking for the API documentation for Classic components, it is\n[available here](/ember/release/classes/Component). The source code for\nGlimmer components can be found in [`@glimmer/component`](https://github.com/glimmerjs/glimmer.js/tree/master/packages/%40glimmer/component).\n\n## Defining a Template-only Component\n\nThe simplest way to create a component is to create a template file in\n`app/templates/components`. For example, if you name a template\n`app/templates/components/person-profile.hbs`:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n<img src={{@person.avatar}}>\n<p class='signature'>{{@person.signature}}</p>\n```\n\nYou will be able to use `<PersonProfile />` to invoke this component elsewhere\nin your application:\n\n```app/templates/application.hbs\n<PersonProfile @person={{this.currentUser}} />\n```\n\nNote that component names are capitalized here in order to distinguish them\nfrom regular HTML elements, but they are dasherized in the file system.\n\nWhile the angle bracket invocation form is generally preferred, it is also\npossible to invoke the same component with the `{{person-profile}}` syntax:\n\n```app/templates/application.hbs\n{{person-profile person=this.currentUser}}\n```\n\nNote that with this syntax, you use dashes in the component name and\narguments are passed without the `@` sign.\n\nIn both cases, Ember will render the content of the component template we\ncreated above. The end result will be something like this:\n\n```html\n<h1>Tomster</h1>\n<img src=\"https://emberjs.com/tomster.jpg\">\n<p class='signature'>Out of office this week</p>\n```\n\n## File System Nesting\n\nComponents can be nested inside sub-folders for logical groupping. For\nexample, if we placed our template in\n`app/templates/components/person/short-profile.hbs`, we can invoke it as\n`<Person::ShortProfile />`:\n\n```app/templates/application.hbs\n<Person::ShortProfile @person={{this.currentUser}} />\n```\n\nOr equivalently, `{{person/short-profile}}`:\n\n```app/templates/application.hbs\n{{person/short-profile person=this.currentUser}}\n```\n\n## Using Blocks\n\nYou can use `yield` inside a template to include the **contents** of any block\nattached to the component. For instance, if we added a `{{yield}}` to our\ncomponent like so:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield}}\n```\n\nWe could then invoke it like this:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <p>Admin mode</p>\n</PersonProfile>\n```\n\nor with curly syntax like this:\n\n```handlebars\n{{#person-profile person=this.currentUser}}\n  <p>Admin mode</p>\n{{/person-profile}}\n```\n\nAnd the content passed in between the brackets of the component would be\nrendered in the same place as the `{{yield}}` within it, replacing it.\n\nBlocks are executed in their original context, meaning they have access to the\nscope and any in-scope variables where they were defined.\n\n### Passing parameters to blocks\n\nYou can also pass positional parameters to `{{yield}}`, which are then made\navailable in the block:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield @person.signature}}\n```\n\nWe can then use this value in the block like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n```\n\n### Passing multiple blocks\n\nYou can pass multiple blocks to a component by giving them names, and\nspecifying which block you are yielding to with `{{yield}}`. For instance, if\nwe wanted to add a way for users to customize the title of our\n`<PersonProfile>` component, we could add a named block inside of the header:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield to=\"title\"}}</h1>\n{{yield}}\n```\n\nThis component could then be invoked like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title>{{this.currentUser.name}}</:title>\n  <:default>{{this.currentUser.signature}}</:default>\n</PersonProfile>\n```\n\nWhen passing named blocks, you must name every block, including the `default`\nblock, which is the block that is defined if you do not pass a `to` parameter\nto `{{yield}}`. Whenever you invoke a component without passing explicitly\nnamed blocks, the passed block is considered the `default` block.\n\n### Passing parameters to named blocks\n\nYou can also pass parameters to named blocks:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield @person.name to=\"title\"}}</h1>\n{{yield @person.signature}}\n```\n\nThese parameters can then be used like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n```\n\n### Checking to see if a block exists\n\nYou can also check to see if a block exists using the `(has-block)` keyword,\nand conditionally use it, or provide a default template instead.\n\n```app/templates/components/person-profile.hbs\n<h1>\n  {{#if (has-block \"title\")}}\n    {{yield @person.name to=\"title\"}}\n  {{else}}\n    {{@person.name}}\n  {{/if}}\n</h1>\n\n{{#if (has-block)}}\n  {{yield @person.signature}}\n{{else}}\n  {{@person.signature}}\n{{/if}}\n```\n\nWith this template, we can then optionally pass in one block, both blocks, or\nnone at all:\n\n```handlebars\n{{! passing both blocks }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n\n{{! passing just the title block }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n</PersonProfile>\n\n{{! passing just the default block }}\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n\n{{! not passing any blocks }}\n<PersonProfile @person={{this.currentUser}}/>\n```\n\n### Checking to see if a block has parameters\n\nWe can also check if a block receives parameters using the `(has-block-params)`\nkeyword, and conditionally yield different values if so.\n\n```app/templates/components/person-profile.hbs\n{{#if (has-block-params)}}\n  {{yield @person.signature}}\n{{else}}\n  {{yield}}\n{{/if}}\n```\n\n## Customizing Components With JavaScript\n\nTo add JavaScript to a component, create a JavaScript file in the same\nlocation as the template file, with the same name, and export a subclass\nof `Component` as the default value. For example, to add Javascript to the\n`PersonProfile` component which we defined above, we would create\n`app/components/person-profile.js` and export our class as the default, like\nso:\n\n```app/components/person-profile.js\nimport Component from '@glimmer/component';\n\nexport default class PersonProfileComponent extends Component {\n  get displayName() {\n    let { title, firstName, lastName } = this.args.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n}\n```\n\nYou can add your own properties, methods, and lifecycle hooks to this\nsubclass to customize its behavior, and you can reference the instance of the\nclass in your template using `{{this}}`. For instance, we could access the\n`displayName` property of our `PersonProfile` component instance in the\ntemplate like this:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## `constructor`\n\nparams: `owner` object and `args` object\n\nConstructs a new component and assigns itself the passed properties. The\nconstructor is run whenever a new instance of the component is created, and\ncan be used to setup the initial state of the component.\n\n```javascript\nimport Component from '@glimmer/component';\n\nexport default class SomeComponent extends Component {\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.displayMode === 'list') {\n      this.items = [];\n    }\n  }\n}\n```\n\nService injections and arguments are available in the constructor.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.fadeIn === true) {\n      this.myAnimations.register(this, 'fade-in');\n    }\n  }\n}\n```\n\n## `willDestroy`\n\n`willDestroy` is called after the component has been removed from the DOM, but\nbefore the component is fully destroyed. This lifecycle hook can be used to\ncleanup the component and any related state.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  willDestroy() {\n    super.willDestroy(...arguments);\n\n    this.myAnimations.unregister(this);\n  }\n}\n```\n\n## `args`\n\nThe `args` property of Glimmer components is an object that contains the\n_arguments_ that are passed to the component. For instance, the\nfollowing component usage:\n\n```handlebars\n<SomeComponent @fadeIn={{true}} />\n```\n\nWould result in the following `args` object to be passed to the component:\n\n```javascript\n{ fadeIn: true }\n```\n\n`args` can be accessed at any point in the component lifecycle, including\n`constructor` and `willDestroy`. They are also automatically marked as tracked\nproperties, and they can be depended on as computed property dependencies:\n\n```javascript\nimport Component from '@glimmer/component';\nimport { computed } from '@ember/object';\n\nexport default class SomeComponent extends Component {\n\n  @computed('args.someValue')\n  get computedGetter() {\n    // updates whenever args.someValue updates\n    return this.args.someValue;\n  }\n\n  get standardGetter() {\n    // updates whenever args.anotherValue updates (Ember 3.13+)\n    return this.args.anotherValue;\n  }\n}\n```\n\n## `isDestroying`\n\nA boolean flag to tell if the component is in the process of destroying. This is set to\ntrue before `willDestroy` is called.\n\n## `isDestroyed`\nA boolean to tell if the component has been fully destroyed. This is set to true\nafter `willDestroy` is called.",
       "access": "public",
       "tagname": ""
     },
@@ -2062,7 +2110,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 21,
+      "line": 22,
       "description": "Set `EmberENV.FEATURES` in your application's `config/environment.js` file\nto enable canary features in your application.\n\nSee the [feature flag guide](https://guides.emberjs.com/release/configuring-ember/feature-flags/)\nfor more details.",
       "access": "public",
       "tagname": ""
@@ -2198,6 +2246,21 @@
       "file": "packages/@ember/polyfills/lib/assign.ts",
       "line": 3
     },
+    "@ember/renderer": {
+      "name": "@ember/renderer",
+      "submodules": {},
+      "elements": {},
+      "classes": {
+        "Renderer": 1
+      },
+      "fors": {},
+      "namespaces": {},
+      "tag": "module",
+      "file": "packages/@ember/renderer/index.ts",
+      "line": 6,
+      "access": "public",
+      "tagname": ""
+    },
     "@ember/runloop": {
       "name": "@ember/runloop",
       "submodules": {},
@@ -2210,8 +2273,8 @@
       },
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@ember/runloop/index.js",
-      "line": 67
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 96
     },
     "@ember/service": {
       "name": "@ember/service",
@@ -2347,7 +2410,7 @@
       "module": "rsvp",
       "namespace": "",
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 65,
+      "line": 59,
       "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": "",
@@ -2380,8 +2443,8 @@
       "extension_for": [],
       "module": "@ember/debug",
       "namespace": "",
-      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
-      "line": 9,
+      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
+      "line": 16,
       "description": "The `ContainerDebugAdapter` helps the container and resolver interface\nwith tools that debug Ember such as the\n[Ember Inspector](https://github.com/emberjs/ember-inspector)\nfor Chrome and Firefox.\n\nThis class can be extended by a custom resolver implementer\nto override some of the methods with library-specific code.\n\nThe methods likely to be overridden are:\n\n* `canCatalogEntriesByType`\n* `catalogEntriesByType`\n\nThe adapter will need to be registered\nin the application's container as `container-debug-adapter:main`.\n\nExample:\n\n```javascript\nApplication.initializer({\n  name: \"containerDebugAdapter\",\n\n  initialize(application) {\n    application.register('container-debug-adapter:main', require('app/container-debug-adapter'));\n  }\n});\n```",
       "extends": "EmberObject",
       "since": "1.5.0",
@@ -2398,8 +2461,8 @@
       "extension_for": [],
       "module": "@ember/debug",
       "namespace": "",
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 125,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 158,
       "description": "The `DataAdapter` helps a data persistence library\ninterface with tools that debug Ember such\nas the [Ember Inspector](https://github.com/emberjs/ember-inspector)\nfor Chrome and Firefox.\n\nThis class will be extended by a persistence library\nwhich will override some of the methods with\nlibrary-specific code.\n\nThe methods likely to be overridden are:\n\n* `getFilters`\n* `detect`\n* `columnsForType`\n* `getRecords`\n* `getRecordColumnValues`\n* `getRecordKeywords`\n* `getRecordFilterValues`\n* `getRecordColor`\n\nThe adapter will need to be registered\nin the application's container as `dataAdapter:main`.\n\nExample:\n\n```javascript\nApplication.initializer({\n  name: \"data-adapter\",\n\n  initialize: function(application) {\n    application.register('data-adapter:main', DS.DataAdapter);\n  }\n});\n```",
       "extends": "EmberObject",
       "access": "public",
@@ -2464,7 +2527,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/utils/curly-component-state-bucket.ts",
-      "line": 33,
+      "line": 15,
       "description": "Represents the internal state of the component.",
       "access": "private",
       "tagname": ""
@@ -2491,7 +2554,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 37,
+      "line": 38,
       "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is\n[available here](/ember/release/modules/@glimmer%2Fcomponent).\n\n## Defining a Classic Component\n\nIf you want to customize the component in order to handle events, transform\narguments or maintain internal state, you implement a subclass of `Component`.\n\nOne example is to add computed properties to your component:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  displayName: computed('person.title', 'person.firstName', 'person.lastName', function() {\n    let { title, firstName, lastName } = this.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## Customizing a Classic Component's HTML Element in JavaScript\n\n### HTML Tag\n\nThe default HTML tag name used for a component's HTML representation is `div`.\nThis can be customized by setting the `tagName` property.\n\nConsider the following component class:\n\n```app/components/emphasized-paragraph.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'em'\n});\n```\n\nWhen invoked, this component would produce output that looks something like\nthis:\n\n```html\n<em id=\"ember1\" class=\"ember-view\"></em>\n```\n\n### HTML `class` Attribute\n\nThe HTML `class` attribute of a component's tag can be set by providing a\n`classNames` property that is set to an array of strings:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class']\n});\n```\n\nInvoking this component will produce output that looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class\"></div>\n```\n\n`class` attribute values can also be set by providing a `classNameBindings`\nproperty set to an array of properties names for the component. The return\nvalue of these properties will be added as part of the value for the\ncomponents's `class` attribute. These properties can be computed properties:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  classNames: ['my-class', 'my-other-class'],\n  classNameBindings: ['propertyA', 'propertyB'],\n\n  propertyA: 'from-a',\n  propertyB: computed(function() {\n    if (someLogic) { return 'from-b'; }\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nNote that `classNames` and `classNameBindings` is in addition to the `class`\nattribute passed with the angle bracket invocation syntax. Therefore, if this\ncomponent was invoked like so:\n\n```handlebars\n<MyWidget class=\"from-invocation\" />\n```\n\nThe resulting HTML will look similar to this:\n\n```html\n<div id=\"ember1\" class=\"from-invocation ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nIf the value of a class name binding returns a boolean the property name\nitself will be used as the class name if the property is true. The class name\nwill not be added if the value is `false` or `undefined`.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['hovered'],\n\n  hovered: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view hovered\"></div>\n```\n\n### Custom Class Names for Boolean Values\n\nWhen using boolean class name bindings you can supply a string value other\nthan the property name for use as the `class` HTML attribute by appending the\npreferred value after a \":\" character when defining the binding:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['awesome:so-very-cool'],\n\n  awesome: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view so-very-cool\"></div>\n```\n\nBoolean value class name bindings whose property names are in a\ncamelCase-style format will be converted to a dasherized format:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isUrgent'],\n\n  isUrgent: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view is-urgent\"></div>\n```\n\nClass name bindings can also refer to object values that are found by\ntraversing a path relative to the component itself:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport EmberObject from '@ember/object';\n\nexport default Component.extend({\n  classNameBindings: ['messages.empty'],\n\n  messages: EmberObject.create({\n    empty: true\n  })\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view empty\"></div>\n```\n\nIf you want to add a class name for a property which evaluates to true and\nand a different class name if it evaluates to false, you can pass a binding\nlike this:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  classNameBindings: ['isEnabled:enabled:disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view enabled\"></div>\n```\n\nWhen isEnabled is `false`, the resulting HTML representation looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nThis syntax offers the convenience to add a class if a property is `false`:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\n// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false\nexport default Component.extend({\n  classNameBindings: ['isEnabled::disabled'],\n  isEnabled: true\n});\n```\n\nInvoking this component when the `isEnabled` property is true will produce\nHTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view\"></div>\n```\n\nInvoking it when the `isEnabled` property on the component is `false` will\nproduce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nUpdates to the value of a class name binding will result in automatic update\nof the  HTML `class` attribute in the component's rendered HTML\nrepresentation. If the value becomes `false` or `undefined` the class name\nwill be removed.\n\nBoth `classNames` and `classNameBindings` are concatenated properties. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n### Other HTML Attributes\n\nThe HTML attribute section of a component's tag can be set by providing an\n`attributeBindings` property set to an array of property names on the component.\nThe return value of these properties will be used as the value of the component's\nHTML associated attribute:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['href'],\n\n  href: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nOne property can be mapped on to another by placing a \":\" between\nthe source property and the destination property:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'a',\n  attributeBindings: ['url:href'],\n\n  url: 'http://google.com'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nHTML attributes passed with angle bracket invocations will take precedence\nover those specified in `attributeBindings`. Therefore, if this component was\ninvoked like so:\n\n```handlebars\n<MyAnchor href=\"http://bing.com\" @url=\"http://google.com\" />\n```\n\nThe resulting HTML will looks like this:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://bing.com\"></a>\n```\n\nNote that the `href` attribute is ultimately set to `http://bing.com`,\ndespite it having attribute binidng to the `url` property, which was\nset to `http://google.com`.\n\nNamespaced attributes (e.g. `xlink:href`) are supported, but have to be\nmapped, since `:` is not a valid character for properties in Javascript:\n\n```app/components/my-use.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'use',\n  attributeBindings: ['xlinkHref:xlink:href'],\n\n  xlinkHref: '#triangle'\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<use xlink:href=\"#triangle\"></use>\n```\n\nIf the value of a property monitored by `attributeBindings` is a boolean, the\nattribute will be present or absent depending on the value:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: false\n});\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<input id=\"ember1\" class=\"ember-view\" />\n```\n\n`attributeBindings` can refer to computed properties:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default Component.extend({\n  tagName: 'input',\n  attributeBindings: ['disabled'],\n\n  disabled: computed(function() {\n    if (someLogic) {\n      return true;\n    } else {\n      return false;\n    }\n  })\n});\n```\n\nTo prevent setting an attribute altogether, use `null` or `undefined` as the\nvalue of the property used in `attributeBindings`:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  tagName: 'form',\n  attributeBindings: ['novalidate'],\n  novalidate: null\n});\n```\n\nUpdates to the property of an attribute binding will result in automatic\nupdate of the  HTML attribute in the component's HTML output.\n\n`attributeBindings` is a concatenated property. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n## Layouts\n\nThe `layout` property can be used to dynamically specify a template associated\nwith a component class, instead of relying on Ember to link together a\ncomponent class and a template based on file names.\n\nIn general, applications should not use this feature, but it's commonly used\nin addons for historical reasons.\n\nThe `layout` property should be set to the default export of a template\nmodule, which is the name of a template file without the `.hbs` extension.\n\n```app/templates/components/person-profile.hbs\n<h1>Person's Title</h1>\n<div class='details'>{{yield}}</div>\n```\n\n```app/components/person-profile.js\n  import Component from '@ember/component';\n  import layout from '../templates/components/person-profile';\n\n  export default Component.extend({\n    layout\n  });\n```\n\nIf you invoke the component:\n\n```handlebars\n<PersonProfile>\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</PersonProfile>\n```\n\nor\n\n```handlebars\n{{#person-profile}}\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n{{/person-profile}}\n```\n\nIt will result in the following HTML output:\n\n```html\n<h1>Person's Title</h1>\n  <div class=\"details\">\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</div>\n```\n\n## Handling Browser Events\n\nComponents can respond to user-initiated events in one of three ways: passing\nactions with angle bracket invocation, adding event handler methods to the\ncomponent's class, or adding actions to the component's template.\n\n### Passing Actions With Angle Bracket Invocation\n\nFor one-off events specific to particular instance of a component, it is possible\nto pass actions to the component's element using angle bracket invocation syntax.\n\n```handlebars\n<MyWidget {{action 'firstWidgetClicked'}} />\n\n<MyWidget {{action 'secondWidgetClicked'}} />\n```\n\nIn this case, when the first component is clicked on, Ember will invoke the\n`firstWidgetClicked` action. When the second component is clicked on, Ember\nwill invoke the `secondWidgetClicked` action instead.\n\nBesides `{{action}}`, it is also possible to pass any arbitrary element modifiers\nusing the angle bracket invocation syntax.\n\n### Event Handler Methods\n\nComponents can also respond to user-initiated events by implementing a method\nthat matches the event name. This approach is appropriate when the same event\nshould be handled by all instances of the same component.\n\nAn event object will be passed as the argument to the event handler method.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  click(event) {\n    // `event.target` is either the component's element or one of its children\n    let tag = event.target.tagName.toLowerCase();\n    console.log('clicked on a `<${tag}>` HTML element!');\n  }\n});\n```\n\nIn this example, whenever the user clicked anywhere inside the component, it\nwill log a message to the console.\n\nIt is possible to handle event types other than `click` by implementing the\nfollowing event handler methods. In addition, custom events can be registered\nby using `Application.customEvents`.\n\nTouch events:\n\n* `touchStart`\n* `touchMove`\n* `touchEnd`\n* `touchCancel`\n\nKeyboard events:\n\n* `keyDown`\n* `keyUp`\n* `keyPress`\n\nMouse events:\n\n* `mouseDown`\n* `mouseUp`\n* `contextMenu`\n* `click`\n* `doubleClick`\n* `focusIn`\n* `focusOut`\n\nForm events:\n\n* `submit`\n* `change`\n* `focusIn`\n* `focusOut`\n* `input`\n\nDrag and drop events:\n\n* `dragStart`\n* `drag`\n* `dragEnter`\n* `dragLeave`\n* `dragOver`\n* `dragEnd`\n* `drop`\n\n### `{{action}}` Helper\n\nInstead of handling all events of a particular type anywhere inside the\ncomponent's element, you may instead want to limit it to a particular\nelement in the component's template. In this case, it would be more\nconvenient to implement an action instead.\n\nFor example, you could implement the action `hello` for the `person-profile`\ncomponent:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  actions: {\n    hello(name) {\n      console.log(\"Hello\", name);\n    }\n  }\n});\n```\n\nAnd then use it in the component's template:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n\n<button {{action 'hello' @person.name}}>\n  Say Hello to {{@person.name}}\n</button>\n```\n\nWhen the user clicks the button, Ember will invoke the `hello` action,\npassing in the current value of `@person.name` as an argument.\n\nSee [Ember.Templates.helpers.action](/ember/release/classes/Ember.Templates.helpers/methods/action?anchor=action).",
       "extends": "Ember.CoreView",
       "uses": [
@@ -2526,7 +2589,7 @@
       "module": "@ember/component",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 37,
+      "line": 43,
       "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",
@@ -2977,7 +3040,7 @@
       "module": "@ember/routing",
       "namespace": "",
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 138,
+      "line": 139,
       "description": "The `EmberRouter` class manages the application state and URLs. Refer to\nthe [routing guide](https://guides.emberjs.com/release/routing/) for documentation.",
       "extends": "EmberObject",
       "uses": [
@@ -3463,8 +3526,8 @@
       "extension_for": [],
       "module": "ember",
       "namespace": "Ember",
-      "file": "packages/@ember/-internals/views/lib/views/core_view.js",
-      "line": 5,
+      "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
+      "line": 7,
       "description": "`Ember.CoreView` is an abstract class that exists to give view-like behavior\nto both Ember's main view class `Component` and other classes that don't need\nthe full functionality of `Component`.\n\nUnless you have specific needs for `CoreView`, you will use `Component`\nin your applications.",
       "extends": "EmberObject",
       "deprecated": true,
@@ -3540,7 +3603,7 @@
       "module": "@ember/canary-features",
       "namespace": "",
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 21,
+      "line": 22,
       "description": "The hash of enabled Canary features. Add to this, any canary features\nbefore creating your application.",
       "static": 1,
       "since": "1.1.0",
@@ -3730,6 +3793,21 @@
       "module": "@ember/polyfills",
       "namespace": ""
     },
+    "Renderer": {
+      "name": "Renderer",
+      "shortname": "Renderer",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "@ember/renderer",
+      "namespace": "",
+      "file": "packages/@ember/renderer/index.ts",
+      "line": 6,
+      "access": "public",
+      "tagname": ""
+    },
     "@ember/runloop": {
       "name": "@ember/runloop",
       "shortname": "@ember/runloop",
@@ -4600,7 +4678,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 104,
+      "line": 100,
       "description": "A backup registry for resolving registrations when no matches can be found.",
       "access": "private",
       "tagname": "",
@@ -4612,7 +4690,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 112,
+      "line": 108,
       "description": "An object that has a `resolve` method that resolves a name.",
       "access": "private",
       "tagname": "",
@@ -4624,7 +4702,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 120,
+      "line": 116,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4635,7 +4713,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 126,
+      "line": 122,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4646,7 +4724,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 133,
+      "line": 129,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4657,7 +4735,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 140,
+      "line": 136,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4668,7 +4746,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 147,
+      "line": 143,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -4679,7 +4757,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 154,
+      "line": 150,
       "description": "Creates a container based on this registry.",
       "access": "private",
       "tagname": "",
@@ -4701,7 +4779,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 166,
+      "line": 162,
       "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": "",
@@ -4729,7 +4807,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 200,
+      "line": 198,
       "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": "",
@@ -4747,7 +4825,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 230,
+      "line": 228,
       "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": "",
@@ -4783,7 +4861,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 273,
+      "line": 271,
       "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": "",
@@ -4805,7 +4883,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 296,
+      "line": 294,
       "description": "A hook to enable custom fullName normalization behavior",
       "access": "private",
       "tagname": "",
@@ -4827,7 +4905,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 314,
+      "line": 312,
       "description": "Normalize a fullName based on the application's conventions",
       "access": "private",
       "tagname": "",
@@ -4849,7 +4927,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 329,
+      "line": 327,
       "itemtype": "method",
       "name": "makeToString",
       "access": "private",
@@ -4875,7 +4953,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 347,
+      "line": 345,
       "description": "Given a fullName check if the container is aware of its factory\nor singleton instance.",
       "access": "private",
       "tagname": "",
@@ -4911,7 +4989,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 366,
+      "line": 364,
       "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": "",
@@ -4934,7 +5012,7 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 407,
+      "line": 405,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -4956,14 +5034,14 @@
     },
     {
       "file": "packages/@ember/-internals/container/lib/registry.ts",
-      "line": 450,
+      "line": 448,
       "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": 480,
+      "line": 478,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -5083,20 +5161,19 @@
       "module": "rsvp"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
-      "line": 50,
+      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
+      "line": 57,
       "description": "The resolver instance of the application\nbeing debugged. This property will be injected\non creation.",
       "itemtype": "property",
       "name": "resolver",
-      "default": "null",
       "access": "public",
       "tagname": "",
       "class": "ContainerDebugAdapter",
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
-      "line": 61,
+      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
+      "line": 67,
       "description": "Returns true if it is possible to catalog a list of available\nclasses in the resolver for a given type.",
       "itemtype": "method",
       "name": "canCatalogEntriesByType",
@@ -5117,8 +5194,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.js",
-      "line": 78,
+      "file": "packages/@ember/-internals/extension-support/lib/container_debug_adapter.ts",
+      "line": 84,
       "description": "Returns the available classes a given type.",
       "itemtype": "method",
       "name": "catalogEntriesByType",
@@ -5139,8 +5216,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 177,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 214,
       "description": "The container-debug-adapter which is used\nto list all models.",
       "itemtype": "property",
       "name": "containerDebugAdapter",
@@ -5152,8 +5229,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 187,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 224,
       "description": "The number of attributes to send\nas columns. (Enough to make the record\nidentifiable).",
       "access": "private",
       "tagname": "",
@@ -5165,8 +5242,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 199,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 236,
       "description": "Ember Data > v1.0.0-beta.18\nrequires string model names to be passed\naround instead of the actual factories.\n\nThis is a stamp for the Ember Inspector\nto differentiate between the versions\nto be able to support older versions too.",
       "access": "public",
       "tagname": "",
@@ -5176,8 +5253,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 213,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 250,
       "description": "Map from records arrays to RecordsWatcher instances",
       "access": "private",
       "tagname": "",
@@ -5188,8 +5265,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 221,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 258,
       "description": "Map from records arrays to TypeWatcher instances",
       "access": "private",
       "tagname": "",
@@ -5200,8 +5277,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 229,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 266,
       "description": "Callback that is currently scheduled on backburner end to flush and check\nall active watchers.",
       "access": "private",
       "tagname": "",
@@ -5212,8 +5289,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 239,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 276,
       "description": "Stores all methods that clear observers.\nThese methods will be called on destruction.",
       "access": "private",
       "tagname": "",
@@ -5224,8 +5301,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 248,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 285,
       "description": "Specifies how records can be filtered.\nRecords returned will need to have a `filterValues`\nproperty with a key for every name in the returned array.",
       "access": "public",
       "tagname": "",
@@ -5239,8 +5316,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 262,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 299,
       "description": "Fetch the model types and observe them for changes.",
       "access": "public",
       "tagname": "",
@@ -5266,8 +5343,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 307,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 347,
       "description": "Fetch the records of a given type and observe them for changes.",
       "access": "public",
       "tagname": "",
@@ -5303,8 +5380,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 374,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 419,
       "description": "Clear all observers before destruction",
       "access": "private",
       "tagname": "",
@@ -5314,8 +5391,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 392,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 437,
       "description": "Detect whether a class is a model.\n\nTest that against the model class\nof your persistence library.",
       "access": "public",
       "tagname": "",
@@ -5328,8 +5405,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 406,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 451,
       "description": "Get the columns for a given model type.",
       "access": "public",
       "tagname": "",
@@ -5343,8 +5420,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 419,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 464,
       "description": "Adds observers to a model type class.",
       "access": "private",
       "tagname": "",
@@ -5370,8 +5447,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 456,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 501,
       "description": "Wraps a given model type and observes changes to it.",
       "access": "private",
       "tagname": "",
@@ -5390,15 +5467,15 @@
         }
       ],
       "return": {
-        "description": "Contains the wrapped type and the function to remove observers\nFormat:\n  type: {Object} The wrapped type.\n    The wrapped type has the following format:\n      name: {String} The name of the type.\n      count: {Integer} The number of records available.\n      columns: {Columns} An array of columns to describe the record.\n      object: {Class} The actual Model type class.\n  release: {Function} The function to remove observers.",
+        "description": "The wrapped type has the following format:\n  name: {String} The name of the type.\n  count: {Integer} The number of records available.\n  columns: {Columns} An array of columns to describe the record.\n  object: {Class} The actual Model type class.",
         "type": "Object"
       },
       "class": "DataAdapter",
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 487,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 525,
       "description": "Fetches all models defined in the application.",
       "access": "private",
       "tagname": "",
@@ -5412,8 +5489,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 516,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 550,
       "description": "Loops over all namespaces and all objects\nattached to them.",
       "access": "private",
       "tagname": "",
@@ -5427,8 +5504,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 545,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 579,
       "description": "Fetches all loaded records for a given type.",
       "access": "public",
       "tagname": "",
@@ -5442,8 +5519,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 558,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 592,
       "description": "Wraps a record and observers changes to it.",
       "access": "private",
       "tagname": "",
@@ -5464,8 +5541,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 579,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 612,
       "description": "Gets the values for each column.",
       "access": "public",
       "tagname": "",
@@ -5479,8 +5556,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 591,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 624,
       "description": "Returns keywords to match when searching records.",
       "access": "public",
       "tagname": "",
@@ -5494,8 +5571,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 602,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 635,
       "description": "Returns the values of filters defined by `getFilters`.",
       "access": "public",
       "tagname": "",
@@ -5516,8 +5593,8 @@
       "module": "@ember/debug"
     },
     {
-      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.js",
-      "line": 614,
+      "file": "packages/@ember/-internals/extension-support/lib/data_adapter.ts",
+      "line": 647,
       "description": "Each record can have a color that represents its state.",
       "access": "public",
       "tagname": "",
@@ -5946,6 +6023,18 @@
       "class": "Ember.Templates.helpers",
       "module": "ember"
     },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts",
+      "line": 5,
+      "description": "Use the {{unique-id}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\n```handlebars\n<input id={{unique-id}} type=\"email\" />\n```\nEach invocation of {{unique-id}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```handlebars\n{{#let (unique-id) as |emailId|}}\n  <label for={{emailId}}>Email address</label>\n  <input id={{emailId}} type=\"email\" />\n{{/let}}\n```",
+      "itemtype": "method",
+      "name": "unique-id",
+      "since": "4.4.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Ember.Templates.helpers",
+      "module": "ember"
+    },
     {
       "file": "packages/@ember/-internals/glimmer/lib/modifiers/on.ts",
       "line": 5,
@@ -6015,6 +6104,33 @@
       "class": "Ember.Templates.helpers",
       "module": "ember"
     },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/utils/managers.ts",
+      "line": 9,
+      "description": "Associate a class with a component manager (an object that is responsible for\ncoordinating the lifecycle events that occurs when invoking, rendering and\nre-rendering a component).",
+      "itemtype": "method",
+      "name": "setComponentManager",
+      "params": [
+        {
+          "name": "factory",
+          "description": "a function to create the owner for an object",
+          "type": "Function"
+        },
+        {
+          "name": "obj",
+          "description": "the object to associate with the componetn manager",
+          "type": "Object"
+        }
+      ],
+      "return": {
+        "description": "the same object passed in",
+        "type": "Object"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "@ember/template",
+      "module": "ember"
+    },
     {
       "file": "packages/@ember/-internals/glimmer/lib/utils/outlet.ts",
       "line": 5,
@@ -6112,19 +6228,44 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 104,
+      "line": 107,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/views/outlet.ts",
-      "line": 112,
+      "line": 115,
       "class": "Component",
       "module": "@ember/template"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 756,
+      "line": 664,
+      "description": "Layout can be used to wrap content in a component.",
+      "itemtype": "property",
+      "name": "layout",
+      "type": "Function",
+      "access": "public",
+      "tagname": "",
+      "class": "Component",
+      "module": "@ember/component"
+    },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/component.ts",
+      "line": 672,
+      "description": "The name of the layout to lookup if no layout is provided.\nBy default `Component` will lookup a template with this name in\n`Ember.TEMPLATES` (a shared global object).",
+      "itemtype": "property",
+      "name": "layoutName",
+      "type": "String",
+      "default": "undefined",
+      "access": "private",
+      "tagname": "",
+      "class": "Component",
+      "module": "@ember/component"
+    },
+    {
+      "file": "packages/@ember/-internals/glimmer/lib/component.ts",
+      "line": 789,
       "description": "Normally, Ember's component model is \"write-only\". The component takes a\nbunch of attributes that it got passed in, and uses them to render its\ntemplate.\n\nOne nice thing about this model is that if you try to set a value to the\nsame thing as last time, Ember (through HTMLBars) will avoid doing any\nwork on the DOM.\n\nThis is not just a performance optimization. If an attribute has not\nchanged, it is important not to clobber the element's \"hidden state\".\nFor example, if you set an input's `value` to the same value as before,\nit will clobber selection state and cursor position. In other words,\nsetting an attribute is not **always** idempotent.\n\nThis method provides a way to read an element's attribute and also\nupdate the last value Ember knows about at the same time. This makes\nsetting an attribute idempotent.\n\nIn particular, what this means is that if you get an `<input>` element's\n`value` attribute and then re-render the template with the same value,\nit will avoid clobbering the cursor and selection position.\nSince most attribute sets are idempotent in the browser, you typically\ncan get away with reading attributes using jQuery, but the most reliable\nway to do so is through this method.",
       "itemtype": "method",
       "name": "readDOMAttr",
@@ -6145,7 +6286,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 807,
+      "line": 840,
       "description": "The WAI-ARIA role of the control represented by this view. For example, a\nbutton may have a role of type 'button', or a pane may have a role of\ntype 'alertdialog'. This property is used by assistive software to help\nvisually challenged users navigate rich web applications.\n\nThe full list of valid WAI-ARIA roles is available at:\n[https://www.w3.org/TR/wai-aria/#roles_categorization](https://www.w3.org/TR/wai-aria/#roles_categorization)",
       "itemtype": "property",
       "name": "ariaRole",
@@ -6158,7 +6299,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 822,
+      "line": 855,
       "description": "Enables components to take a list of parameters as arguments.\nFor example, a component that takes two parameters with the names\n`name` and `age`:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nlet MyComponent = Component.extend();\n\nMyComponent.reopenClass({\n  positionalParams: ['name', 'age']\n});\n\nexport default MyComponent;\n```\n\nIt can then be invoked like this:\n\n```hbs\n{{my-component \"John\" 38}}\n```\n\nThe parameters can be referred to just like named parameters:\n\n```hbs\nName: {{name}}, Age: {{age}}.\n```\n\nUsing a string instead of an array allows for an arbitrary number of\nparameters:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nlet MyComponent = Component.extend();\n\nMyComponent.reopenClass({\n  positionalParams: 'names'\n});\n\nexport default MyComponent;\n```\n\nIt can then be invoked like this:\n\n```hbs\n{{my-component \"John\" \"Michael\" \"Scott\"}}\n```\nThe parameters can then be referred to by enumerating over the list:\n\n```hbs\n{{#each names as |name|}}{{name}}{{/each}}\n```",
       "static": 1,
       "access": "public",
@@ -6171,7 +6312,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 883,
+      "line": 916,
       "description": "Called when the attributes passed into the component have been updated.\nCalled both during the initial render of a container and during a rerender.\nCan be used in place of an observer; code placed here will be executed\nevery time any attribute updates.",
       "itemtype": "method",
       "name": "didReceiveAttrs",
@@ -6183,7 +6324,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 894,
+      "line": 927,
       "description": "Called when the attributes passed into the component have been updated.\nCalled both during the initial render of a container and during a rerender.\nCan be used in place of an observer; code placed here will be executed\nevery time any attribute updates.",
       "itemtype": "event",
       "name": "didReceiveAttrs",
@@ -6195,7 +6336,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 904,
+      "line": 937,
       "description": "Called after a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "method",
       "name": "didRender",
@@ -6207,7 +6348,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 913,
+      "line": 946,
       "description": "Called after a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "event",
       "name": "didRender",
@@ -6219,7 +6360,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 921,
+      "line": 954,
       "description": "Called before a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "method",
       "name": "willRender",
@@ -6231,7 +6372,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 930,
+      "line": 963,
       "description": "Called before a component has been rendered, both on initial render and\nin subsequent rerenders.",
       "itemtype": "event",
       "name": "willRender",
@@ -6243,7 +6384,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 938,
+      "line": 971,
       "description": "Called when the attributes passed into the component have been changed.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdateAttrs",
@@ -6255,7 +6396,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 947,
+      "line": 980,
       "description": "Called when the attributes passed into the component have been changed.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdateAttrs",
@@ -6267,7 +6408,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 955,
+      "line": 988,
       "description": "Called when the component is about to update and rerender itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "willUpdate",
@@ -6279,7 +6420,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 964,
+      "line": 997,
       "description": "Called when the component is about to update and rerender itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "willUpdate",
@@ -6291,7 +6432,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 972,
+      "line": 1005,
       "description": "Called when the component has updated and rerendered itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "method",
       "name": "didUpdate",
@@ -6303,7 +6444,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 981,
+      "line": 1014,
       "description": "Called when the component has updated and rerendered itself.\nCalled only during a rerender, not during an initial render.",
       "itemtype": "event",
       "name": "didUpdate",
@@ -6315,32 +6456,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 989,
-      "description": "Layout can be used to wrap content in a component.",
-      "itemtype": "property",
-      "name": "layout",
-      "type": "Function",
-      "access": "public",
-      "tagname": "",
-      "class": "Component",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 996,
-      "description": "The name of the layout to lookup if no layout is provided.\nBy default `Component` will lookup a template with this name in\n`Ember.TEMPLATES` (a shared global object).",
-      "itemtype": "property",
-      "name": "layoutName",
-      "type": "String",
-      "default": "null",
-      "access": "private",
-      "tagname": "",
-      "class": "Component",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/component.ts",
-      "line": 1006,
+      "line": 1022,
       "description": "The HTML `id` of the component's element in the DOM. You can provide this\nvalue yourself but it must be unique (just as in HTML):\n\n```handlebars\n{{my-component elementId=\"a-really-cool-id\"}}\n```\n\n```handlebars\n<MyComponent @elementId=\"a-really-cool-id\" />\n```\nIf not manually set a default value will be provided by the framework.\nOnce rendered an element's `elementId` is considered immutable and you\nshould never change it. If you need to compute a dynamic value for the\n`elementId`, you should do this when the component or element is being\ninstantiated:\n\n```javascript\nexport default Component.extend({\n  init() {\n    this._super(...arguments);\n\n    var index = this.get('index');\n    this.set('elementId', `component-id${index}`);\n  }\n});\n```",
       "itemtype": "property",
       "name": "elementId",
@@ -6364,7 +6480,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 83,
+      "line": 89,
       "description": "Override this function when writing a class-based helper.",
       "itemtype": "method",
       "name": "compute",
@@ -6388,7 +6504,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 103,
+      "line": 109,
       "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",
@@ -6400,7 +6516,7 @@
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
-      "line": 239,
+      "line": 246,
       "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": [
@@ -7098,7 +7214,7 @@
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
       "line": 160,
-      "access": "private",
+      "access": "public",
       "tagname": "",
       "itemtype": "method",
       "name": "hasListeners",
@@ -7205,7 +7321,7 @@
     {
       "file": "packages/@ember/-internals/metal/lib/is_blank.ts",
       "line": 5,
-      "description": "A value is blank if it is empty or a whitespace string.\n\n```javascript\nimport { isBlank } from '@ember/utils';\n\nisBlank();                // true\nisBlank(null);            // true\nisBlank(undefined);       // true\nisBlank('');              // true\nisBlank([]);              // true\nisBlank('\\n\\t');          // true\nisBlank('  ');            // true\nisBlank({});              // false\nisBlank('\\n\\t Hello');    // false\nisBlank('Hello world');   // false\nisBlank([1,2,3]);         // false\n```",
+      "description": "A value is blank if it is empty or a whitespace string.\n\n```javascript\nimport { isBlank } from '@ember/utils';\n\nisBlank(null);            // true\nisBlank(undefined);       // true\nisBlank('');              // true\nisBlank([]);              // true\nisBlank('\\n\\t');          // true\nisBlank('  ');            // true\nisBlank({});              // false\nisBlank('\\n\\t Hello');    // false\nisBlank('Hello world');   // false\nisBlank([1,2,3]);         // false\n```",
       "itemtype": "method",
       "name": "isBlank",
       "static": 1,
@@ -7229,7 +7345,7 @@
     {
       "file": "packages/@ember/-internals/metal/lib/is_empty.ts",
       "line": 5,
-      "description": "Verifies that a value is `null` or `undefined`, an empty string, or an empty\narray.\n\nConstrains the rules on `isNone` by returning true for empty strings and\nempty arrays.\n\nIf the value is an object with a `size` property of type number, it is used\nto check emptiness.\n\n```javascript\nisEmpty();                 // true\nisEmpty(null);             // true\nisEmpty(undefined);        // true\nisEmpty('');               // true\nisEmpty([]);               // true\nisEmpty({ size: 0});       // true\nisEmpty({});               // false\nisEmpty('Adam Hawkins');   // false\nisEmpty([0,1,2]);          // false\nisEmpty('\\n\\t');           // false\nisEmpty('  ');             // false\nisEmpty({ size: 1 })       // false\nisEmpty({ size: () => 0 }) // false\n```",
+      "description": "Verifies that a value is `null` or `undefined`, an empty string, or an empty\narray.\n\nConstrains the rules on `isNone` by returning true for empty strings and\nempty arrays.\n\nIf the value is an object with a `size` property of type number, it is used\nto check emptiness.\n\n```javascript\nisEmpty(null);             // true\nisEmpty(undefined);        // true\nisEmpty('');               // true\nisEmpty([]);               // true\nisEmpty({ size: 0});       // true\nisEmpty({});               // false\nisEmpty('Adam Hawkins');   // false\nisEmpty([0,1,2]);          // false\nisEmpty('\\n\\t');           // false\nisEmpty('  ');             // false\nisEmpty({ size: 1 })       // false\nisEmpty({ size: () => 0 }) // false\n```",
       "itemtype": "method",
       "name": "isEmpty",
       "static": 1,
@@ -7252,7 +7368,7 @@
     {
       "file": "packages/@ember/-internals/metal/lib/is_none.ts",
       "line": 4,
-      "description": "Returns true if the passed value is null or undefined. This avoids errors\nfrom JSLint complaining about use of ==, which can be technically\nconfusing.\n\n```javascript\nisNone();              // true\nisNone(null);          // true\nisNone(undefined);     // true\nisNone('');            // false\nisNone([]);            // false\nisNone(function() {}); // false\n```",
+      "description": "Returns true if the passed value is null or undefined. This avoids errors\nfrom JSLint complaining about use of ==, which can be technically\nconfusing.\n\n```javascript\nisNone(null);          // true\nisNone(undefined);     // true\nisNone('');            // false\nisNone([]);            // false\nisNone(function() {}); // false\n```",
       "itemtype": "method",
       "name": "isNone",
       "static": 1,
@@ -7275,7 +7391,7 @@
     {
       "file": "packages/@ember/-internals/metal/lib/is_present.ts",
       "line": 5,
-      "description": "A value is present if it not `isBlank`.\n\n```javascript\nisPresent();                // false\nisPresent(null);            // false\nisPresent(undefined);       // false\nisPresent('');              // false\nisPresent('  ');            // false\nisPresent('\\n\\t');          // false\nisPresent([]);              // false\nisPresent({ length: 0 });   // false\nisPresent(false);           // true\nisPresent(true);            // true\nisPresent('string');        // true\nisPresent(0);               // true\nisPresent(function() {});   // true\nisPresent({});              // true\nisPresent('\\n\\t Hello');    // true\nisPresent([1, 2, 3]);       // true\n```",
+      "description": "A value is present if it not `isBlank`.\n\n```javascript\nisPresent(null);            // false\nisPresent(undefined);       // false\nisPresent('');              // false\nisPresent('  ');            // false\nisPresent('\\n\\t');          // false\nisPresent([]);              // false\nisPresent({ length: 0 });   // false\nisPresent(false);           // true\nisPresent(true);            // true\nisPresent('string');        // true\nisPresent(0);               // true\nisPresent(function() {});   // true\nisPresent({});              // true\nisPresent('\\n\\t Hello');    // true\nisPresent([1, 2, 3]);       // true\n```",
       "itemtype": "method",
       "name": "isPresent",
       "static": 1,
@@ -7689,7 +7805,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/property_get.ts",
-      "line": 41,
+      "line": 42,
       "description": "Gets the value of a property on an object. If the property is computed,\nthe function will be invoked. If the property is not defined but the\nobject implements the `unknownProperty` method then that will be invoked.\n\n```javascript\nimport { get } from '@ember/object';\nget(obj, \"name\");\n```\n\nIf you plan to run on IE8 and older browsers then you should use this\nmethod anytime you want to retrieve a property on an object that you don't\nknow for sure is private. (Properties beginning with an underscore '_'\nare considered private.)\n\nOn all newer browsers, you only need to use this method to retrieve\nproperties if the property might not be defined on the object and you want\nto respect the `unknownProperty` handler. Otherwise you can ignore this\nmethod.\n\nNote that if the object itself is `undefined`, this method will throw\nan error.",
       "itemtype": "method",
       "name": "get",
@@ -8553,7 +8669,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 141,
+      "line": 140,
       "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.\n\nCalling `replaceWith` from the Router service will cause default query parameter values to be included in the URL.\nThis behavior is different from calling `replaceWith` on a route.\nSee the [Router Service RFC](https://github.com/emberjs/rfcs/blob/master/text/0095-router-service.md#query-parameter-semantics) for more info.\n\nUsage example:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\n\nexport default class extends Route {\n  beforeModel() {\n    if (!authorized()){\n      this.replaceWith('unauthorized');\n    }\n  }\n});\n```",
       "itemtype": "method",
       "name": "replaceWith",
@@ -8586,7 +8702,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 180,
+      "line": 179,
       "description": "Generate a URL based on the supplied route name and optionally a model. The\nURL is returned as a string that can be used for any purpose.\n\nIn this example, the URL for the `author.books` route for a given author\nis copied to the clipboard.\n\n```app/templates/application.hbs\n<CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n```\n\n```app/components/copy-link.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\nimport { action } from '@ember/object';\n\nexport default class CopyLinkComponent extends Component {\n  @service router;\n  @service clipboard;\n\n  @action\n  copyBooksURL() {\n    if (this.author) {\n      const url = this.router.urlFor('author.books', this.args.author);\n      this.clipboard.set(url);\n      // Clipboard now has /author/tomster/books\n    }\n  }\n}\n```\n\nJust like with `transitionTo` and `replaceWith`, `urlFor` can also handle\nquery parameters.\n\n```app/templates/application.hbs\n<CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n```\n\n```app/components/copy-link.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\nimport { action } from '@ember/object';\n\nexport default class CopyLinkComponent extends Component {\n  @service router;\n  @service clipboard;\n\n  @action\n  copyOnlyEmberBooksURL() {\n    if (this.author) {\n      const url = this.router.urlFor('author.books', this.author, {\n        queryParams: { filter: 'emberjs' }\n      });\n      this.clipboard.set(url);\n      // Clipboard now has /author/tomster/books?filter=emberjs\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "urlFor",
@@ -8619,7 +8735,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 253,
+      "line": 252,
       "description": "Returns `true` if `routeName/models/queryParams` is the active route, where `models` and `queryParams` are optional.\nSee [model](api/ember/release/classes/Route/methods/model?anchor=model) and\n[queryParams](/api/ember/3.7/classes/Route/properties/queryParams?anchor=queryParams) for more information about these arguments.\n\nIn the following example, `isActive` will return `true` if the current route is `/posts`.\n\n```app/components/posts.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  displayComments() {\n    return this.router.isActive('posts');\n  }\n});\n```\n\nThe next example includes a dynamic segment, and will return `true` if the current route is `/posts/1`,\nassuming the post has an id of 1:\n\n```app/components/posts.js\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  displayComments(post) {\n    return this.router.isActive('posts', post.id);\n  }\n});\n```\n\nWhere `post.id` is the id of a specific post, which is represented in the route as /posts/[post.id].\nIf `post.id` is equal to 1, then isActive will return true if the current route is /posts/1, and false if the route is anything else.",
       "itemtype": "method",
       "name": "isActive",
@@ -8652,7 +8768,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 347,
+      "line": 356,
       "description": "Takes a string URL and returns a `RouteInfo` for the leafmost route represented\nby the URL. Returns `null` if the URL is not recognized. This method expects to\nreceive the actual URL as seen by the browser including the app's `rootURL`.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nIn the following example `recognize` is used to verify if a path belongs to our\napplication before transitioning to it.\n\n```\nimport Component from '@ember/component';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n  path = '/';\n\n  click() {\n    if (this.router.recognize(this.path)) {\n      this.router.transitionTo(this.path);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "recognize",
@@ -8674,7 +8790,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 388,
+      "line": 397,
       "description": "Takes a string URL and returns a promise that resolves to a\n`RouteInfoWithAttributes` for the leafmost route represented by the URL.\nThe promise rejects if the URL is not recognized or an unhandled exception\nis encountered. This method expects to receive the actual URL as seen by\nthe browser including the app's `rootURL`.",
       "itemtype": "method",
       "name": "recognizeAndLoad",
@@ -8696,8 +8812,54 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 410,
-      "description": "The `routeWillChange` event is fired at the beginning of any\nattempted transition with a `Transition` object as the sole\nargument. This action can be used for aborting, redirecting,\nor decorating the transition from the currently active routes.\n\nA good example is preventing navigation when a form is\nhalf-filled out:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  constructor() {\n    super(...arguments);\n\n    this.router.on('routeWillChange', (transition) => {\n      if (!transition.to.find(route => route.name === this.routeName)) {\n        alert(\"Please save or cancel your changes.\");\n        transition.abort();\n      }\n    })\n  }\n}\n```\n\nThe `routeWillChange` event fires whenever a new route is chosen as the desired target of a transition. This includes `transitionTo`, `replaceWith`, all redirection for any reason including error handling, and abort. Aborting implies changing the desired target back to where you already were. Once a transition has completed, `routeDidChange` fires.",
+      "line": 419,
+      "description": "You can register a listener for events emitted by this service with `.on()`:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeWillChange', (transition) => {\n      if (!transition.to.find(route => route.name === this.routeName)) {\n        alert(\"Please save or cancel your changes.\");\n        transition.abort();\n      }\n    })\n  }\n}\n```",
+      "itemtype": "method",
+      "name": "on",
+      "params": [
+        {
+          "name": "eventName",
+          "description": "",
+          "type": "String"
+        },
+        {
+          "name": "callback",
+          "description": "",
+          "type": "Function"
+        }
+      ],
+      "access": "public",
+      "tagname": "",
+      "class": "RouterService",
+      "module": "@ember/routing"
+    },
+    {
+      "file": "packages/@ember/-internals/routing/lib/services/router.ts",
+      "line": 446,
+      "description": "You can unregister a listener for events emitted by this service with `.off()`:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  callback = (transition) =>  {\n    if (!transition.to.find(route => route.name === this.routeName)) {\n      alert(\"Please save or cancel your changes.\");\n      transition.abort();\n    }\n  };\n\n  activate() {\n    this.router.on('routeWillChange', this.callback);\n  }\n\n  deactivate() {\n    this.router.off('routeWillChange', this.callback);\n}\n```",
+      "itemtype": "method",
+      "name": "off",
+      "params": [
+        {
+          "name": "eventName",
+          "description": "",
+          "type": "String"
+        },
+        {
+          "name": "callback",
+          "description": "",
+          "type": "Function"
+        }
+      ],
+      "access": "public",
+      "tagname": "",
+      "class": "RouterService",
+      "module": "@ember/routing"
+    },
+    {
+      "file": "packages/@ember/-internals/routing/lib/services/router.ts",
+      "line": 478,
+      "description": "The `routeWillChange` event is fired at the beginning of any\nattempted transition with a `Transition` object as the sole\nargument. This action can be used for aborting, redirecting,\nor decorating the transition from the currently active routes.\n\nA good example is preventing navigation when a form is\nhalf-filled out:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeWillChange', (transition) => {\n      if (!transition.to.find(route => route.name === this.routeName)) {\n        alert(\"Please save or cancel your changes.\");\n        transition.abort();\n      }\n    })\n  }\n}\n```\n\nThe `routeWillChange` event fires whenever a new route is chosen as the desired target of a transition. This includes `transitionTo`, `replaceWith`, all redirection for any reason including error handling, and abort. Aborting implies changing the desired target back to where you already were. Once a transition has completed, `routeDidChange` fires.",
       "itemtype": "event",
       "name": "routeWillChange",
       "params": [
@@ -8714,8 +8876,8 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 446,
-      "description": "The `routeDidChange` event only fires once a transition has settled.\nThis includes aborts and error substates. Like the `routeWillChange` event\nit receives a Transition as the sole argument.\n\nA good example is sending some analytics when the route has transitioned:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  constructor() {\n    super(...arguments);\n\n    this.router.on('routeDidChange', (transition) => {\n      ga.send('pageView', {\n        current: transition.to.name,\n        from: transition.from.name\n      });\n    })\n  }\n}\n```\n\n`routeDidChange` will be called after any `Route`'s\n[didTransition](/ember/release/classes/Route/events/didTransition?anchor=didTransition)\naction has been fired.\nThe updates of properties\n[currentURL](/ember/release/classes/RouterService/properties/currentURL?anchor=currentURL),\n[currentRouteName](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRouteName)\nand\n[currentRoute](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRoute)\nare completed at the time `routeDidChange` is called.",
+      "line": 512,
+      "description": "The `routeDidChange` event only fires once a transition has settled.\nThis includes aborts and error substates. Like the `routeWillChange` event\nit receives a Transition as the sole argument.\n\nA good example is sending some analytics when the route has transitioned:\n\n```app/routes/contact-form.js\nimport Route from '@ember/routing';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n\n  activate() {\n    this.router.on('routeDidChange', (transition) => {\n      ga.send('pageView', {\n        current: transition.to.name,\n        from: transition.from.name\n      });\n    })\n  }\n}\n```\n\n`routeDidChange` will be called after any `Route`'s\n[didTransition](/ember/release/classes/Route/events/didTransition?anchor=didTransition)\naction has been fired.\nThe updates of properties\n[currentURL](/ember/release/classes/RouterService/properties/currentURL?anchor=currentURL),\n[currentRouteName](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRouteName)\nand\n[currentRoute](/ember/release/classes/RouterService/properties/currentURL?anchor=currentRoute)\nare completed at the time `routeDidChange` is called.",
       "itemtype": "event",
       "name": "routeDidChange",
       "params": [
@@ -8732,7 +8894,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 489,
+      "line": 553,
       "description": "Refreshes all currently active routes, doing a full transition.\nIf a route name is provided and refers to a currently active route,\nit will refresh only that route and its descendents.\nReturns a promise that will be resolved once the refresh is complete.\nAll resetController, beforeModel, model, afterModel, redirect, and setupController\nhooks will be called again. You will get new data from the model hook.",
       "itemtype": "method",
       "name": "refresh",
@@ -8757,7 +8919,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 526,
+      "line": 590,
       "description": "Name of the current route.\n\n This property represents the logical name of the route,\n which is comma separated.\n For the following router:\n\n ```app/router.js\n Router.map(function() {\n   this.route('about');\n   this.route('blog', function () {\n     this.route('post', { path: ':post_id' });\n   });\n });\n ```\n\n It will return:\n\n * `index` when you visit `/`\n * `about` when you visit `/about`\n * `blog.index` when you visit `/blog`\n * `blog.post` when you visit `/blog/some-post-id`",
       "itemtype": "property",
       "name": "currentRouteName",
@@ -8769,7 +8931,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 556,
+      "line": 620,
       "description": "Current URL for the application.\n\n  This property represents the URL path for this route.\n  For the following router:\n\n ```app/router.js\n Router.map(function() {\n   this.route('about');\n   this.route('blog', function () {\n     this.route('post', { path: ':post_id' });\n   });\n });\n ```\n\n It will return:\n\n * `/` when you visit `/`\n * `/about` when you visit `/about`\n * `/blog` when you visit `/blog`\n * `/blog/some-post-id` when you visit `/blog/some-post-id`",
       "itemtype": "property",
       "name": "currentURL",
@@ -8781,7 +8943,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 585,
+      "line": 649,
       "description": "The `location` property returns what implementation of the `location` API\nyour application is using, which determines what type of URL is being used.\n\nSee [Location](/ember/release/classes/Location) for more information.\n\nTo force a particular `location` API implementation to be used in your\napplication you can set a location type on your `config/environment`.\nFor example, to set the `history` type:\n\n```config/environment.js\n'use strict';\n\nmodule.exports = function(environment) {\n  let ENV = {\n    modulePrefix: 'router-service',\n    environment,\n    rootURL: '/',\n    locationType: 'history',\n    ...\n  }\n}\n```\n\nThe following location types are available by default:\n`auto`, `hash`, `history`, `none`.\n\nSee [HashLocation](/ember/release/classes/HashLocation).\nSee [HistoryLocation](/ember/release/classes/HistoryLocation).\nSee [NoneLocation](/ember/release/classes/NoneLocation).\nSee [AutoLocation](/ember/release/classes/AutoLocation).",
       "itemtype": "property",
       "name": "location",
@@ -8796,7 +8958,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 625,
+      "line": 689,
       "description": "The `rootURL` property represents the URL of the root of\nthe application, '/' by default.\nThis prefix is assumed on all routes defined on this app.\n\nIf you change the `rootURL` in your environment configuration\nlike so:\n\n```config/environment.js\n'use strict';\n\nmodule.exports = function(environment) {\n  let ENV = {\n    modulePrefix: 'router-service',\n    environment,\n    rootURL: '/my-root',\n  …\n  }\n]\n```\n\nThis property will return `/my-root`.",
       "itemtype": "property",
       "name": "rootURL",
@@ -8808,7 +8970,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/services/router.ts",
-      "line": 655,
+      "line": 719,
       "description": "The `currentRoute` property contains metadata about the current leaf route.\nIt returns a `RouteInfo` object that has information like the route name,\nparams, query params and more.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nThis property is guaranteed to change whenever a route transition\nhappens (even when that transition only changes parameters\nand doesn't change the active route).\n\nUsage example:\n```app/components/header.js\n  import Component from '@glimmer/component';\n  import { service } from '@ember/service';\n  import { notEmpty } from '@ember/object/computed';\n\n  export default class extends Component {\n    @service router;\n\n    @notEmpty('router.currentRoute.child') isChildRoute;\n  });\n```",
       "itemtype": "property",
       "name": "currentRoute",
@@ -10128,7 +10290,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 148,
+      "line": 149,
       "description": "Represents the URL of the root of the application, often '/'. This prefix is\n assumed on all routes defined on this router.",
       "itemtype": "property",
       "name": "rootURL",
@@ -10140,7 +10302,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 159,
+      "line": 160,
       "description": "The `location` property determines the type of URL's that your\n application will use.\n\n The following location types are currently available:\n\n * `history` - use the browser's history API to make the URLs look just like any standard URL\n * `hash` - use `#` to separate the server part of the URL from the Ember part: `/blog/#/posts/new`\n * `none` - do not store the Ember URL in the actual browser URL (mainly used for testing)\n * `auto` - use the best option based on browser capabilities: `history` if possible, then `hash` if possible, otherwise `none`\n\n This value is defaulted to `auto` by the `locationType` setting of `/config/environment.js`",
       "itemtype": "property",
       "name": "location",
@@ -10155,7 +10317,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 217,
+      "line": 218,
       "description": "The `Router.map` function allows you to define mappings from URLs to routes\nin your application. These mappings are defined within the\nsupplied callback function using `this.route`.\n\nThe first parameter is the name of the route which is used by default as the\npath name as well.\n\nThe second parameter is the optional options hash. Available options are:\n\n  * `path`: allows you to provide your own path as well as mark dynamic\n    segments.\n  * `resetNamespace`: false by default; when nesting routes, ember will\n    combine the route names to form the fully-qualified route name, which is\n    used with `{{link-to}}` or manually transitioning to routes. Setting\n    `resetNamespace: true` will cause the route not to inherit from its\n    parent route's names. This is handy for preventing extremely long route names.\n    Keep in mind that the actual URL path behavior is still retained.\n\nThe third parameter is a function, which can be used to nest routes.\nNested routes, by default, will have the parent route tree's route name and\npath prepended to it's own.\n\n```app/router.js\nRouter.map(function(){\n  this.route('post', { path: '/post/:post_id' }, function() {\n    this.route('edit');\n    this.route('comments', { resetNamespace: true }, function() {\n      this.route('new');\n    });\n  });\n});\n```",
       "itemtype": "method",
       "name": "map",
@@ -10172,7 +10334,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 546,
+      "line": 547,
       "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",
@@ -10183,7 +10345,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 669,
+      "line": 670,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:",
       "itemtype": "method",
       "name": "transitionTo",
@@ -10217,7 +10379,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 714,
+      "line": 715,
       "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",
@@ -10251,7 +10413,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 741,
+      "line": 742,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -10272,7 +10434,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 753,
+      "line": 754,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -10302,7 +10464,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 775,
+      "line": 776,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -10317,7 +10479,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 786,
+      "line": 787,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -10328,7 +10490,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 932,
+      "line": 935,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10355,7 +10517,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 962,
+      "line": 965,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -10378,7 +10540,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 980,
+      "line": 983,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -10405,7 +10567,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1008,
+      "line": 1011,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -10428,7 +10590,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1029,
+      "line": 1032,
       "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": "",
@@ -10455,7 +10617,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1115,
+      "line": 1113,
       "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": "",
@@ -10492,7 +10654,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1142,
+      "line": 1140,
       "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": "",
@@ -10514,7 +10676,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1156,
+      "line": 1154,
       "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": "",
@@ -10536,7 +10698,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1218,
+      "line": 1216,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -10568,7 +10730,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1256,
+      "line": 1254,
       "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": "",
@@ -10595,7 +10757,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1427,
+      "line": 1425,
       "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",
@@ -10607,7 +10769,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1464,
+      "line": 1462,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
@@ -10619,7 +10781,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1477,
+      "line": 1475,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -10631,7 +10793,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1635,
+      "line": 1633,
       "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": "",
@@ -10656,7 +10818,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1656,
+      "line": 1654,
       "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": "",
@@ -10681,7 +10843,7 @@
     },
     {
       "file": "packages/@ember/-internals/routing/lib/system/router.ts",
-      "line": 1678,
+      "line": 1676,
       "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": "",
@@ -10974,6 +11136,19 @@
       "class": "Transition",
       "module": "@ember/routing"
     },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.d.ts",
+      "line": 6,
+      "description": "The object whose properties will be forwarded.",
+      "itemtype": "property",
+      "name": "content",
+      "type": "{unknown}",
+      "default": "null",
+      "access": "public",
+      "tagname": "",
+      "class": "Ember.ProxyMixin",
+      "module": "@ember/routing"
+    },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.js",
       "line": 64,
@@ -12031,7 +12206,7 @@
         {
           "name": "objects",
           "description": "the objects to add",
-          "type": "Enumberable"
+          "type": "Enumerable"
         }
       ],
       "return": {
@@ -12317,28 +12492,28 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/evented.d.ts",
-      "line": 16,
+      "line": 23,
       "description": "Subscribes a function to a named event and then cancels the subscription\nafter the first time the event is triggered. It is good to use ``one`` when\nyou only care about the first time an event has taken place.",
       "class": "Evented",
       "module": "@ember/enumerable"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/evented.d.ts",
-      "line": 27,
+      "line": 34,
       "description": "Triggers a named event for the object. Any additional arguments\nwill be passed as parameters to the functions that are subscribed to the\nevent.",
       "class": "Evented",
       "module": "@ember/enumerable"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/evented.d.ts",
-      "line": 33,
+      "line": 40,
       "description": "Cancels subscription for given name, target, and method.",
       "class": "Evented",
       "module": "@ember/enumerable"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/evented.d.ts",
-      "line": 42,
+      "line": 49,
       "description": "Checks to see if object has any subscriptions for named event.",
       "class": "Evented",
       "module": "@ember/enumerable"
@@ -13408,13 +13583,25 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 21,
+      "line": 14,
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 27,
+      "line": 17,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 22,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 24,
       "class": "CoreObject",
       "module": "@ember/array"
     },
@@ -13427,26 +13614,56 @@
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
       "line": 33,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 36,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 44,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 50,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 53,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 56,
       "description": "CoreObject constructor takes owner.",
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 38,
+      "line": 61,
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 41,
+      "line": 64,
       "description": "An overridable method called when objects are instantiated. By default,\ndoes nothing unless it is overridden during class definition.",
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 47,
+      "line": 70,
       "description": "Defines the properties that will be concatenated from the superclass (instead of overridden).",
       "default": "null",
       "class": "CoreObject",
@@ -13454,7 +13671,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 53,
+      "line": 76,
       "description": "Destroyed object property flag. If this property is true the observers and bindings were\nalready removed by the effect of calling the destroy() method.",
       "default": "false",
       "class": "CoreObject",
@@ -13462,7 +13679,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 59,
+      "line": 82,
       "description": "Destruction scheduled flag. The destroy() method has been called. The object stays intact\nuntil the end of the run loop at which point the isDestroyed flag is set.",
       "default": "false",
       "class": "CoreObject",
@@ -13470,7 +13687,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 66,
+      "line": 90,
       "description": "Destroys an object by setting the `isDestroyed` flag and removing its\nmetadata, which effectively destroys observers and bindings.\nIf you try to set a property on a destroyed object, an exception will be\nraised.\nNote that destruction is scheduled for the end of the run loop and does not\nhappen immediately.  It will set an isDestroying flag immediately.",
       "return": {
         "description": "receiver"
@@ -13480,14 +13697,14 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 77,
+      "line": 101,
       "description": "Override to implement teardown.",
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 82,
+      "line": 106,
       "description": "Returns a string representation which attempts to provide more information than Javascript's toString\ntypically does, in a generic way for all Ember objects (e.g., \"<App.Person:ember1024>\").",
       "return": {
         "description": "string representation"
@@ -13497,19 +13714,19 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 94,
+      "line": 118,
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 100,
+      "line": 124,
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 103,
+      "line": 127,
       "description": "Iterate over each computed property for the class, passing its name and any\nassociated metadata (see metaForProperty) to the callback.",
       "internal": "",
       "class": "CoreObject",
@@ -13517,7 +13734,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 109,
+      "line": 133,
       "description": "Returns the original hash that was passed to meta().",
       "params": [
         {
@@ -13531,13 +13748,19 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 116,
+      "line": 140,
       "class": "CoreObject",
       "module": "@ember/array"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
-      "line": 119,
+      "line": 143,
+      "class": "CoreObject",
+      "module": "@ember/array"
+    },
+    {
+      "file": "packages/@ember/-internals/runtime/lib/system/core_object.d.ts",
+      "line": 146,
       "class": "CoreObject",
       "module": "@ember/array"
     },
@@ -13791,8 +14014,8 @@
       "module": "@ember/application"
     },
     {
-      "file": "packages/@ember/-internals/runtime/lib/compare.js",
-      "line": 44,
+      "file": "packages/@ember/-internals/runtime/lib/compare.ts",
+      "line": 48,
       "description": "Compares two javascript values and returns:\n\n - -1 if the first is smaller than the second,\n - 0 if both are equal,\n - 1 if the first is greater than the second.\n\n ```javascript\n import { compare } from '@ember/utils';\n\n compare('hello', 'hello');  // 0\n compare('abc', 'dfg');      // -1\n compare(2, 1);              // 1\n ```\n\nIf the types of the two objects are different precedence occurs in the\nfollowing order, with types earlier in the list considered `<` types\nlater in the list:\n\n - undefined\n - null\n - boolean\n - number\n - string\n - array\n - object\n - instance\n - function\n - class\n - date\n\n ```javascript\n import { compare } from '@ember/utils';\n\n compare('hello', 50);       // 1\n compare(50, 'hello');       // -1\n ```",
       "itemtype": "method",
       "name": "compare",
@@ -13819,7 +14042,7 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@ember/-internals/runtime/lib/is-equal.js",
+      "file": "packages/@ember/-internals/runtime/lib/is-equal.ts",
       "line": 4,
       "description": "Compares two objects, returning true if they are equal.\n\n```javascript\nimport { isEqual } from '@ember/utils';\n\nisEqual('hello', 'hello');                   // true\nisEqual(1, 2);                               // false\n```\n\n`isEqual` is a more specific comparison than a triple equal comparison.\nIt will call the `isEqual` instance method on the objects being\ncompared, allowing finer control over when objects should be considered\nequal to each other.\n\n```javascript\nimport { isEqual } from '@ember/utils';\nimport EmberObject from '@ember/object';\n\nlet Person = EmberObject.extend({\n  isEqual(other) { return this.ssn == other.ssn; }\n});\n\nlet personA = Person.create({name: 'Muhammad Ali', ssn: '123-45-6789'});\nlet personB = Person.create({name: 'Cassius Clay', ssn: '123-45-6789'});\n\nisEqual(personA, personB); // true\n```\n\nDue to the expense of array comparisons, collections will never be equal to\neach other even if each of their items are equal to each other.\n\n```javascript\nimport { isEqual } from '@ember/utils';\n\nisEqual([4, 2], [4, 2]);                     // false\n```",
       "itemtype": "method",
@@ -13847,8 +14070,8 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@ember/-internals/runtime/lib/type-of.js",
-      "line": 24,
+      "file": "packages/@ember/-internals/runtime/lib/type-of.ts",
+      "line": 40,
       "description": "Returns a consistent type for the passed object.\n\nUse this instead of the built-in `typeof` to get the type of an item.\nIt will return the same result across all browsers and includes a bit\nmore detail. Here is what will be returned:\n\n    | Return Value  | Meaning                                              |\n    |---------------|------------------------------------------------------|\n    | 'string'      | String primitive or String object.                   |\n    | 'number'      | Number primitive or Number object.                   |\n    | 'boolean'     | Boolean primitive or Boolean object.                 |\n    | 'null'        | Null value                                           |\n    | 'undefined'   | Undefined value                                      |\n    | 'function'    | A function                                           |\n    | 'array'       | An instance of Array                                 |\n    | 'regexp'      | An instance of RegExp                                |\n    | 'date'        | An instance of Date                                  |\n    | 'filelist'    | An instance of FileList                              |\n    | 'class'       | An Ember class (created using EmberObject.extend())  |\n    | 'instance'    | An Ember object instance                             |\n    | 'error'       | An instance of the Error object                      |\n    | 'object'      | A JavaScript object not inheriting from EmberObject  |\n\nExamples:\n\n```javascript\nimport { A } from '@ember/array';\nimport { typeOf } from '@ember/utils';\nimport EmberObject from '@ember/object';\n\ntypeOf();                       // 'undefined'\ntypeOf(null);                   // 'null'\ntypeOf(undefined);              // 'undefined'\ntypeOf('michael');              // 'string'\ntypeOf(new String('michael'));  // 'string'\ntypeOf(101);                    // 'number'\ntypeOf(new Number(101));        // 'number'\ntypeOf(true);                   // 'boolean'\ntypeOf(new Boolean(true));      // 'boolean'\ntypeOf(A);                      // 'function'\ntypeOf(A());                    // 'array'\ntypeOf([1, 2, 90]);             // 'array'\ntypeOf(/abc/);                  // 'regexp'\ntypeOf(new Date());             // 'date'\ntypeOf(event.target.files);     // 'filelist'\ntypeOf(EmberObject.extend());   // 'class'\ntypeOf(EmberObject.create());   // 'instance'\ntypeOf(new Error('teamocil'));  // 'error'\n\n// 'normal' JavaScript object\ntypeOf({ a: 'b' });             // 'object'\n```",
       "itemtype": "method",
       "name": "typeOf",
@@ -14405,6 +14628,12 @@
       "class": "Ember.EventDispatcher",
       "module": "ember"
     },
+    {
+      "file": "packages/@ember/-internals/views/lib/system/event_dispatcher.d.ts",
+      "line": 8,
+      "class": "Ember.EventDispatcher",
+      "module": "ember"
+    },
     {
       "file": "packages/@ember/-internals/views/lib/system/event_dispatcher.js",
       "line": 27,
@@ -14518,7 +14747,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 41,
+      "line": 35,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14535,7 +14764,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 63,
+      "line": 57,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14552,7 +14781,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 83,
+      "line": 77,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14569,7 +14798,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 115,
+      "line": 109,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14586,7 +14815,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 158,
+      "line": 152,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14603,7 +14832,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 167,
+      "line": 161,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -14620,7 +14849,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 182,
+      "line": 176,
       "description": "`getViewClientRects` provides information about the position of the border\nbox edges of a view relative to the viewport.\n\nIt is only intended to be used by development tools like the Ember Inspector\nand may not work on older browsers.",
       "access": "private",
       "tagname": "",
@@ -14638,7 +14867,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 198,
+      "line": 192,
       "description": "`getViewBoundingClientRect` provides information about the position of the\nbounding border box edges of a view relative to the viewport.\n\nIt is only intended to be used by development tools like the Ember Inspector\nand may not work on older browsers.",
       "access": "private",
       "tagname": "",
@@ -14656,7 +14885,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/system/utils.ts",
-      "line": 214,
+      "line": 208,
       "description": "Determines if the element matches the specified selector.",
       "access": "private",
       "tagname": "",
@@ -14678,8 +14907,8 @@
       "module": "ember"
     },
     {
-      "file": "packages/@ember/-internals/views/lib/views/core_view.js",
-      "line": 34,
+      "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
+      "line": 39,
       "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",
@@ -14692,8 +14921,8 @@
       "namespace": "Ember"
     },
     {
-      "file": "packages/@ember/-internals/views/lib/views/core_view.js",
-      "line": 52,
+      "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
+      "line": 57,
       "description": "Override the default event firing from `Evented` to\nalso call methods with the given name.",
       "itemtype": "method",
       "name": "trigger",
@@ -14710,6 +14939,13 @@
       "module": "ember",
       "namespace": "Ember"
     },
+    {
+      "file": "packages/@ember/application/lib/application.d.ts",
+      "line": 17,
+      "class": "Application",
+      "module": "ember",
+      "namespace": "Ember"
+    },
     {
       "file": "packages/@ember/application/lib/application.js",
       "line": 185,
@@ -15307,7 +15543,7 @@
     },
     {
       "file": "packages/@ember/canary-features/index.ts",
-      "line": 32,
+      "line": 33,
       "description": "Determine whether the specified `feature` is enabled. Used by Ember's\nbuild tools to exclude experimental features from beta/stable builds.\n\nYou can define the following configuration options:\n\n* `EmberENV.ENABLE_OPTIONAL_FEATURES` - enable any features that have not been explicitly\n  enabled/disabled.",
       "itemtype": "method",
       "name": "isEnabled",
@@ -15450,7 +15686,7 @@
     },
     {
       "file": "packages/@ember/debug/lib/deprecate.ts",
-      "line": 177,
+      "line": 181,
       "description": "Display a deprecation warning with the provided message and a stack trace\n(Chrome and Firefox only).\n\n* In a production build, this method is defined as an empty function (NOP).\nUses of this method in Ember itself are stripped from the ember.prod.js build.",
       "itemtype": "method",
       "name": "deprecate",
@@ -17311,8 +17547,23 @@
       "module": "@ember/polyfills"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 31,
+      "file": "packages/@ember/renderer/index.ts",
+      "line": 11,
+      "description": "Returns a promise which will resolve when rendering has settled. Settled in\nthis context is defined as when all of the tags in use are \"current\" (e.g.\n`renderers.every(r => r._isValid())`). When this is checked at the _end_ of\nthe run loop, this essentially guarantees that all rendering is completed.",
+      "itemtype": "method",
+      "name": "renderSettled",
+      "return": {
+        "description": "a promise which fulfills when rendering has settled",
+        "type": "Promise<void>"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "Renderer",
+      "module": "@ember/renderer"
+    },
+    {
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 60,
       "description": "Array of named queues. This array determines the order in which queues\nare flushed at the end of the RunLoop. You can define your own queues by\nsimply adding the queue name to this array. Normally you should not need\nto inspect or modify this property.",
       "itemtype": "property",
       "name": "queues",
@@ -17321,11 +17572,11 @@
       "access": "private",
       "tagname": "",
       "class": "@ember/runloop",
-      "module": "@ember/polyfills"
+      "module": "@ember/renderer"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 74,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 103,
       "description": "Runs the passed target and method inside of a RunLoop, ensuring any\ndeferred actions including bindings and views updates are flushed at the\nend.\n\nNormally you should not need to invoke this method yourself. However if\nyou are implementing raw event handlers when interfacing with other\nlibraries or plugins, you should probably wrap all of your code inside this\ncall.\n\n```javascript\nimport { run } from '@ember/runloop';\n\nrun(function() {\n  // code to be executed within a RunLoop\n});\n```",
       "itemtype": "method",
       "name": "run",
@@ -17359,8 +17610,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 106,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 151,
       "description": "If no run-loop is present, it creates a new one. If a run loop is\npresent it will queue itself to run on the existing run-loops action\nqueue.\n\nPlease note: This is not for normal usage, and should be used sparingly.\n\nIf invoked when not within a run loop:\n\n```javascript\nimport { join } from '@ember/runloop';\n\njoin(function() {\n  // creates a new run-loop\n});\n```\n\nAlternatively, if called within an existing run loop:\n\n```javascript\nimport { run, join } from '@ember/runloop';\n\nrun(function() {\n  // creates a new run-loop\n\n  join(function() {\n    // joins with the existing run-loop, and queues for invocation on\n    // the existing run-loops action queue.\n  });\n});\n```",
       "itemtype": "method",
       "name": "join",
@@ -17394,8 +17645,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 154,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 213,
       "description": "Allows you to specify which context to call the specified function in while\nadding the execution of that function to the Ember run loop. This ability\nmakes this method a great way to asynchronously integrate third-party libraries\ninto your Ember application.\n\n`bind` takes two main arguments, the desired context and the function to\ninvoke in that context. Any additional arguments will be supplied as arguments\nto the function that is passed in.\n\nLet's use the creation of a TinyMCE component as an example. Currently,\nTinyMCE provides a setup configuration option we can use to do some processing\nafter the TinyMCE instance is initialized but before it is actually rendered.\nWe can use that setup option to do some additional setup for our component.\nThe component itself could look something like the following:\n\n```app/components/rich-text-editor.js\nimport Component from '@ember/component';\nimport { on } from '@ember/object/evented';\nimport { bind } from '@ember/runloop';\n\nexport default Component.extend({\n  initializeTinyMCE: on('didInsertElement', function() {\n    tinymce.init({\n      selector: '#' + this.$().prop('id'),\n      setup: bind(this, this.setupEditor)\n    });\n  }),\n\n  didInsertElement() {\n    tinymce.init({\n      selector: '#' + this.$().prop('id'),\n      setup: bind(this, this.setupEditor)\n    });\n  }\n\n  setupEditor(editor) {\n    this.set('editor', editor);\n\n    editor.on('change', function() {\n      console.log('content changed!');\n    });\n  }\n});\n```\n\nIn this example, we use `bind` to bind the setupEditor method to the\ncontext of the RichTextEditor component and to have the invocation of that\nmethod be safely handled and executed by the Ember run loop.",
       "itemtype": "method",
       "name": "bind",
@@ -17430,8 +17681,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 241,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 327,
       "description": "Begins a new RunLoop. Any deferred actions invoked after the begin will\nbe buffered until you invoke a matching call to `end()`. This is\na lower-level way to use a RunLoop instead of using `run()`.\n\n```javascript\nimport { begin, end } from '@ember/runloop';\n\nbegin();\n// code to be executed within a RunLoop\nend();\n```",
       "itemtype": "method",
       "name": "begin",
@@ -17446,8 +17697,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 264,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 350,
       "description": "Ends a RunLoop. This must be called sometime after you call\n`begin()` to flush any deferred actions. This is a lower-level way\nto use a RunLoop instead of using `run()`.\n\n```javascript\nimport { begin, end } from '@ember/runloop';\n\nbegin();\n// code to be executed within a RunLoop\nend();\n```",
       "itemtype": "method",
       "name": "end",
@@ -17462,8 +17713,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 287,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 373,
       "description": "Adds the passed target/method and any optional arguments to the named\nqueue to be executed at the end of the RunLoop. If you have not already\nstarted a RunLoop when calling this method one will be started for you\nautomatically.\n\nAt the end of a RunLoop, any methods scheduled in this way will be invoked.\nMethods will be invoked in an order matching the named queues defined in\nthe `queues` property.\n\n```javascript\nimport { schedule } from '@ember/runloop';\n\nschedule('afterRender', this, function() {\n  // this will be executed in the 'afterRender' queue\n  console.log('scheduled on afterRender queue');\n});\n\nschedule('actions', this, function() {\n  // this will be executed in the 'actions' queue\n  console.log('scheduled on actions queue');\n});\n\n// Note the functions will be run in order based on the run queues order.\n// Output would be:\n//   scheduled on actions queue\n//   scheduled on afterRender queue\n```",
       "itemtype": "method",
       "name": "schedule",
@@ -17502,8 +17753,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 342,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 446,
       "description": "Invokes the passed target/method and optional arguments after a specified\nperiod of time. The last parameter of this method must always be a number\nof milliseconds.\n\nYou should use this method whenever you need to run some action after a\nperiod of time instead of using `setTimeout()`. This method will ensure that\nitems that expire during the same script execution cycle all execute\ntogether, which is often more efficient than using a real setTimeout.\n\n```javascript\nimport { later } from '@ember/runloop';\n\nlater(myContext, function() {\n  // code here will execute within a RunLoop in about 500ms with this == myContext\n}, 500);\n```",
       "itemtype": "method",
       "name": "later",
@@ -17542,8 +17793,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 376,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 497,
       "description": "Schedule a function to run one time during the current RunLoop. This is equivalent\n to calling `scheduleOnce` with the \"actions\" queue.",
       "itemtype": "method",
       "name": "once",
@@ -17577,8 +17828,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 396,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 528,
       "description": "Schedules a function to run one time in a given queue of the current RunLoop.\nCalling this method with the same queue/target/method combination will have\nno effect (past the initial call).\n\nNote that although you can pass optional arguments these will not be\nconsidered when looking for duplicates. New arguments will replace previous\ncalls.\n\n```javascript\nimport { run, scheduleOnce } from '@ember/runloop';\n\nfunction sayHi() {\n  console.log('hi');\n}\n\nrun(function() {\n  scheduleOnce('afterRender', myContext, sayHi);\n  scheduleOnce('afterRender', myContext, sayHi);\n  // sayHi will only be executed once, in the afterRender queue of the RunLoop\n});\n```\n\nAlso note that for `scheduleOnce` to prevent additional calls, you need to\npass the same function instance. The following case works as expected:\n\n```javascript\nfunction log() {\n  console.log('Logging only once');\n}\n\nfunction scheduleIt() {\n  scheduleOnce('actions', myContext, log);\n}\n\nscheduleIt();\nscheduleIt();\n```\n\nBut this other case will schedule the function multiple times:\n\n```javascript\nimport { scheduleOnce } from '@ember/runloop';\n\nfunction scheduleIt() {\n  scheduleOnce('actions', myContext, function() {\n    console.log('Closure');\n  });\n}\n\nscheduleIt();\nscheduleIt();\n\n// \"Closure\" will print twice, even though we're using `scheduleOnce`,\n// because the function we pass to it won't match the\n// previously scheduled operation.\n```\n\nAvailable queues, and their order, can be found at `queues`",
       "itemtype": "method",
       "name": "scheduleOnce",
@@ -17618,8 +17869,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 472,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 622,
       "description": "Schedules an item to run from within a separate run loop, after\ncontrol has been returned to the system. This is equivalent to calling\n`later` with a wait time of 1ms.\n\n```javascript\nimport { next } from '@ember/runloop';\n\nnext(myContext, function() {\n  // code to be executed in the next run loop,\n  // which will be scheduled after the current one\n});\n```\n\nMultiple operations scheduled with `next` will coalesce\ninto the same later run loop, along with any other operations\nscheduled by `later` that expire right around the same\ntime that `next` operations will fire.\n\nNote that there are often alternatives to using `next`.\nFor instance, if you'd like to schedule an operation to happen\nafter all DOM element operations have completed within the current\nrun loop, you can make use of the `afterRender` run loop queue (added\nby the `ember-views` package, along with the preceding `render` queue\nwhere all the DOM element operations happen).\n\nExample:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\nimport { scheduleOnce } from '@ember/runloop';\n\nexport Component.extend({\n  didInsertElement() {\n    this._super(...arguments);\n    scheduleOnce('afterRender', this, 'processChildElements');\n  },\n\n  processChildElements() {\n    // ... do something with component's child component\n    // elements after they've finished rendering, which\n    // can't be done within this component's\n    // `didInsertElement` hook because that gets run\n    // before the child elements have been added to the DOM.\n  }\n});\n```\n\nOne benefit of the above approach compared to using `next` is\nthat you will be able to perform DOM/CSS operations before unprocessed\nelements are rendered to the screen, which may prevent flickering or\nother artifacts caused by delaying processing until after rendering.\n\nThe other major benefit to the above approach is that `next`\nintroduces an element of non-determinism, which can make things much\nharder to test, due to its reliance on `setTimeout`; it's much harder\nto guarantee the order of scheduled operations when they are scheduled\noutside of the current run loop, i.e. with `next`.",
       "itemtype": "method",
       "name": "next",
@@ -17653,8 +17904,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 547,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 707,
       "description": "Cancels a scheduled item. Must be a value returned by `later()`,\n`once()`, `scheduleOnce()`, `next()`, `debounce()`, or\n`throttle()`.\n\n```javascript\nimport {\n  next,\n  cancel,\n  later,\n  scheduleOnce,\n  once,\n  throttle,\n  debounce\n} from '@ember/runloop';\n\nlet runNext = next(myContext, function() {\n  // will not be executed\n});\n\ncancel(runNext);\n\nlet runLater = later(myContext, function() {\n  // will not be executed\n}, 500);\n\ncancel(runLater);\n\nlet runScheduleOnce = scheduleOnce('afterRender', myContext, function() {\n  // will not be executed\n});\n\ncancel(runScheduleOnce);\n\nlet runOnce = once(myContext, function() {\n  // will not be executed\n});\n\ncancel(runOnce);\n\nlet throttle = throttle(myContext, function() {\n  // will not be executed\n}, 1, false);\n\ncancel(throttle);\n\nlet debounce = debounce(myContext, function() {\n  // will not be executed\n}, 1);\n\ncancel(debounce);\n\nlet debounceImmediate = debounce(myContext, function() {\n  // will be executed since we passed in true (immediate)\n}, 100, true);\n\n// the 100ms delay until this method can be called again will be canceled\ncancel(debounceImmediate);\n```",
       "itemtype": "method",
       "name": "cancel",
@@ -17676,8 +17927,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 618,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 778,
       "description": "Delay calling the target method until the debounce period has elapsed\nwith no additional debounce calls. If `debounce` is called again before\nthe specified time has elapsed, the timer is reset and the entire period\nmust pass again before the target method is called.\n\nThis method should be used when an event may be called multiple times\nbut the action should only be called once when the event is done firing.\nA common example is for scroll events where you only want updates to\nhappen once scrolling has ceased.\n\n```javascript\nimport { debounce } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'debounce' };\n\ndebounce(myContext, whoRan, 150);\n\n// less than 150ms passes\ndebounce(myContext, whoRan, 150);\n\n// 150ms passes\n// whoRan is invoked with context myContext\n// console logs 'debounce ran.' one time.\n```\n\nImmediate allows you to run the function immediately, but debounce\nother calls for this function until the wait time has elapsed. If\n`debounce` is called again before the specified time has elapsed,\nthe timer is reset and the entire period must pass again before\nthe method can be called again.\n\n```javascript\nimport { debounce } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'debounce' };\n\ndebounce(myContext, whoRan, 150, true);\n\n// console logs 'debounce ran.' one time immediately.\n// 100ms passes\ndebounce(myContext, whoRan, 150, true);\n\n// 150ms passes and nothing else is logged to the console and\n// the debouncee is no longer being watched\ndebounce(myContext, whoRan, 150, true);\n\n// console logs 'debounce ran.' one time immediately.\n// 150ms passes and nothing else is logged to the console and\n// the debouncee is no longer being watched\n```",
       "itemtype": "method",
       "name": "debounce",
@@ -17721,8 +17972,8 @@
       "module": "@ember/runloop"
     },
     {
-      "file": "packages/@ember/runloop/index.js",
-      "line": 696,
+      "file": "packages/@ember/runloop/index.ts",
+      "line": 875,
       "description": "Ensure that the target method is never called more frequently than\nthe specified spacing period. The target method is called immediately.\n\n```javascript\nimport { throttle } from '@ember/runloop';\n\nfunction whoRan() {\n  console.log(this.name + ' ran.');\n}\n\nlet myContext = { name: 'throttle' };\n\nthrottle(myContext, whoRan, 150);\n// whoRan is invoked with context myContext\n// console logs 'throttle ran.'\n\n// 50ms passes\nthrottle(myContext, whoRan, 150);\n\n// 50ms passes\nthrottle(myContext, whoRan, 150);\n\n// 150ms passes\nthrottle(myContext, whoRan, 150);\n// whoRan is invoked with context myContext\n// console logs 'throttle ran.'\n```",
       "itemtype": "method",
       "name": "throttle",
@@ -18495,11 +18746,11 @@
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:103"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:127"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:109"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:133"
     },
     {
       "message": "replacing incorrect tag: function with method",
@@ -18523,7 +18774,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:450"
+      "line": " packages/@ember/-internals/container/lib/registry.ts:448"
     },
     {
       "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.",
@@ -18587,11 +18838,11 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:104"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:107"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:112"
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:115"
     },
     {
       "message": "Missing item type\nThe template-compiler does not support strict mode at this time.\nprecompile from ember-template-compiler returns a string and\nnot a template-factory, so it doesn't help with strict-mode testing.\n\nWe also can't import from `@ember/template-compiler` because it\ndoesn't exist to this kind of test, otherwise we'd be able to use\nprecompileTemplate, which would be perfect :D\n\nCopied(ish) from https://github.com/NullVoxPopuli/ember-repl/blob/main/addon/hbs.ts#L51",
@@ -18847,15 +19098,15 @@
     },
     {
       "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:1633"
     },
     {
       "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:1654"
     },
     {
       "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:1676"
     },
     {
       "message": "Missing item type",
@@ -18871,19 +19122,19 @@
     },
     {
       "message": "Missing item type\nSubscribes a function to a named event and then cancels the subscription\nafter the first time the event is triggered. It is good to use ``one`` when\nyou only care about the first time an event has taken place.",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:16"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:23"
     },
     {
       "message": "Missing item type\nTriggers a named event for the object. Any additional arguments\nwill be passed as parameters to the functions that are subscribed to the\nevent.",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:27"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:34"
     },
     {
       "message": "Missing item type\nCancels subscription for given name, target, and method.",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:33"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:40"
     },
     {
       "message": "Missing item type\nChecks to see if object has any subscriptions for named event.",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:42"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/evented.d.ts:49"
     },
     {
       "message": "Missing item type\nThis mixin provides properties and property observing functionality, core features of the Ember object model.",
@@ -18943,75 +19194,107 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:21"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:14"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:17"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:22"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:27"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:24"
     },
     {
       "message": "Missing item type",
       "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:30"
     },
     {
-      "message": "Missing item type\nCoreObject constructor takes owner.",
+      "message": "Missing item type",
       "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:33"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:38"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:36"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:44"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:50"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:53"
+    },
+    {
+      "message": "Missing item type\nCoreObject constructor takes owner.",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:56"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:61"
     },
     {
       "message": "Missing item type\nAn overridable method called when objects are instantiated. By default,\ndoes nothing unless it is overridden during class definition.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:41"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:64"
     },
     {
       "message": "Missing item type\nDefines the properties that will be concatenated from the superclass (instead of overridden).",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:47"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:70"
     },
     {
       "message": "Missing item type\nDestroyed object property flag. If this property is true the observers and bindings were\nalready removed by the effect of calling the destroy() method.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:53"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:76"
     },
     {
       "message": "Missing item type\nDestruction scheduled flag. The destroy() method has been called. The object stays intact\nuntil the end of the run loop at which point the isDestroyed flag is set.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:59"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:82"
     },
     {
       "message": "Missing item type\nDestroys an object by setting the `isDestroyed` flag and removing its\nmetadata, which effectively destroys observers and bindings.\nIf you try to set a property on a destroyed object, an exception will be\nraised.\nNote that destruction is scheduled for the end of the run loop and does not\nhappen immediately.  It will set an isDestroying flag immediately.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:66"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:90"
     },
     {
       "message": "Missing item type\nOverride to implement teardown.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:77"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:101"
     },
     {
       "message": "Missing item type\nReturns a string representation which attempts to provide more information than Javascript's toString\ntypically does, in a generic way for all Ember objects (e.g., \"<App.Person:ember1024>\").",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:82"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:106"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:94"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:118"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:100"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:124"
     },
     {
       "message": "Missing item type\nIterate over each computed property for the class, passing its name and any\nassociated metadata (see metaForProperty) to the callback.",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:103"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:127"
     },
     {
       "message": "Missing item type\nReturns the original hash that was passed to meta().",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:109"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:133"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:116"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:140"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:119"
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:143"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/system/core_object.d.ts:146"
     },
     {
       "message": "Missing item type",
@@ -19029,6 +19312,14 @@
       "message": "Missing item type\nStrongly hint runtimes to intern the provided string.\n\nWhen do I need to use this function?\n\nFor the most part, never. Pre-mature optimization is bad, and often the\nruntime does exactly what you need it to, and more often the trade-off isn't\nworth it.\n\nWhy?\n\nRuntimes store strings in at least 2 different representations:\nRopes and Symbols (interned strings). The Rope provides a memory efficient\ndata-structure for strings created from concatenation or some other string\nmanipulation like splitting.\n\nUnfortunately checking equality of different ropes can be quite costly as\nruntimes must resort to clever string comparison algorithms. These\nalgorithms typically cost in proportion to the length of the string.\nLuckily, this is where the Symbols (interned strings) shine. As Symbols are\nunique by their string content, equality checks can be done by pointer\ncomparison.\n\nHow do I know if my string is a rope or symbol?\n\nTypically (warning general sweeping statement, but truthy in runtimes at\npresent) static strings created as part of the JS source are interned.\nStrings often used for comparisons can be interned at runtime if some\ncriteria are met.  One of these criteria can be the size of the entire rope.\nFor example, in chrome 38 a rope longer then 12 characters will not\nintern, nor will segments of that rope.\n\nSome numbers: http://jsperf.com/eval-vs-keys/8\n\nKnown Trick™",
       "line": " packages/@ember/-internals/utils/lib/intern.ts:1"
     },
+    {
+      "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"
+    },
     {
       "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"