ember-source 7.4.0-alpha.1 → 7.4.0-beta.1

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": "7.4.0-alpha.1"
+    "version": "7.4.0-beta.1"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -742,6 +742,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@ember/-internals/utils/lib/internal-mixin-create.ts": {
+      "name": "packages/@ember/-internals/utils/lib/internal-mixin-create.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@ember/-internals/utils/lib/invoke.ts": {
       "name": "packages/@ember/-internals/utils/lib/invoke.ts",
       "modules": {},
@@ -1646,22 +1653,22 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/component/dist/-private/component.d.ts": {
-      "name": "packages/@glimmer/component/dist/-private/component.d.ts",
+    "packages/@glimmer/component/dist/component/src/-private/component.d.ts": {
+      "name": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "modules": {},
       "classes": {},
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/component/dist/-private/ember-component-manager.d.ts": {
-      "name": "packages/@glimmer/component/dist/-private/ember-component-manager.d.ts",
+    "packages/@glimmer/component/dist/component/src/-private/ember-component-manager.d.ts": {
+      "name": "packages/@glimmer/component/dist/component/src/-private/ember-component-manager.d.ts",
       "modules": {},
       "classes": {},
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/component/dist/index.d.ts": {
-      "name": "packages/@glimmer/component/dist/index.d.ts",
+    "packages/@glimmer/component/dist/component/src/index.d.ts": {
+      "name": "packages/@glimmer/component/dist/component/src/index.d.ts",
       "modules": {
         "@glimmer/component": 1
       },
@@ -1669,8 +1676,15 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/component/dist/index.js": {
-      "name": "packages/@glimmer/component/dist/index.js",
+    "packages/@glimmer/component/dist/dev/index.js": {
+      "name": "packages/@glimmer/component/dist/dev/index.js",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
+    "packages/@glimmer/component/dist/prod/index.js": {
+      "name": "packages/@glimmer/component/dist/prod/index.js",
       "modules": {},
       "classes": {},
       "fors": {},
@@ -1774,6 +1788,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/destroyable/index.ts": {
+      "name": "packages/@glimmer/destroyable/index.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/global-context/index.ts": {
       "name": "packages/@glimmer/global-context/index.ts",
       "modules": {},
@@ -2307,6 +2328,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/util/lib/destroyable-key.ts": {
+      "name": "packages/@glimmer/util/lib/destroyable-key.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/util/lib/intern.ts": {
       "name": "packages/@glimmer/util/lib/intern.ts",
       "modules": {},
@@ -2749,7 +2777,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/array/index.ts",
-      "line": 1414
+      "line": 1415
     },
     "@ember/array/proxy": {
       "name": "@ember/array/proxy",
@@ -2762,7 +2790,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/array/proxy.ts",
-      "line": 57
+      "line": 58
     },
     "@ember/canary-features": {
       "name": "@ember/canary-features",
@@ -2816,7 +2844,7 @@
       },
       "tag": "module",
       "file": "packages/@ember/controller/index.ts",
-      "line": 311
+      "line": 312
     },
     "@ember/debug": {
       "name": "@ember/debug",
@@ -2909,7 +2937,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/enumerable/index.ts",
-      "line": 8,
+      "line": 9,
       "access": "private",
       "tagname": ""
     },
@@ -2944,7 +2972,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/core.ts",
-      "line": 171
+      "line": 172
     },
     "@ember/object/evented": {
       "name": "@ember/object/evented",
@@ -2957,7 +2985,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/evented.ts",
-      "line": 15
+      "line": 17
     },
     "@ember/object/mixin": {
       "name": "@ember/object/mixin",
@@ -2973,7 +3001,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/mixin.ts",
-      "line": 454
+      "line": 456
     },
     "@ember/object/observable": {
       "name": "@ember/object/observable",
@@ -2986,7 +3014,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/observable.ts",
-      "line": 25
+      "line": 26
     },
     "@ember/object/promise-proxy-mixin": {
       "name": "@ember/object/promise-proxy-mixin",
@@ -2999,7 +3027,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 48
+      "line": 50
     },
     "@ember/object/proxy": {
       "name": "@ember/object/proxy",
@@ -3012,7 +3040,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/object/proxy.ts",
-      "line": 8
+      "line": 9
     },
     "@ember/reactive/collections": {
       "name": "@ember/reactive/collections",
@@ -3129,7 +3157,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/route.ts",
-      "line": 74
+      "line": 83
     },
     "@ember/routing/router-service": {
       "name": "@ember/routing/router-service",
@@ -3142,7 +3170,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 28
+      "line": 35
     },
     "@ember/routing/router": {
       "name": "@ember/routing/router",
@@ -3155,7 +3183,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/routing/router.ts",
-      "line": 136
+      "line": 145
     },
     "@ember/routing/transition": {
       "name": "@ember/routing/transition",
@@ -3212,7 +3240,7 @@
       "fors": {},
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@glimmer/component/dist/index.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/index.d.ts",
       "line": 3,
       "description": "A component is a reusable UI element that consists of a 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.\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/emberjs/ember.js/tree/main/packages/%40glimmer/component).\n\nNote: Prior to Ember 6.8, by default, components were authored in paired `.hbs` and `.js`\nfiles. This is still supported, but the default authoring format is now `.gjs` or \"template tag\".\nTo read more about how components were previously authored, see the\n[6.7 version of this API documentation](https://api.emberjs.com/ember/6.7/modules/@glimmer%2Fcomponent).\n  \n## Defining a Template-only Component\n\nThe simplest way to create a component is to create a `gjs` file in\n`app/components` with a `<template>` tag wrapper:\n\n```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  <h1>{{@person.name}}</h1>\n  <img src={{@person.avatar}}>\n  <p class='signature'>{{@person.signature}}</p>\n</template>\n```\n\nYou will be able to use `<PersonProfile />` to invoke this component elsewhere\nin your application:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport PersonProfile from '../components/person-profile';\n  \n<template>\n  <PersonProfile @person={{@model.currentUser}} />\n</template>\n```\n\nNote that component names are capitalized here in order to distinguish them\nfrom regular HTML elements.\n\nEmber 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\nIn Ember templates, “invokables” are things you can invoke in a template. These include components,\nhelpers, and modifiers. In the template tag format, these invokables need to be imported before\nthey can be used. This makes it easier to understand where values come from and what they do, as\nwell as unlocks build optimizations.\n\nWhen making use of the `PersonProfile` component as defined before in a different component file,\nit first needs to be imported. This is done using the import statement, just like you would import\nany other JavaScript module -- from your local project or from an external package.\n\nSince they are imported, Components can be placed anywhere in your project on the filesystem, but\nthey are conventionally placed within `app/components` for reusable components and within\n`app/templates` for Route components.\n  \nRoute components must be named after the route they are associated with -- and placed in the\n`app/templates` directory. For example, a `Person` route would have a corresponding `Person`\ncomponent defined in `app/templates/person.gjs`. This component would then be rendered whenever\nthe user visits the `/person` route. For more information, see the\n[Routing](https://guides.emberjs.com/release/routing/) section of the guides.\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  <h1>{{@person.name}}</h1>\n  {{yield}}\n</template>\n```\n\nWe could then invoke it like this:\n\n```gjs\nimport PersonProfile from '../components/person-profile';\n  \n<template>\n  <PersonProfile @person={{@model.currentUser}}>\n    <p>Admin mode</p>\n  </PersonProfile>\n</template>\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  <h1>{{@person.name}}</h1>\n  {{yield @person.signature}}\n</template>\n```\n\nWe can then use this value in the block like so:\n\n```gjs\nimport PersonProfile from '../components/person-profile';\n  \n<template>\n  <PersonProfile @person={{@model.currentUser}} as |signature|>\n    {{signature}}\n  </PersonProfile>\n</template>\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  <h1>{{yield to=\"title\"}}</h1>\n  {{yield}}\n</template>\n```\n\nThis component could then be invoked like so:\n\n```gjs\nimport PersonProfile from '../components/person-profile';\n\n<template>\n  <PersonProfile @person={{@model.currentUser}}>\n    <:title>{{@model.currentUser.name}}</:title>\n    <:default>{{@model.currentUser.signature}}</:default>\n  </PersonProfile>\n</template>\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  <h1>{{yield @person.name to=\"title\"}}</h1>\n  {{yield @person.signature}}\n</template>\n```\n\nThese parameters can then be used like so:\n\n```gjs\nimport PersonProfile from '../components/person-profile';\n\n<template>\n  <PersonProfile @person={{@model.currentUser}}>\n    <:title as |name|>{{name}}</:title>\n    <:default as |signature|>{{signature}}</:default>\n  </PersonProfile>\n</template>\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\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</template>\n```\n\nWith this template, we can then optionally pass in one block, both blocks, or\nnone at all:\n\n```gjs\nimport PersonProfile from '../components/person-profile';\n\n<template>\n  {{! passing both blocks }}\n  <PersonProfile @person={{@model.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={{@model.currentUser}}>\n    <:title as |name|>{{name}}</:title>\n  </PersonProfile>\n\n  {{! passing just the default block }}\n  <PersonProfile @person={{@model.currentUser}} as |signature|>\n    {{signature}}\n  </PersonProfile>\n\n  {{! not passing any blocks }}\n  <PersonProfile @person={{@model.currentUser}}/>\n</template>\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```gjs {data-filename=\"app/components/person-profile.gjs\"}\n<template>\n  {{#if (has-block-params)}}\n    {{yield @person.signature}}\n  {{else}}\n    {{yield}}\n  {{/if}}\n</template>\n```\n\n## Customizing Components With JavaScript\n\nTo add JavaScript to a component, add a class extending from `@glimmer/component` to the `gjs`\nfile, wrapping your `<template>` tag.\nFor example, to add JavaScript to the `PersonProfile` component which we defined above:\n\n```gjs {data-filename=\"app/components/person-profile.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class PersonProfile 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  <template>\n    <h1>{{this.displayName}}</h1>\n    {{yield}}\n  </template>\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}}`. In the example above, we access the\n`displayName` property of our `PersonProfile` component instance in the\ntemplate.\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```gjs\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```gjs\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  \nYou may prefer the [@ember/destroyable](/ember/release/modules//@ember%2Fdestroyable) APIs for\nthis purpose.\n\n```gjs\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();\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```gjs\n<template>\n  <SomeComponent @fadeIn={{true}} />\n</template>\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 to update as any other tracked property:\n\n```gjs\nimport Component from '@glimmer/component';\nimport { computed } from '@ember/object';\n\nexport default class SomeComponent extends Component {\n  get standardGetter() {\n    // updates whenever args.anotherValue updates\n    return this.args.anotherValue;\n  }\n}\n```\n  \nA components arguments are accessible in the template using the `@` prefix - for example,\n`this.args.fadeIn` from the example above can be accessed in the template as `@fadeIn`.\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",
@@ -3385,7 +3413,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/utils/curly-component-state-bucket.ts",
-      "line": 23,
+      "line": 24,
       "description": "Represents the internal state of the component.",
       "access": "private",
       "tagname": ""
@@ -3519,7 +3547,7 @@
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/index.ts",
       "line": 104,
-      "description": "## Looking for template keywords and helpers? \n   \n See [@ember/helper](../modules/@ember%2Fhelper).",
+      "description": "## Looking for template keywords and helpers? \n   \n See [@ember/helper](../../modules/@ember%2Fhelper).",
       "access": "public",
       "tagname": ""
     },
@@ -3902,7 +3930,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 63,
+      "line": 64,
       "description": "`ProxyMixin` forwards all properties not defined by the proxy itself\nto a proxied `content` object.  See ObjectProxy for more details.",
       "access": "private",
       "tagname": ""
@@ -3921,7 +3949,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/action_handler.ts",
-      "line": 10,
+      "line": 11,
       "description": "`ActionHandler` is available on some familiar classes including\n`Route`, `Component`, and `Controller`.\n(Internally the mixin is used by `CoreView`, `ControllerMixin`,\nand `Route` and available to the above classes through\ninheritance.)",
       "access": "private",
       "tagname": ""
@@ -3937,7 +3965,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/comparable.ts",
-      "line": 8,
+      "line": 9,
       "description": "Implements some standard methods for comparing objects. Add this mixin to\nany class you create that can compare its instances.\n\nYou should implement the `compare()` method.",
       "since": "Ember 0.9",
       "access": "private",
@@ -3956,7 +3984,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 12,
+      "line": 13,
       "description": "ContainerProxyMixin is used to provide public access to specific\ncontainer functionality.",
       "extends": "ContainerProxy",
       "access": "private",
@@ -3976,7 +4004,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts",
-      "line": 12,
+      "line": 13,
       "description": "RegistryProxyMixin is used to provide public access to specific\nregistry functionality.",
       "extends": "RegistryProxy",
       "access": "private",
@@ -3995,7 +4023,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts",
-      "line": 13,
+      "line": 14,
       "description": "`TargetActionSupport` is a mixin that can be included in a class\nto add a `triggerAction` method with semantics similar to the\n`{{action}}` helper. In normal Ember usage, the `{{action}}` helper is\nusually the best choice. This mixin is most often useful when you are\ndoing more complex event handling in Components.",
       "extends": "Mixin",
       "access": "private",
@@ -4041,7 +4069,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/views/lib/mixins/action_support.ts",
-      "line": 10,
+      "line": 11,
       "access": "private",
       "tagname": ""
     },
@@ -4073,7 +4101,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 9,
+      "line": 17,
       "description": "`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,
@@ -4176,7 +4204,7 @@
       "module": "@ember/array",
       "namespace": "",
       "file": "packages/@ember/array/index.ts",
-      "line": 156,
+      "line": 157,
       "description": "This mixin implements Observer-friendly Array-like behavior. It is not a\nconcrete implementation, but it can be used up by other classes that want\nto appear like arrays.\n\nFor example, ArrayProxy is a concrete class that can be instantiated to\nimplement array-like behavior. This class uses the Array Mixin by way of\nthe MutableArray mixin, which allows observable changes to be made to the\nunderlying array.\n\nThis mixin defines methods specifically for collections that provide\nindex-ordered access to their contents. When you are designing code that\nneeds to accept any kind of Array-like object, you should use these methods\ninstead of Array primitives because these will properly notify observers of\nchanges to the array.\n\nAlthough these methods are efficient, they do add a layer of indirection to\nyour application so it is a good idea to use them only when you need the\nflexibility of using both true JavaScript arrays and \"virtual\" arrays such\nas controllers and collections.\n\nYou can use the methods defined in this module to access and modify array\ncontents in an observable-friendly way. You can also be notified whenever\nthe membership of an array changes by using `.observes('myArray.[]')`.\n\nTo support `EmberArray` in your own class, you must override two\nprimitives to use it: `length()` and `objectAt()`.",
       "uses": [
         "Enumerable"
@@ -4199,7 +4227,7 @@
       "module": "@ember/array",
       "namespace": "",
       "file": "packages/@ember/array/index.ts",
-      "line": 1414,
+      "line": 1415,
       "description": "This mixin defines the API for modifying array-like objects. These methods\ncan be applied only to a collection that keeps its items in an ordered set.\nIt builds upon the Array mixin and adds methods to modify the array.\nOne concrete implementations of this class include ArrayProxy.\n\nIt is important to use the methods in this class to modify arrays so that\nchanges are observable. This allows the binding system in Ember to function\ncorrectly.\n\n\nNote that an Array can change even if it does not implement this mixin.\nFor example, one might implement a SparseArray that cannot be directly\nmodified, but if its underlying enumerable changes, it will change also.",
       "uses": [
         "EmberArray",
@@ -4219,7 +4247,7 @@
       "module": "ember",
       "namespace": "",
       "file": "packages/@ember/array/index.ts",
-      "line": 2015,
+      "line": 2016,
       "description": "The NativeArray mixin contains the properties needed to make the native\nArray support MutableArray and all of its dependent APIs.",
       "uses": [
         "MutableArray",
@@ -4239,14 +4267,16 @@
       "module": "@ember/array/proxy",
       "namespace": "",
       "file": "packages/@ember/array/proxy.ts",
-      "line": 57,
+      "line": 58,
       "description": "An ArrayProxy wraps any other object that implements `Array` and/or\n`MutableArray,` forwarding all requests. This makes it very useful for\na number of binding use cases or other cases where being able to swap\nout the underlying array is useful.\n\nA simple example of usage:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nlet pets = ['dog', 'cat', 'fish'];\nlet ap = ArrayProxy.create({ content: A(pets) });\n\nap.get('firstObject');                        // 'dog'\nap.set('content', ['amoeba', 'paramecium']);\nap.get('firstObject');                        // 'amoeba'\n```\n\nThis class can also be useful as a layer to transform the contents of\nan array, as they are accessed. This can be done by overriding\n`objectAtContent`:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nlet pets = ['dog', 'cat', 'fish'];\nlet ap = ArrayProxy.create({\n    content: A(pets),\n    objectAtContent: function(idx) {\n        return this.get('content').objectAt(idx).toUpperCase();\n    }\n});\n\nap.get('firstObject'); // . 'DOG'\n```\n\nWhen overriding this class, it is important to place the call to\n`_super` *after* setting `content` so the internal observers have\na chance to fire properly:\n\n```javascript\nimport { A } from '@ember/array';\nimport ArrayProxy from '@ember/array/proxy';\n\nexport default ArrayProxy.extend({\n  init() {\n    this.set('content', A(['dog', 'cat', 'fish']));\n    this._super(...arguments);\n  }\n});\n```",
       "extends": "EmberObject",
       "uses": [
         "MutableArray"
       ],
       "access": "public",
-      "tagname": ""
+      "tagname": "",
+      "deprecated": true,
+      "deprecationMessage": "Use a tracked array or a native `Proxy` instead."
     },
     "FEATURES": {
       "name": "FEATURES",
@@ -4290,7 +4320,7 @@
       "module": "@ember/controller",
       "namespace": "Ember",
       "file": "packages/@ember/controller/index.ts",
-      "line": 27,
+      "line": 28,
       "uses": [
         "Ember.ActionHandler"
       ],
@@ -4308,7 +4338,7 @@
       "module": "@ember/controller",
       "namespace": "Ember",
       "file": "packages/@ember/controller/index.ts",
-      "line": 311,
+      "line": 312,
       "extends": "EmberObject",
       "uses": [
         "Ember.ControllerMixin"
@@ -4439,7 +4469,7 @@
       "module": "@ember/enumerable",
       "namespace": "",
       "file": "packages/@ember/enumerable/index.ts",
-      "line": 8,
+      "line": 9,
       "description": "The methods in this mixin have been moved to [MutableArray](/ember/release/classes/MutableArray). This mixin has\nbeen intentionally preserved to avoid breaking Enumerable.detect checks\nuntil the community migrates away from them.",
       "access": "private",
       "tagname": ""
@@ -4455,7 +4485,7 @@
       "module": "ember",
       "namespace": "Ember",
       "file": "packages/@ember/enumerable/mutable.ts",
-      "line": 8,
+      "line": 9,
       "description": "The methods in this mixin have been moved to MutableArray. This mixin has\nbeen intentionally preserved to avoid breaking MutableEnumerable.detect\nchecks until the community migrates away from them.",
       "uses": [
         "Enumerable"
@@ -4535,7 +4565,7 @@
       "module": "@ember/object/core",
       "namespace": "",
       "file": "packages/@ember/object/core.ts",
-      "line": 171,
+      "line": 172,
       "description": "`CoreObject` is the base class for all Ember constructs. It establishes a\nclass system based on Ember's Mixin system, and provides the basis for the\nEmber Object Model. `CoreObject` should generally not be used directly,\ninstead you should use `EmberObject`.\n\n## Usage\n\nYou can define a class by extending from `CoreObject` using the `extend`\nmethod:\n\n```js\nconst Person = CoreObject.extend({\n  name: 'Tomster',\n});\n```\n\nFor detailed usage, see the [Object Model](https://guides.emberjs.com/release/object-model/)\nsection of the guides.\n\n## Usage with Native Classes\n\nNative JavaScript `class` syntax can be used to extend from any `CoreObject`\nbased class:\n\n```js\nclass Person extends CoreObject {\n  init() {\n    super.init(...arguments);\n    this.name = 'Tomster';\n  }\n}\n```\n\nSome notes about `class` usage:\n\n* `new` syntax is not currently supported with classes that extend from\n  `EmberObject` or `CoreObject`. You must continue to use the `create` method\n  when making new instances of classes, even if they are defined using native\n  class syntax. If you want to use `new` syntax, consider creating classes\n  which do _not_ extend from `EmberObject` or `CoreObject`. Ember features,\n  such as computed properties and decorators, will still work with base-less\n  classes.\n* Instead of using `this._super()`, you must use standard `super` syntax in\n  native classes. See the [MDN docs on classes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Super_class_calls_with_super)\n  for more details.\n* Native classes support using [constructors](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Constructor)\n  to set up newly-created instances. Ember uses these to, among other things,\n  support features that need to retrieve other entities by name, like Service\n  injection and `getOwner`. To ensure your custom instance setup logic takes\n  place after this important work is done, avoid using the `constructor` in\n  favor of `init`.\n* Properties passed to `create` will be available on the instance by the time\n  `init` runs, so any code that requires these values should work at that\n  time.\n* Using native classes, and switching back to the old Ember Object model is\n  fully supported.",
       "access": "public",
       "tagname": ""
@@ -4555,10 +4585,12 @@
       "module": "@ember/object/evented",
       "namespace": "",
       "file": "packages/@ember/object/evented.ts",
-      "line": 15,
+      "line": 17,
       "description": "This mixin allows for Ember objects to subscribe to and emit events.\n\n```app/utils/person.js\nimport EmberObject from '@ember/object';\nimport Evented from '@ember/object/evented';\n\nexport default class Person extends EmberObject.extend(Evented) {\n  greet() {\n    // ...\n    this.trigger('greet');\n  }\n}\n```\n\n```javascript\nvar person = Person.create();\n\nperson.on('greet', function() {\n  console.log('Our person has greeted');\n});\n\nperson.greet();\n\n// outputs: 'Our person has greeted'\n```\n\nYou can also chain multiple event subscriptions:\n\n```javascript\nperson.on('greet', function() {\n  console.log('Our person has greeted');\n}).one('greet', function() {\n  console.log('Offer one-time special');\n}).off('event', this, forgetThis);\n```",
       "access": "public",
-      "tagname": ""
+      "tagname": "",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead."
     },
     "EmberObject": {
       "name": "EmberObject",
@@ -4591,7 +4623,7 @@
       "module": "@ember/object/mixin",
       "namespace": "",
       "file": "packages/@ember/object/mixin.ts",
-      "line": 454,
+      "line": 456,
       "description": "The `Mixin` class allows you to create mixins, whose properties can be\nadded to other classes. For instance,\n\n```javascript\nimport Mixin from '@ember/object/mixin';\n\nconst EditableMixin = Mixin.create({\n  edit() {\n    console.log('starting to edit');\n    this.set('isEditing', true);\n  },\n  isEditing: false\n});\n```\n\n```javascript\nimport EmberObject from '@ember/object';\nimport EditableMixin from '../mixins/editable';\n\n// Mix mixins into classes by passing them as the first arguments to\n// `.extend.`\nclass Comment extends EmberObject.extend(EditableMixin) {\n  post = null\n}\n\nlet comment = Comment.create({\n  post: somePost\n});\n\ncomment.edit(); // outputs 'starting to edit'\n```\n\nNote that Mixins are created with `Mixin.create`, not\n`Mixin.extend`.\n\nNote that mixins extend a constructor's prototype so arrays and object literals\ndefined as properties will be shared amongst objects that implement the mixin.\nIf you want to define a property in a mixin that is not shared, you can define\nit either as a computed property or have it be created on initialization of the object.\n\n```javascript\n// filters array will be shared amongst any object implementing mixin\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\n\nconst FilterableMixin = Mixin.create({\n  filters: A()\n});\n```\n\n```javascript\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\nimport { computed } from '@ember/object';\n\n// filters will be a separate array for every object implementing the mixin\nconst FilterableMixin = Mixin.create({\n  filters: computed(function() {\n    return A();\n  })\n});\n```\n\n```javascript\nimport Mixin from '@ember/object/mixin';\nimport { A } from '@ember/array';\n\n// filters will be created as a separate array during the object's initialization\nconst Filterable = Mixin.create({\n  filters: null,\n\n  init() {\n    this._super(...arguments);\n    this.set(\"filters\", A());\n  }\n});\n```",
       "access": "public",
       "tagname": ""
@@ -4621,7 +4653,7 @@
       "module": "@ember/object/observable",
       "namespace": "",
       "file": "packages/@ember/object/observable.ts",
-      "line": 25,
+      "line": 26,
       "description": "## Overview\n\nThis mixin provides properties and property observing functionality, core\nfeatures of the Ember object model.\n\nProperties and observers allow one object to observe changes to a\nproperty on another object. This is one of the fundamental ways that\nmodels, controllers and views communicate with each other in an Ember\napplication.\n\nAny object that has this mixin applied can be used in observer\noperations. That includes `EmberObject` and most objects you will\ninteract with as you write your Ember application.\n\nNote that you will not generally apply this mixin to classes yourself,\nbut you will use the features provided by this module frequently, so it\nis important to understand how to use it.\n\n## Using `get()` and `set()`\n\nBecause of Ember's support for bindings and observers, you will always\naccess properties using the get method, and set properties using the\nset method. This allows the observing objects to be notified and\ncomputed properties to be handled properly.\n\nMore documentation about `get` and `set` are below.\n\n## Observing Property Changes\n\nYou typically observe property changes simply by using the `observer`\nfunction in classes that you write.\n\nFor example:\n\n```javascript\nimport { observer } from '@ember/object';\nimport EmberObject from '@ember/object';\n\nEmberObject.extend({\n  valueObserver: observer('value', function(sender, key, value, rev) {\n    // Executes whenever the \"value\" property changes\n    // See the addObserver method for more information about the callback arguments\n  })\n});\n```\n\nAlthough this is the most common way to add an observer, this capability\nis actually built into the `EmberObject` class on top of two methods\ndefined in this mixin: `addObserver` and `removeObserver`. You can use\nthese two methods to add and remove observers yourself if you need to\ndo so at runtime.\n\nTo add an observer for a property, call:\n\n```javascript\nobject.addObserver('propertyKey', targetObject, targetAction)\n```\n\nThis will call the `targetAction` method on the `targetObject` whenever\nthe value of the `propertyKey` changes.\n\nNote that if `propertyKey` is a computed property, the observer will be\ncalled when any of the property dependencies are changed, even if the\nresulting value of the computed property is unchanged. This is necessary\nbecause computed properties are not computed until `get` is called.",
       "access": "public",
       "tagname": ""
@@ -4637,10 +4669,12 @@
       "module": "@ember/object/promise-proxy-mixin",
       "namespace": "",
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 48,
+      "line": 50,
       "description": "A low level mixin making ObjectProxy promise-aware.\n\n```javascript\nimport { resolve } from 'rsvp';\nimport $ from 'jquery';\nimport ObjectProxy from '@ember/object/proxy';\nimport PromiseProxyMixin from '@ember/object/promise-proxy-mixin';\n\nlet ObjectPromiseProxy = ObjectProxy.extend(PromiseProxyMixin);\n\nlet proxy = ObjectPromiseProxy.create({\n  promise: resolve($.getJSON('/some/remote/data.json'))\n});\n\nproxy.then(function(json){\n   // the json\n}, function(reason) {\n   // the reason why you have no json\n});\n```\n\nthe proxy has bindable attributes which\ntrack the promises life cycle\n\n```javascript\nproxy.get('isPending')   //=> true\nproxy.get('isSettled')  //=> false\nproxy.get('isRejected')  //=> false\nproxy.get('isFulfilled') //=> false\n```\n\nWhen the $.getJSON completes, and the promise is fulfilled\nwith json, the life cycle attributes will update accordingly.\nNote that $.getJSON doesn't return an ECMA specified promise,\nit is useful to wrap this with an `RSVP.resolve` so that it behaves\nas a spec compliant promise.\n\n```javascript\nproxy.get('isPending')   //=> false\nproxy.get('isSettled')   //=> true\nproxy.get('isRejected')  //=> false\nproxy.get('isFulfilled') //=> true\n```\n\nAs the proxy is an ObjectProxy, and the json now its content,\nall the json properties will be available directly from the proxy.\n\n```javascript\n// Assuming the following json:\n{\n  firstName: 'Stefan',\n  lastName: 'Penner'\n}\n\n// both properties will accessible on the proxy\nproxy.get('firstName') //=> 'Stefan'\nproxy.get('lastName')  //=> 'Penner'\n```",
       "access": "public",
-      "tagname": ""
+      "tagname": "",
+      "deprecated": true,
+      "deprecationMessage": "Use native `async`/`await` and promises directly instead."
     },
     "ObjectProxy": {
       "name": "ObjectProxy",
@@ -4653,14 +4687,16 @@
       "module": "@ember/object/proxy",
       "namespace": "",
       "file": "packages/@ember/object/proxy.ts",
-      "line": 8,
+      "line": 9,
       "description": "`ObjectProxy` forwards all properties not defined by the proxy itself\nto a proxied `content` object.\n\n```javascript\nimport EmberObject from '@ember/object';\nimport ObjectProxy from '@ember/object/proxy';\n\nlet exampleObject = EmberObject.create({\n  name: 'Foo'\n});\n\nlet exampleProxy = ObjectProxy.create({\n  content: exampleObject\n});\n\n// Access and change existing properties\nexampleProxy.get('name');          // 'Foo'\nexampleProxy.set('name', 'Bar');\nexampleObject.get('name');         // 'Bar'\n\n// Create new 'description' property on `exampleObject`\nexampleProxy.set('description', 'Foo is a whizboo baz');\nexampleObject.get('description');  // 'Foo is a whizboo baz'\n```\n\nWhile `content` is unset, setting a property to be delegated will throw an\nError.\n\n```javascript\nimport ObjectProxy from '@ember/object/proxy';\n\nlet exampleProxy = ObjectProxy.create({\n  content: null,\n  flag: null\n});\nexampleProxy.set('flag', true);\nexampleProxy.get('flag');         // true\nexampleProxy.get('foo');          // undefined\nexampleProxy.set('foo', 'data');  // throws Error\n```\n\nDelegated properties can be bound to and will change when content is updated.\n\nComputed properties on the proxy itself can depend on delegated properties.\n\n```javascript\nimport { computed } from '@ember/object';\nimport ObjectProxy from '@ember/object/proxy';\n\nclass ProxyWithComputedProperty extends ObjectProxy {\n  @computed('firstName', 'lastName')\n  get fullName() {\n    var firstName = this.get('firstName'),\n        lastName = this.get('lastName');\n    if (firstName && lastName) {\n      return firstName + ' ' + lastName;\n    }\n    return firstName || lastName;\n  }\n}\n\nlet exampleProxy = ProxyWithComputedProperty.create();\n\nexampleProxy.get('fullName');  // undefined\nexampleProxy.set('content', {\n  firstName: 'Tom', lastName: 'Dale'\n}); // triggers property change for fullName on proxy\n\nexampleProxy.get('fullName');  // 'Tom Dale'\n```",
       "extends": "EmberObject",
       "uses": [
         "Ember.ProxyMixin"
       ],
       "access": "public",
-      "tagname": ""
+      "tagname": "",
+      "deprecated": true,
+      "deprecationMessage": "Use tracked properties or a native `Proxy` instead."
     },
     "@ember/reactive/collections": {
       "name": "@ember/reactive/collections",
@@ -4843,7 +4879,7 @@
       "module": "@ember/routing/route",
       "namespace": "",
       "file": "packages/@ember/routing/route.ts",
-      "line": 74,
+      "line": 83,
       "description": "The `Route` class is used to define individual routes. Refer to\nthe [routing guide](https://guides.emberjs.com/release/routing/) for documentation.",
       "extends": "EmberObject",
       "uses": [
@@ -4865,7 +4901,7 @@
       "module": "@ember/routing/router-service",
       "namespace": "",
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 28,
+      "line": 35,
       "description": "The Router service is the public API that provides access to the router.\n\nThe immediate benefit of the Router service is that you can inject it into components,\ngiving them a friendly way to initiate transitions and ask questions about the current\nglobal router state.\n\nIn this example, the Router service is injected into a component to initiate a transition\nto a dedicated route:\n\n```gjs {data-filename=\"app/components/example.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\nimport { service } from '@ember/service';\n\nexport default class ExampleComponent extends Component {\n  @service router;\n\n  @action\n  next() {\n    this.router.transitionTo('other.route');\n  }\n}\n```\n\nLike any service, it can also be injected into helpers, routes, etc.",
       "access": "public",
       "tagname": "",
@@ -4882,7 +4918,7 @@
       "module": "@ember/routing/router",
       "namespace": "",
       "file": "packages/@ember/routing/router.ts",
-      "line": 136,
+      "line": 145,
       "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": [
@@ -8094,7 +8130,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 28,
+      "line": 29,
       "description": "Add an event listener",
       "itemtype": "method",
       "name": "addListener",
@@ -8132,7 +8168,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 62,
+      "line": 63,
       "description": "Remove an event listener\n\nArguments should match those passed to `addListener`.",
       "itemtype": "method",
       "name": "removeListener",
@@ -8165,7 +8201,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 105,
+      "line": 106,
       "description": "Send an event. The execution of suspended listeners\nis skipped, and once listeners are removed. A listener without\na target is executed on the passed object. If an array of actions\nis not passed, the actions stored on the passed object are invoked.",
       "itemtype": "method",
       "name": "sendEvent",
@@ -8197,7 +8233,7 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 162,
+      "line": 163,
       "access": "public",
       "tagname": "",
       "itemtype": "method",
@@ -8223,11 +8259,13 @@
     },
     {
       "file": "packages/@ember/-internals/metal/lib/events.ts",
-      "line": 180,
+      "line": 181,
       "description": "Define a property as a function that should be executed when\na specified event or events are triggered.\n\n``` javascript\nimport EmberObject from '@ember/object';\nimport { on } from '@ember/object/evented';\nimport { sendEvent } from '@ember/object/events';\n\nlet Job = EmberObject.extend({\n  logCompleted: on('completed', function() {\n    console.log('Job completed!');\n  })\n});\n\nlet job = Job.create();\n\nsendEvent(job, 'completed'); // Logs 'Job completed!'\n ```",
       "itemtype": "method",
       "name": "on",
       "static": 1,
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "eventNames",
@@ -9236,7 +9274,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 72,
+      "line": 73,
       "description": "The object whose properties will be forwarded.",
       "itemtype": "property",
       "name": "content",
@@ -9250,7 +9288,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/-proxy.ts",
-      "line": 94,
+      "line": 95,
       "description": "The object whose properties will be forwarded.",
       "itemtype": "property",
       "name": "content",
@@ -9264,7 +9302,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/action_handler.ts",
-      "line": 28,
+      "line": 29,
       "description": "The collection of functions, keyed by name, available on this\n`ActionHandler` as action targets.\n\nThese functions will be invoked when a matching `{{action}}` is triggered\nfrom within a template and the application's current route is this route.\n\nActions can also be invoked from other parts of your application\nvia `ActionHandler#send`.\n\nThe `actions` hash will inherit action handlers from\nthe `actions` hash defined on extended parent classes\nor mixins rather than just replace the entire hash, e.g.:\n\n```app/mixins/can-display-banner.js\nimport Mixin from '@ember/object/mixin';\n\nexport default Mixin.create({\n  actions: {\n    displayBanner(msg) {\n      // ...\n    }\n  }\n});\n```\n\n```app/routes/welcome.js\nimport Route from '@ember/routing/route';\nimport CanDisplayBanner from '../mixins/can-display-banner';\n\nexport default Route.extend(CanDisplayBanner, {\n  actions: {\n    playMusic() {\n      // ...\n    }\n  }\n});\n\n// `WelcomeRoute`, when active, will be able to respond\n// to both actions, since the actions hash is merged rather\n// then replaced when extending mixins / parent classes.\nthis.send('displayBanner');\nthis.send('playMusic');\n```\n\nWithin a Controller, Route or Component's action handler,\nthe value of the `this` context is the Controller, Route or\nComponent object:\n\n```app/routes/song.js\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  actions: {\n    myAction() {\n      this.controllerFor(\"song\");\n      this.transitionTo(\"other.route\");\n      ...\n    }\n  }\n});\n```\n\nIt is also possible to call `this._super(...arguments)` from within an\naction handler if it overrides a handler defined on a parent\nclass or mixin:\n\nTake for example the following routes:\n\n```app/mixins/debug-route.js\nimport Mixin from '@ember/object/mixin';\n\nexport default Mixin.create({\n  actions: {\n    debugRouteInformation() {\n      console.debug(\"It's a-me, console.debug!\");\n    }\n  }\n});\n```\n\n```app/routes/annoying-debug.js\nimport Route from '@ember/routing/route';\nimport DebugRoute from '../mixins/debug-route';\n\nexport default Route.extend(DebugRoute, {\n  actions: {\n    debugRouteInformation() {\n      // also call the debugRouteInformation of mixed in DebugRoute\n      this._super(...arguments);\n\n      // show additional annoyance\n      window.alert(...);\n    }\n  }\n});\n```\n\n## Bubbling\n\nBy default, an action will stop bubbling once a handler defined\non the `actions` hash handles it. To continue bubbling the action,\nyou must return `true` from the handler:\n\n```app/router.js\nRouter.map(function() {\n  this.route(\"album\", function() {\n    this.route(\"song\");\n  });\n});\n```\n\n```app/routes/album.js\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  actions: {\n    startPlaying: function() {\n    }\n  }\n});\n```\n\n```app/routes/album-song.js\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  actions: {\n    startPlaying() {\n      // ...\n\n      if (actionShouldAlsoBeTriggeredOnParentRoute) {\n        return true;\n      }\n    }\n  }\n});\n```",
       "itemtype": "property",
       "name": "actions",
@@ -9280,7 +9318,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/action_handler.ts",
-      "line": 174,
+      "line": 175,
       "description": "Triggers a named action on the `ActionHandler`. Any parameters\nsupplied after the `actionName` string will be passed as arguments\nto the action target function.\n\nIf the `ActionHandler` has its `target` property set, actions may\nbubble to the `target`. Bubbling happens when an `actionName` can\nnot be found in the `ActionHandler`'s `actions` hash or if the\naction target function returns `true`.\n\nExample\n\n```app/routes/welcome.js\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  actions: {\n    playTheme() {\n      this.send('playMusic', 'theme.mp3');\n    },\n    playMusic(track) {\n      // ...\n    }\n  }\n});\n```",
       "itemtype": "method",
       "name": "send",
@@ -9306,7 +9344,7 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/comparable.ts",
-      "line": 23,
+      "line": 24,
       "description": "__Required.__ You must implement this method to apply this mixin.\n\nOverride to return the result of the comparison of the two parameters. The\ncompare method should return:\n\n- `-1` if `a < b`\n- `0` if `a == b`\n- `1` if `a > b`\n\nDefault implementation raises an exception.",
       "itemtype": "method",
       "name": "compare",
@@ -9334,13 +9372,13 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 21,
+      "line": 22,
       "class": "ContainerProxyMixin",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts",
-      "line": 25,
+      "line": 26,
       "description": "The container stores state.",
       "access": "private",
       "tagname": "",
@@ -9352,20 +9390,20 @@
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts",
-      "line": 21,
+      "line": 22,
       "class": "RegistryProxyMixin",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts",
-      "line": 32,
+      "line": 33,
       "class": "Ember.TargetActionSupport",
       "module": "ember",
       "namespace": "Ember"
     },
     {
       "file": "packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts",
-      "line": 54,
+      "line": 55,
       "description": "The following is private and vestigial.\nSend an `action` with an `actionContext` to a `target`. The action, actionContext\nand target will be retrieved from properties of the object. For example:\n\n```javascript\nimport { alias } from '@ember/object/computed';\n\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  target: alias('controller'),\n  action: 'save',\n  actionContext: alias('context'),\n  click() {\n    this.triggerAction(); // Sends the `save` action, along with the current context\n                          // to the current controller\n  }\n});\n```\n\nThe `target`, `action`, and `actionContext` can be provided as properties of\nan optional object argument to `triggerAction` as well.\n\n```javascript\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  click() {\n    this.triggerAction({\n      action: 'save',\n      target: this.get('controller'),\n      actionContext: this.get('context')\n    }); // Sends the `save` action, along with the current context\n        // to the current controller\n  }\n});\n```\n\nThe `actionContext` defaults to the object you are mixing `TargetActionSupport` into.\nBut `target` and `action` must be specified either as properties or with the argument\nto `triggerAction`, or a combination:\n\n```javascript\nimport { alias } from '@ember/object/computed';\n\nApp.SaveButtonView = Ember.View.extend(Ember.TargetActionSupport, {\n  target: alias('controller'),\n  click() {\n    this.triggerAction({\n      action: 'save'\n    }); // Sends the `save` action, along with a reference to `this`,\n        // to the current controller\n  }\n});\n```",
       "itemtype": "method",
       "name": "triggerAction",
@@ -9559,6 +9597,15 @@
       "class": "Ember",
       "module": "@ember/object"
     },
+    {
+      "file": "packages/@ember/-internals/utils/lib/internal-mixin-create.ts",
+      "line": 1,
+      "description": "Key for the internal Mixin constructor.\n\nEmber's own internals are built on mixins, so they need a way to construct\none without triggering the mixin deprecation that `Mixin.create` emits. This\nis deliberately a Symbol so that it does not show up as a discoverable\nproperty name and cannot be reached by name from application code.",
+      "access": "private",
+      "tagname": "",
+      "class": "Ember",
+      "module": "@ember/object"
+    },
     {
       "file": "packages/@ember/-internals/utils/lib/invoke.ts",
       "line": 1,
@@ -9875,7 +9922,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 38,
+      "line": 49,
       "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",
@@ -9889,7 +9936,7 @@
     },
     {
       "file": "packages/@ember/-internals/views/lib/views/core_view.ts",
-      "line": 77,
+      "line": 101,
       "description": "Override the default event firing from `Evented` to\nalso call methods with the given name.",
       "itemtype": "method",
       "name": "trigger",
@@ -10480,7 +10527,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 190,
+      "line": 191,
       "description": "__Required.__ You must implement this method to apply this mixin.\n\nYour array must support the `length` property. Your replace methods should\nset this property whenever it changes.",
       "itemtype": "property",
       "name": "length",
@@ -10492,7 +10539,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 200,
+      "line": 201,
       "description": "Returns the object at the given `index`. If the given `index` is negative\nor is greater or equal than the array length, returns `undefined`.\n\nThis is one of the primitives you must implement to support `EmberArray`.\nIf your object supports retrieving the value of an array item using `get()`\n(i.e. `myArray.get(0)`), then you do not need to implement this method\nyourself.\n\n```javascript\nlet arr = ['a', 'b', 'c', 'd'];\n\narr.objectAt(0);   // 'a'\narr.objectAt(3);   // 'd'\narr.objectAt(-1);  // undefined\narr.objectAt(4);   // undefined\narr.objectAt(5);   // undefined\n```",
       "itemtype": "method",
       "name": "objectAt",
@@ -10514,7 +10561,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 225,
+      "line": 226,
       "description": "This returns the objects at the specified indexes, using `objectAt`.\n\n```javascript\nlet arr = ['a', 'b', 'c', 'd'];\n\narr.objectsAt([0, 1, 2]);  // ['a', 'b', 'c']\narr.objectsAt([2, 3, 4]);  // ['c', 'd', undefined]\n```",
       "itemtype": "method",
       "name": "objectsAt",
@@ -10536,7 +10583,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 241,
+      "line": 242,
       "description": "This is the handler for the special array content property. If you get\nthis property, it will return this. If you set this property to a new\narray, it will replace the current content.\n\n```javascript\nlet peopleToMoon = ['Armstrong', 'Aldrin'];\n\npeopleToMoon.get('[]'); // ['Armstrong', 'Aldrin']\n\npeopleToMoon.set('[]', ['Collins']); // ['Collins']\npeopleToMoon.get('[]'); // ['Collins']\n```",
       "itemtype": "property",
       "name": "[]",
@@ -10550,7 +10597,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 261,
+      "line": 262,
       "description": "The first object in the array, or `undefined` if the array is empty.\n\n```javascript\nlet vowels = ['a', 'e', 'i', 'o', 'u'];\nvowels.firstObject; // 'a'\n\nvowels.shiftObject();\nvowels.firstObject; // 'e'\n\nvowels.reverseObjects();\nvowels.firstObject; // 'u'\n\nvowels.clear();\nvowels.firstObject; // undefined\n```",
       "itemtype": "property",
       "name": "firstObject",
@@ -10565,7 +10612,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 283,
+      "line": 284,
       "description": "The last object in the array, or `undefined` if the array is empty.",
       "itemtype": "property",
       "name": "lastObject",
@@ -10580,7 +10627,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 291,
+      "line": 292,
       "description": "Returns a new array that is a slice of the receiver. This implementation\nuses the observable array methods to retrieve the objects for the new\nslice.\n\n```javascript\nlet arr = ['red', 'green', 'blue'];\n\narr.slice(0);       // ['red', 'green', 'blue']\narr.slice(0, 2);    // ['red', 'green']\narr.slice(1, 100);  // ['green', 'blue']\n```",
       "itemtype": "method",
       "name": "slice",
@@ -10607,7 +10654,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 311,
+      "line": 312,
       "description": "Used to determine the passed object's first occurrence in the array.\nReturns the index if found, -1 if no match is found.\n\nThe optional `startAt` argument can be used to pass a starting\nindex to search from, effectively slicing the searchable portion\nof the array. If it's negative it will add the array length to\nthe startAt value passed in as the index to search from. If less\nthan or equal to `-1 * array.length` the entire array is searched.\n\n```javascript\nlet arr = ['a', 'b', 'c', 'd', 'a'];\n\narr.indexOf('a');       //  0\narr.indexOf('z');       // -1\narr.indexOf('a', 2);    //  4\narr.indexOf('a', -1);   //  4, equivalent to indexOf('a', 4)\narr.indexOf('a', -100); //  0, searches entire array\narr.indexOf('b', 3);    // -1\narr.indexOf('a', 100);  // -1\n\nlet people = [{ name: 'Zoey' }, { name: 'Bob' }]\nlet newPerson = { name: 'Tom' };\npeople = [newPerson, ...people, newPerson];\n\npeople.indexOf(newPerson);     //  0\npeople.indexOf(newPerson, 1);  //  3\npeople.indexOf(newPerson, -4); //  0\npeople.indexOf(newPerson, 10); // -1\n```",
       "itemtype": "method",
       "name": "indexOf",
@@ -10634,7 +10681,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 349,
+      "line": 350,
       "description": "Returns the index of the given `object`'s last occurrence.\n\n- If no `startAt` argument is given, the search starts from\nthe last position.\n- If it's greater than or equal to the length of the array,\nthe search starts from the last position.\n- If it's negative, it is taken as the offset from the end\nof the array i.e. `startAt + array.length`.\n- If it's any other positive number, will search backwards\nfrom that index of the array.\n\nReturns -1 if no match is found.\n\n```javascript\nlet arr = ['a', 'b', 'c', 'd', 'a'];\n\narr.lastIndexOf('a');       //  4\narr.lastIndexOf('z');       // -1\narr.lastIndexOf('a', 2);    //  0\narr.lastIndexOf('a', -1);   //  4\narr.lastIndexOf('a', -3);   //  0\narr.lastIndexOf('b', 3);    //  1\narr.lastIndexOf('a', 100);  //  4\n```",
       "itemtype": "method",
       "name": "lastIndexOf",
@@ -10661,7 +10708,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 384,
+      "line": 385,
       "description": "Iterates through the array, calling the passed function on each\nitem. This method corresponds to the `forEach()` method defined in\nJavaScript 1.6.\n\nThe callback method you provide should have the following signature (all\nparameters are optional):\n\n```javascript\nfunction(item, index, array);\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as `this` on the context. This is a good way\nto give your iterator function access to the current object.\n\nExample Usage:\n\n```javascript\nlet foods = [\n  { name: 'apple', eaten: false },\n  { name: 'banana', eaten: false },\n  { name: 'carrot', eaten: false }\n];\n\nfoods.forEach((food) => food.eaten = true);\n\nlet output = '';\nfoods.forEach((item, index, array) =>\n  output += `${index + 1}/${array.length} ${item.name}\\n`;\n);\nconsole.log(output);\n// 1/3 apple\n// 2/3 banana\n// 3/3 carrot\n```",
       "itemtype": "method",
       "name": "forEach",
@@ -10689,7 +10736,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 435,
+      "line": 436,
       "description": "Alias for `mapBy`.\n\nReturns the value of the named\nproperty on all items in the enumeration.\n\n```javascript\nlet people = [{name: 'Joe'}, {name: 'Matt'}];\n\npeople.getEach('name');\n// ['Joe', 'Matt'];\n\npeople.getEach('nonexistentProperty');\n// [undefined, undefined];\n```",
       "itemtype": "method",
       "name": "getEach",
@@ -10711,7 +10758,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 457,
+      "line": 458,
       "description": "Sets the value on the named property for each member. This is more\nergonomic than using other methods defined on this helper. If the object\nimplements Observable, the value will be changed to `set(),` otherwise\nit will be set directly. `null` objects are skipped.\n\n```javascript\nlet people = [{name: 'Joe'}, {name: 'Matt'}];\n\npeople.setEach('zipCode', '10011');\n// [{name: 'Joe', zipCode: '10011'}, {name: 'Matt', zipCode: '10011'}];\n```",
       "itemtype": "method",
       "name": "setEach",
@@ -10738,7 +10785,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 477,
+      "line": 478,
       "description": "Maps all of the items in the enumeration to another value, returning\na new array. This method corresponds to `map()` defined in JavaScript 1.6.\n\nThe callback method you provide should have the following signature (all\nparameters are optional):\n\n```javascript\nfunction(item, index, array);\nlet arr = [1, 2, 3, 4, 5, 6];\n\narr.map(element => element * element);\n// [1, 4, 9, 16, 25, 36];\n\narr.map((element, index) => element + index);\n// [1, 3, 5, 7, 9, 11];\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nIt should return the mapped value.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as `this` on the context. This is a good way\nto give your iterator function access to the current object.",
       "itemtype": "method",
       "name": "map",
@@ -10766,7 +10813,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 515,
+      "line": 516,
       "description": "Similar to map, this specialized function returns the value of the named\nproperty on all items in the enumeration.\n\n```javascript\nlet people = [{name: 'Joe'}, {name: 'Matt'}];\n\npeople.mapBy('name');\n// ['Joe', 'Matt'];\n\npeople.mapBy('unknownProperty');\n// [undefined, undefined];\n```",
       "itemtype": "method",
       "name": "mapBy",
@@ -10788,7 +10835,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 536,
+      "line": 537,
       "description": "Returns a new array with all of the items in the enumeration that the provided\ncallback function returns true for. This method corresponds to [Array.prototype.filter()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter).\n\nThe callback method should have the following signature:\n\n```javascript\nfunction(item, index, array);\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nAll parameters are optional. The function should return `true` to include the item\nin the results, and `false` otherwise.\n\nExample:\n\n```javascript\nimport { A } from '@ember/array';\nfunction isAdult(person) {\n  return person.age > 18;\n};\n\nlet people = A([{ name: 'John', age: 14 }, { name: 'Joan', age: 45 }]);\n\npeople.filter(isAdult); // returns [{ name: 'Joan', age: 45 }];\n```\n\nNote that in addition to a callback, you can pass an optional target object\nthat will be set as `this` on the context. This is a good way to give your\niterator function access to the current object. For example:\n\n```javascript\nfunction isAdultAndEngineer(person) {\n  return person.age > 18 && this.engineering;\n}\n\nclass AdultsCollection {\n  engineering = false;\n\n  constructor(opts = {}) {\n    super(...arguments);\n\n    this.engineering = opts.engineering;\n    this.people = A([{ name: 'John', age: 14 }, { name: 'Joan', age: 45 }]);\n  }\n}\n\nlet collection = new AdultsCollection({ engineering: true });\ncollection.people.filter(isAdultAndEngineer, { target: collection });\n```",
       "itemtype": "method",
       "name": "filter",
@@ -10816,7 +10863,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 600,
+      "line": 601,
       "description": "Returns an array with all of the items in the enumeration where the passed\nfunction returns false. This method is the inverse of filter().\n\nThe callback method you provide should have the following signature (all\nparameters are optional):\n\n```javascript\nfunction(item, index, array);\n```\n\n- *item* is the current item in the iteration.\n- *index* is the current index in the iteration\n- *array* is the array itself.\n\nIt should return a falsey value to include the item in the results.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as \"this\" on the context. This is a good way\nto give your iterator function access to the current object.\n\nExample Usage:\n\n```javascript\nconst food = [\n  { food: 'apple', isFruit: true },\n  { food: 'bread', isFruit: false },\n  { food: 'banana', isFruit: true }\n];\nconst nonFruits = food.reject(function(thing) {\n  return thing.isFruit;\n}); // [{food: 'bread', isFruit: false}]\n```",
       "itemtype": "method",
       "name": "reject",
@@ -10844,7 +10891,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 644,
+      "line": 645,
       "description": "Filters the array by the property and an optional value. If a value is given, it returns\nthe items that have said value for the property. If not, it returns all the items that\nhave a truthy value for the property.\n\nExample Usage:\n\n```javascript\nimport { A } from '@ember/array';\nlet things = A([{ food: 'apple', isFruit: true }, { food: 'beans', isFruit: false }]);\n\nthings.filterBy('food', 'beans'); // [{ food: 'beans', isFruit: false }]\nthings.filterBy('isFruit'); // [{ food: 'apple', isFruit: true }]\n```",
       "itemtype": "method",
       "name": "filterBy",
@@ -10872,7 +10919,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 666,
+      "line": 667,
       "description": "Returns an array with the items that do not have truthy values for the provided key.\nYou can pass an optional second argument with a target value to reject for the key.\nOtherwise this will reject objects where the provided property evaluates to false.\n\nExample Usage:\n\n```javascript\n  let food = [\n    { name: \"apple\", isFruit: true },\n    { name: \"carrot\", isFruit: false },\n    { name: \"bread\", isFruit: false },\n  ];\n  food.rejectBy('isFruit'); // [{ name: \"carrot\", isFruit: false }, { name: \"bread\", isFruit: false }]\n  food.rejectBy('name', 'carrot'); // [{ name: \"apple\", isFruit: true }}, { name: \"bread\", isFruit: false }]\n```",
       "itemtype": "method",
       "name": "rejectBy",
@@ -10900,7 +10947,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 690,
+      "line": 691,
       "description": "Returns the first item in the array for which the callback returns true.\nThis method is similar to the `find()` method defined in ECMAScript 2015.\n\nThe callback method you provide should have the following signature (all\nparameters are optional):\n\n```javascript\nfunction(item, index, array);\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nIt should return the `true` to include the item in the results, `false`\notherwise.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as `this` on the context. This is a good way\nto give your iterator function access to the current object.\n\nExample Usage:\n\n```javascript\nlet users = [\n  { id: 1, name: 'Yehuda' },\n  { id: 2, name: 'Tom' },\n  { id: 3, name: 'Melanie' },\n  { id: 4, name: 'Leah' }\n];\n\nusers.find((user) => user.name == 'Tom'); // [{ id: 2, name: 'Tom' }]\nusers.find(({ id }) => id == 3); // [{ id: 3, name: 'Melanie' }]\n```",
       "itemtype": "method",
       "name": "find",
@@ -10928,7 +10975,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 740,
+      "line": 741,
       "description": "Returns the first item with a property matching the passed value. You\ncan pass an optional second argument with the target value. Otherwise\nthis will match any property that evaluates to `true`.\n\nThis method works much like the more generic `find()` method.\n\nUsage Example:\n\n```javascript\nlet users = [\n  { id: 1, name: 'Yehuda', isTom: false },\n  { id: 2, name: 'Tom', isTom: true },\n  { id: 3, name: 'Melanie', isTom: false },\n  { id: 4, name: 'Leah', isTom: false }\n];\n\nusers.findBy('id', 4); // { id: 4, name: 'Leah', isTom: false }\nusers.findBy('name', 'Melanie'); // { id: 3, name: 'Melanie', isTom: false }\nusers.findBy('isTom'); // { id: 2, name: 'Tom', isTom: true }\n```",
       "itemtype": "method",
       "name": "findBy",
@@ -10956,7 +11003,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 770,
+      "line": 771,
       "description": "Returns `true` if the passed function returns true for every item in the\nenumeration. This corresponds with the `Array.prototype.every()` method defined in ES5.\n\nThe callback method should have the following signature:\n\n```javascript\nfunction(item, index, array);\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nAll params are optional. The method should return `true` or `false`.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as `this` on the context. This is a good way\nto give your iterator function access to the current object.\n\nUsage example:\n\n```javascript\nimport { A } from '@ember/array';\nfunction isAdult(person) {\n  return person.age > 18;\n};\n\nconst people = A([{ name: 'John', age: 24 }, { name: 'Joan', age: 45 }]);\nconst areAllAdults = people.every(isAdult);\n```",
       "itemtype": "method",
       "name": "every",
@@ -10984,7 +11031,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 812,
+      "line": 813,
       "description": "Returns `true` if the passed property resolves to the value of the second\nargument for all items in the array. This method is often simpler/faster\nthan using a callback.\n\nNote that like the native `Array.every`, `isEvery` will return true when called\non any empty array.\n```javascript\nclass Language {\n  constructor(name, isProgrammingLanguage) {\n    this.name = name;\n    this.programmingLanguage = isProgrammingLanguage;\n  }\n}\n\nconst compiledLanguages = [\n  new Language('Java', true),\n  new Language('Go', true),\n  new Language('Rust', true)\n]\n\nconst languagesKnownByMe = [\n  new Language('Javascript', true),\n  new Language('English', false),\n  new Language('Ruby', true)\n]\n\ncompiledLanguages.isEvery('programmingLanguage'); // true\nlanguagesKnownByMe.isEvery('programmingLanguage'); // false\n```",
       "itemtype": "method",
       "name": "isEvery",
@@ -11013,7 +11060,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 852,
+      "line": 853,
       "description": "The any() method executes the callback function once for each element\npresent in the array until it finds the one where callback returns a truthy\nvalue (i.e. `true`). If such an element is found, any() immediately returns\ntrue. Otherwise, any() returns false.\n\n```javascript\nfunction(item, index, array);\n```\n\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array object itself.\n\nNote that in addition to a callback, you can also pass an optional target\nobject that will be set as `this` on the context. It can be a good way\nto give your iterator function access to an object in cases where an ES6\narrow function would not be appropriate.\n\nUsage Example:\n\n```javascript\nlet includesManager = people.any(this.findPersonInManagersList, this);\n\nlet includesStockHolder = people.any(person => {\n  return this.findPersonInStockHoldersList(person)\n});\n\nif (includesManager || includesStockHolder) {\n  Paychecks.addBiggerBonus();\n}\n```",
       "itemtype": "method",
       "name": "any",
@@ -11041,7 +11088,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 895,
+      "line": 896,
       "description": "Returns `true` if the passed property resolves to the value of the second\nargument for any item in the array. This method is often simpler/faster\nthan using a callback.\n\nExample usage:\n\n```javascript\nconst food = [\n  { food: 'apple', isFruit: true },\n  { food: 'bread', isFruit: false },\n  { food: 'banana', isFruit: true }\n];\n\nfood.isAny('isFruit'); // true\n```",
       "itemtype": "method",
       "name": "isAny",
@@ -11070,7 +11117,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 921,
+      "line": 922,
       "description": "This will combine the values of the array into a single value. It\nis a useful way to collect a summary value from an array. This\ncorresponds to the `reduce()` method defined in JavaScript 1.8.\n\nThe callback method you provide should have the following signature (all\nparameters are optional):\n\n```javascript\nfunction(previousValue, item, index, array);\n```\n\n- `previousValue` is the value returned by the last call to the iterator.\n- `item` is the current item in the iteration.\n- `index` is the current index in the iteration.\n- `array` is the array itself.\n\nReturn the new cumulative value.\n\nIn addition to the callback you can also pass an `initialValue`. An error\nwill be raised if you do not pass an initial value and the enumerator is\nempty.\n\nNote that unlike the other methods, this method does not allow you to\npass a target object to set as this for the callback. It's part of the\nspec. Sorry.\n\nExample Usage:\n\n```javascript\n  let numbers = [1, 2, 3, 4, 5];\n\n  numbers.reduce(function(summation, current) {\n    return summation + current;\n  }); // 15 (1 + 2 + 3 + 4 + 5)\n\n  numbers.reduce(function(summation, current) {\n    return summation + current;\n  }, -15); // 0 (-15 + 1 + 2 + 3 + 4 + 5)\n\n\n  let binaryValues = [true, false, false];\n\n  binaryValues.reduce(function(truthValue, current) {\n    return truthValue && current;\n  }); // false (true && false && false)\n```",
       "itemtype": "method",
       "name": "reduce",
@@ -11097,7 +11144,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 979,
+      "line": 980,
       "description": "Invokes the named method on every object in the receiver that\nimplements it. This method corresponds to the implementation in\nPrototype 1.6.\n\n```javascript\nclass Person {\n  name = null;\n\n  constructor(name) {\n    this.name = name;\n  }\n\n  greet(prefix='Hello') {\n    return `${prefix} ${this.name}`;\n  }\n}\n\nlet people = [new Person('Joe'), new Person('Matt')];\n\npeople.invoke('greet'); // ['Hello Joe', 'Hello Matt']\npeople.invoke('greet', 'Bonjour'); // ['Bonjour Joe', 'Bonjour Matt']\n```",
       "itemtype": "method",
       "name": "invoke",
@@ -11124,7 +11171,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1013,
+      "line": 1014,
       "description": "Simply converts the object into a genuine array. The order is not\nguaranteed. Corresponds to the method implemented by Prototype.",
       "itemtype": "method",
       "name": "toArray",
@@ -11139,7 +11186,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1022,
+      "line": 1023,
       "description": "Returns a copy of the array with all `null` and `undefined` elements removed.\n\n```javascript\nlet arr = ['a', null, 'c', undefined];\narr.compact();  // ['a', 'c']\n```",
       "itemtype": "method",
       "name": "compact",
@@ -11154,7 +11201,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1035,
+      "line": 1036,
       "description": "Used to determine if the array contains the passed object.\nReturns `true` if found, `false` otherwise.\n\nThe optional `startAt` argument can be used to pass a starting\nindex to search from, effectively slicing the searchable portion\nof the array. If it's negative it will add the array length to\nthe startAt value passed in as the index to search from. If less\nthan or equal to `-1 * array.length` the entire array is searched.\n\nThis method has the same behavior of JavaScript's [Array.includes](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes).\n\n```javascript\n[1, 2, 3].includes(2);     // true\n[1, 2, 3].includes(4);     // false\n[1, 2, 3].includes(3, 2);  // true\n[1, 2, 3].includes(3, 3);  // false\n[1, 2, 3].includes(3, -1); // true\n[1, 2, 3].includes(1, -1); // false\n[1, 2, 3].includes(1, -4); // true\n[1, 2, NaN].includes(NaN); // true\n```",
       "itemtype": "method",
       "name": "includes",
@@ -11181,7 +11228,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1065,
+      "line": 1066,
       "description": "Sorts the array by the keys specified in the argument.\n\nYou may provide multiple arguments to sort by multiple properties.\n\n```javascript\n   let colors = [\n { name: 'red', weight: 500 },\n { name: 'green', weight: 600 },\n { name: 'blue', weight: 500 }\n];\n\n   colors.sortBy('name');\n   // [{name: 'blue', weight: 500}, {name: 'green', weight: 600}, {name: 'red', weight: 500}]\n\n   colors.sortBy('weight', 'name');\n   // [{name: 'blue', weight: 500}, {name: 'red', weight: 500}, {name: 'green', weight: 600}]\n   ```",
       "itemtype": "method",
       "name": "sortBy",
@@ -11204,7 +11251,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1090,
+      "line": 1091,
       "description": "Returns a new array that contains only unique values. The default\nimplementation returns an array regardless of the receiver type.\n\n```javascript\nlet arr = ['a', 'a', 'b', 'b'];\narr.uniq();  // ['a', 'b']\n```\n\nThis only works on primitive data types, e.g. Strings, Numbers, etc.",
       "itemtype": "method",
       "name": "uniq",
@@ -11219,7 +11266,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1106,
+      "line": 1107,
       "description": "Returns a new array that contains only items containing a unique property value.\nThe default implementation returns an array regardless of the receiver type.\n\n```javascript\nlet arr = [{ value: 'a' }, { value: 'a' }, { value: 'b' }, { value: 'b' }];\narr.uniqBy('value');  // [{ value: 'a' }, { value: 'b' }]\n\nlet arr = [2.2, 2.1, 3.2, 3.3];\narr.uniqBy(Math.floor);  // [2.2, 3.2];\n```",
       "itemtype": "method",
       "name": "uniqBy",
@@ -11241,7 +11288,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1125,
+      "line": 1126,
       "description": "Returns a new array that excludes the passed value. The default\nimplementation returns an array regardless of the receiver type.\nIf the receiver does not contain the value it returns the original array.\n\n```javascript\nlet arr = ['a', 'b', 'a', 'c'];\narr.without('a');  // ['b', 'c']\n```",
       "itemtype": "method",
       "name": "without",
@@ -11263,7 +11310,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1435,
+      "line": 1436,
       "description": "__Required.__ You must implement this method to apply this mixin.\n\nThis is one of the primitives you must implement to support `Array`.\nYou should replace amt objects started at idx with the objects in the\npassed array.\n\nNote that this method is expected to validate the type(s) of objects that it expects.",
       "itemtype": "method",
       "name": "replace",
@@ -11292,7 +11339,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1454,
+      "line": 1455,
       "description": "Remove all elements from the array. This is useful if you\nwant to reuse an existing array without having to recreate it.\n\n```javascript\nlet colors = ['red', 'green', 'blue'];\n\ncolors.length;  // 3\ncolors.clear(); // []\ncolors.length;  // 0\n```",
       "itemtype": "method",
       "name": "clear",
@@ -11307,7 +11354,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1471,
+      "line": 1472,
       "description": "This will use the primitive `replace()` method to insert an object at the\nspecified index.\n\n```javascript\nlet colors = ['red', 'green', 'blue'];\n\ncolors.insertAt(2, 'yellow');  // ['red', 'green', 'yellow', 'blue']\ncolors.insertAt(5, 'orange');  // Error: Index out of range\n```",
       "itemtype": "method",
       "name": "insertAt",
@@ -11334,7 +11381,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1489,
+      "line": 1490,
       "description": "Remove an object at the specified index using the `replace()` primitive\nmethod. You can pass either a single index, or a start and a length.\n\nIf you pass a start and length that is beyond the\nlength this method will throw an assertion.\n\n```javascript\nlet colors = ['red', 'green', 'blue', 'yellow', 'orange'];\n\ncolors.removeAt(0);     // ['green', 'blue', 'yellow', 'orange']\ncolors.removeAt(2, 2);  // ['green', 'blue']\ncolors.removeAt(4, 2);  // Error: Index out of range\n```",
       "itemtype": "method",
       "name": "removeAt",
@@ -11361,7 +11408,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1511,
+      "line": 1512,
       "description": "Push the object onto the end of the array. Works just like `push()` but it\nis KVO-compliant.\n\n```javascript\nlet colors = ['red', 'green'];\n\ncolors.pushObject('black');     // ['red', 'green', 'black']\ncolors.pushObject(['yellow']);  // ['red', 'green', ['yellow']]\n```",
       "itemtype": "method",
       "name": "pushObject",
@@ -11382,7 +11429,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1528,
+      "line": 1529,
       "description": "Add the objects in the passed array to the end of the array. Defers\nnotifying observers of the change until all objects are added.\n\n```javascript\nlet colors = ['red'];\n\ncolors.pushObjects(['yellow', 'orange']);  // ['red', 'yellow', 'orange']\n```",
       "itemtype": "method",
       "name": "pushObjects",
@@ -11404,7 +11451,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1544,
+      "line": 1545,
       "description": "Pop object from array or nil if none are left. Works just like `pop()` but\nit is KVO-compliant.\n\n```javascript\nlet colors = ['red', 'green', 'blue'];\n\ncolors.popObject();   // 'blue'\nconsole.log(colors);  // ['red', 'green']\n```",
       "itemtype": "method",
       "name": "popObject",
@@ -11418,7 +11465,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1560,
+      "line": 1561,
       "description": "Shift an object from start of array or nil if none are left. Works just\nlike `shift()` but it is KVO-compliant.\n\n```javascript\nlet colors = ['red', 'green', 'blue'];\n\ncolors.shiftObject();  // 'red'\nconsole.log(colors);   // ['green', 'blue']\n```",
       "itemtype": "method",
       "name": "shiftObject",
@@ -11432,7 +11479,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1576,
+      "line": 1577,
       "description": "Unshift an object to start of array. Works just like `unshift()` but it is\nKVO-compliant.\n\n```javascript\nlet colors = ['red'];\n\ncolors.unshiftObject('yellow');    // ['yellow', 'red']\ncolors.unshiftObject(['black']);   // [['black'], 'yellow', 'red']\n```",
       "itemtype": "method",
       "name": "unshiftObject",
@@ -11453,7 +11500,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1593,
+      "line": 1594,
       "description": "Adds the named objects to the beginning of the array. Defers notifying\nobservers until all objects have been added.\n\n```javascript\nlet colors = ['red'];\n\ncolors.unshiftObjects(['black', 'white']);   // ['black', 'white', 'red']\ncolors.unshiftObjects('yellow'); // Type Error: 'undefined' is not a function\n```",
       "itemtype": "method",
       "name": "unshiftObjects",
@@ -11475,7 +11522,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1610,
+      "line": 1611,
       "description": "Reverse objects in the array. Works just like `reverse()` but it is\nKVO-compliant.",
       "itemtype": "method",
       "name": "reverseObjects",
@@ -11490,7 +11537,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1619,
+      "line": 1620,
       "description": "Replace all the receiver's content with content of the argument.\nIf argument is an empty array receiver will be cleared.\n\n```javascript\nlet colors = ['red', 'green', 'blue'];\n\ncolors.setObjects(['black', 'white']);  // ['black', 'white']\ncolors.setObjects([]);                  // []\n```",
       "itemtype": "method",
       "name": "setObjects",
@@ -11512,7 +11559,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1637,
+      "line": 1638,
       "description": "Remove all occurrences of an object in the array.\n\n```javascript\nlet cities = ['Chicago', 'Berlin', 'Lima', 'Chicago'];\n\ncities.removeObject('Chicago');  // ['Berlin', 'Lima']\ncities.removeObject('Lima');     // ['Berlin']\ncities.removeObject('Tokyo')     // ['Berlin']\n```",
       "itemtype": "method",
       "name": "removeObject",
@@ -11534,7 +11581,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1654,
+      "line": 1655,
       "description": "Removes each object in the passed array from the receiver.",
       "itemtype": "method",
       "name": "removeObjects",
@@ -11556,7 +11603,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1663,
+      "line": 1664,
       "description": "Push the object onto the end of the array if it is not already\npresent in the array.\n\n```javascript\nlet cities = ['Chicago', 'Berlin'];\n\ncities.addObject('Lima');    // ['Chicago', 'Berlin', 'Lima']\ncities.addObject('Berlin');  // ['Chicago', 'Berlin', 'Lima']\n```",
       "itemtype": "method",
       "name": "addObject",
@@ -11578,7 +11625,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1680,
+      "line": 1681,
       "description": "Adds each object in the passed array to the receiver.",
       "itemtype": "method",
       "name": "addObjects",
@@ -11600,7 +11647,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1810,
+      "line": 1811,
       "description": "Creates an `NativeArray` from an Array-like object.\nDoes not modify the original object's contents.\n  \nThis exists primarily for historic reasons and should not be used\nin new code. Prefer native [Array](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array)\nor [trackedArray](/ember/release/functions/@ember%2Freactive%2Fcollections/trackedArray).\n\nExample\n\n```app/components/my-component.js\nimport Component from '@ember/component';\nimport { A } from '@ember/array';\n\nexport default Component.extend({\n  tagName: 'ul',\n  classNames: ['pagination'],\n\n  init() {\n    this._super(...arguments);\n\n    if (!this.get('content')) {\n      this.set('content', A());\n      this.set('otherContent', A([1,2,3]));\n    }\n  }\n});\n```",
       "itemtype": "method",
       "name": "A",
@@ -11616,70 +11663,70 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1855,
+      "line": 1856,
       "description": "The final definition of NativeArray removes all native methods. This is the list of removed methods\nwhen run in Chrome 106.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1872,
+      "line": 1873,
       "description": "These additional items must be redefined since `Omit` causes methods that return `this` to return the\ntype at the time of the Omit.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1896,
+      "line": 1897,
       "description": "Remove all elements from the array. This is useful if you\nwant to reuse an existing array without having to recreate it.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1901,
+      "line": 1902,
       "description": "This will use the primitive `replace()` method to insert an object at the\nspecified index.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1906,
+      "line": 1907,
       "description": "Remove an object at the specified index using the `replace()` primitive\nmethod. You can pass either a single index, or a start and a length.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1911,
+      "line": 1912,
       "description": "Add the objects in the passed numerable to the end of the array. Defers\nnotifying observers of the change until all objects are added.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1916,
+      "line": 1917,
       "description": "Adds the named objects to the beginning of the array. Defers notifying\nobservers until all objects have been added.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1921,
+      "line": 1922,
       "description": "Reverse objects in the array. Works just like `reverse()` but it is\nKVO-compliant.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1926,
+      "line": 1927,
       "description": "Replace all the receiver's content with content of the argument.\nIf argument is an empty array receiver will be cleared.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1931,
+      "line": 1932,
       "description": "Remove all occurrences of an object in the array.\n\n```javascript\nlet cities = ['Chicago', 'Berlin', 'Lima', 'Chicago'];\n\ncities.removeObject('Chicago');  // ['Berlin', 'Lima']\ncities.removeObject('Lima');     // ['Berlin']\ncities.removeObject('Tokyo')     // ['Berlin']\n```",
       "itemtype": "method",
       "name": "removeObject",
@@ -11701,14 +11748,14 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1948,
+      "line": 1949,
       "description": "Removes each object in the passed array from the receiver.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1952,
+      "line": 1953,
       "description": "Push the object onto the end of the array if it is not already\npresent in the array.\n\n```javascript\nlet cities = ['Chicago', 'Berlin'];\n\ncities.addObject('Lima');    // ['Chicago', 'Berlin', 'Lima']\ncities.addObject('Berlin');  // ['Chicago', 'Berlin', 'Lima']\n```",
       "itemtype": "method",
       "name": "addObject",
@@ -11730,14 +11777,14 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1969,
+      "line": 1970,
       "description": "Adds each object in the passed enumerable to the receiver.",
       "class": "@ember/array",
       "module": "ember"
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1973,
+      "line": 1974,
       "description": "Sets the value on the named property for each member. This is more\nergonomic than using other methods defined on this helper. If the object\nimplements Observable, the value will be changed to `set(),` otherwise\nit will be set directly. `null` objects are skipped.\n\n```javascript\nlet people = [{name: 'Joe'}, {name: 'Matt'}];\n\npeople.setEach('zipCode', '10011');\n// [{name: 'Joe', zipCode: '10011'}, {name: 'Matt', zipCode: '10011'}];\n```",
       "itemtype": "method",
       "name": "setEach",
@@ -11764,7 +11811,7 @@
     },
     {
       "file": "packages/@ember/array/index.ts",
-      "line": 1993,
+      "line": 1994,
       "description": "This is the handler for the special array content property. If you get\nthis property, it will return this. If you set this property to a new\narray, it will replace the current content.\n\n```javascript\nlet peopleToMoon = ['Armstrong', 'Aldrin'];\n\npeopleToMoon.get('[]'); // ['Armstrong', 'Aldrin']\n\npeopleToMoon.set('[]', ['Collins']); // ['Collins']\npeopleToMoon.get('[]'); // ['Collins']\n```",
       "itemtype": "property",
       "name": "[]",
@@ -11778,7 +11825,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 118,
+      "line": 120,
       "description": "The content array. Must be an object that implements `Array` and/or\n`MutableArray.`",
       "itemtype": "property",
       "name": "content",
@@ -11790,7 +11837,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 127,
+      "line": 129,
       "description": "The array that the proxy pretends to be. In the default `ArrayProxy`\nimplementation, this and `content` are the same. Subclasses of `ArrayProxy`\ncan override this property to provide things like sorting and filtering.",
       "itemtype": "property",
       "name": "arrangedContent",
@@ -11801,7 +11848,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 136,
+      "line": 138,
       "description": "Should actually retrieve the object at the specified index from the\ncontent. You can override this method in subclasses to transform the\ncontent item to something new.\n\nThis method will only be called if content is non-`null`.",
       "itemtype": "method",
       "name": "objectAtContent",
@@ -11823,7 +11870,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 149,
+      "line": 151,
       "description": "Should actually replace the specified objects on the content array.\nYou can override this method in subclasses to transform the content item\ninto something new.\n\nThis method will only be called if content is non-`null`.",
       "itemtype": "method",
       "name": "replaceContent",
@@ -11853,12 +11900,6 @@
       "class": "ArrayProxy",
       "module": "@ember/array/proxy"
     },
-    {
-      "file": "packages/@ember/array/proxy.ts",
-      "line": 178,
-      "class": "ArrayProxy",
-      "module": "@ember/array/proxy"
-    },
     {
       "file": "packages/@ember/array/proxy.ts",
       "line": 180,
@@ -11867,7 +11908,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 183,
+      "line": 182,
       "class": "ArrayProxy",
       "module": "@ember/array/proxy"
     },
@@ -11879,7 +11920,7 @@
     },
     {
       "file": "packages/@ember/array/proxy.ts",
-      "line": 188,
+      "line": 187,
       "class": "ArrayProxy",
       "module": "@ember/array/proxy"
     },
@@ -11913,6 +11954,12 @@
       "class": "ArrayProxy",
       "module": "@ember/array/proxy"
     },
+    {
+      "file": "packages/@ember/array/proxy.ts",
+      "line": 200,
+      "class": "ArrayProxy",
+      "module": "@ember/array/proxy"
+    },
     {
       "file": "packages/@ember/canary-features/index.ts",
       "line": 29,
@@ -12069,14 +12116,14 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 34,
+      "line": 35,
       "class": "Ember.ControllerMixin",
       "module": "@ember/controller",
       "namespace": "Ember"
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 39,
+      "line": 40,
       "description": "The object to which actions from the view should be sent.\n\nFor example, when a template uses the `{{action}}` helper,\nit will attempt to send the action to the view's controller's `target`.\n\nBy default, the value of the target property is set to the router, and\nis injected when a controller is instantiated. This injection is applied\nas part of the application's initialization process. In most cases the\n`target` property will automatically be set to the logical consumer of\nactions for the controller.",
       "itemtype": "property",
       "name": "target",
@@ -12089,7 +12136,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 57,
+      "line": 58,
       "description": "The controller's current model. When retrieving or modifying a controller's\nmodel, this property should be used instead of the `content` property.",
       "itemtype": "property",
       "name": "model",
@@ -12101,7 +12148,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 66,
+      "line": 67,
       "description": "Defines which query parameters the controller accepts.\nIf you give the names `['category','page']` it will bind\nthe values of these query parameters to the variables\n`this.category` and `this.page`.\n\nBy default, query parameters are parsed as strings. This\nmay cause unexpected behavior if a query parameter is used with `toggleProperty`,\nbecause the initial value set for `param=false` will be the string `\"false\"`, which is truthy.\n\nTo avoid this, you may specify that the query parameter should be parsed as a boolean\nby using the following verbose form with a `type` property:\n```javascript\n  queryParams: [{\n    category: {\n      type: 'boolean'\n    }\n  }]\n```\nAvailable values for the `type` parameter are `'boolean'`, `'number'`, `'array'`, and `'string'`.\nIf query param type is not specified, it will default to `'string'`.",
       "itemtype": "property",
       "name": "queryParams",
@@ -12113,7 +12160,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 94,
+      "line": 95,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\n```javascript\naController.transitionToRoute('blogPosts');\naController.transitionToRoute('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\naController.transitionToRoute('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\naController.transitionToRoute('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/router.js\nRouter.map(function() {\n  this.route('blogPost', { path: ':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId', resetNamespace: true });\n  });\n});\n```\n\n```javascript\naController.transitionToRoute('blogComment', aPost, aComment);\naController.transitionToRoute('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\naController.transitionToRoute('/');\naController.transitionToRoute('/blog/post/1/comment/13');\naController.transitionToRoute('/blog/posts?sort=title');\n```\n\nAn options hash with a `queryParams` property may be provided as\nthe final argument to add query parameters to the destination URL.\n\n```javascript\naController.transitionToRoute('blogPost', 1, {\n  queryParams: { showComments: 'true' }\n});\n\n// if you just want to transition the query parameters without changing the route\naController.transitionToRoute({ queryParams: { sort: 'date' } });\n```\n\nSee also [replaceRoute](/ember/release/classes/Ember.ControllerMixin/methods/replaceRoute?anchor=replaceRoute).",
       "itemtype": "method",
       "name": "transitionToRoute",
@@ -12150,7 +12197,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 172,
+      "line": 173,
       "description": "Transition into another route while replacing the current URL, if possible.\nThis will replace the current history entry instead of adding a new one.\nBeside that, it is identical to `transitionToRoute` in all other respects.\n\n```javascript\naController.replaceRoute('blogPosts');\naController.replaceRoute('blogPosts.recentEntries');\n```\n\nOptionally supply a model for the route in question. The model\nwill be serialized into the URL using the `serialize` hook of\nthe route:\n\n```javascript\naController.replaceRoute('blogPost', aPost);\n```\n\nIf a literal is passed (such as a number or a string), it will\nbe treated as an identifier instead. In this case, the `model`\nhook of the route will be triggered:\n\n```javascript\naController.replaceRoute('blogPost', 1);\n```\n\nMultiple models will be applied last to first recursively up the\nroute tree.\n\n```app/router.js\nRouter.map(function() {\n  this.route('blogPost', { path: ':blogPostId' }, function() {\n    this.route('blogComment', { path: ':blogCommentId', resetNamespace: true });\n  });\n});\n```\n\n```\naController.replaceRoute('blogComment', aPost, aComment);\naController.replaceRoute('blogComment', 1, 13);\n```\n\nIt is also possible to pass a URL (a string that starts with a\n`/`).\n\n```javascript\naController.replaceRoute('/');\naController.replaceRoute('/blog/post/1/comment/13');\n```",
       "itemtype": "method",
       "name": "replaceRoute",
@@ -12187,7 +12234,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 267,
+      "line": 268,
       "description": "This property is updated to various different callback functions depending on\nthe current \"state\" of the backing route. It is used by\n`Controller.prototype._qpChanged`.\n\nThe methods backing each state can be found in the `Route.prototype._qp` computed\nproperty return value (the `.states` property). The current values are listed here for\nthe sanity of future travelers:\n\n* `inactive` - This state is used when this controller instance is not part of the active\n  route hierarchy. Set in `Route.prototype._reset` (a `router.js` microlib hook) and\n  `Route.prototype.actions.finalizeQueryParamChange`.\n* `active` - This state is used when this controller instance is part of the active\n  route hierarchy. Set in `Route.prototype.actions.finalizeQueryParamChange`.\n* `allowOverrides` - This state is used in `Route.prototype.setup` (`route.js` microlib hook).",
       "itemtype": "method",
       "name": "_qpDelegate",
@@ -12199,7 +12246,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 288,
+      "line": 289,
       "description": "During `Route#setup` observers are created to invoke this method\nwhen any of the query params declared in `Controller#queryParams` property\nare changed.\n\nWhen invoked this method uses the currently active query param update delegate\n(see `Controller.prototype._qpDelegate` for details) and invokes it with\nthe QP key/value being changed.",
       "itemtype": "method",
       "name": "_qpChanged",
@@ -12211,7 +12258,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 320,
+      "line": 321,
       "description": "Creates a property that lazily looks up another controller in the container.\nCan only be used when defining another controller.\n\nExample:\n\n```app/controllers/post.js\nimport Controller, {\n  inject as controller\n} from '@ember/controller';\n\nexport default class PostController extends Controller {\n  @controller posts;\n}\n```\n\nClassic Class Example:\n\n```app/controllers/post.js\nimport Controller, {\n  inject as controller\n} from '@ember/controller';\n\nexport default Controller.extend({\n  posts: controller()\n});\n```\n\nThis example will create a `posts` property on the `post` controller that\nlooks up the `posts` controller in the container, making it easy to reference\nother controllers.",
       "itemtype": "method",
       "name": "inject",
@@ -12235,7 +12282,7 @@
     },
     {
       "file": "packages/@ember/controller/index.ts",
-      "line": 373,
+      "line": 374,
       "description": "A type registry for Ember `Controller`s. Meant to be declaration-merged so string\nlookups resolve to the correct type.\n\nBlueprints should include such a declaration merge for TypeScript:\n\n```ts\nimport Controller from '@ember/controller';\n\nexport default class ExampleController extends Controller {\n// ...\n}\n\ndeclare module '@ember/controller' {\n  export interface Registry {\n    example: ExampleController;\n  }\n}\n```\n\nThen `@inject` can check that the service is registered correctly, and APIs\nlike `owner.lookup('controller:example')` can return `ExampleController`.",
       "class": "Ember.@ember/controller",
       "module": "@ember/controller"
@@ -15214,19 +15261,19 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 233,
+      "line": 234,
       "class": "CoreObject",
       "module": "@ember/object/core"
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 237,
+      "line": 238,
       "class": "CoreObject",
       "module": "@ember/object/core"
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 317,
+      "line": 318,
       "description": "An overridable method called when objects are instantiated. By default,\ndoes nothing unless it is overridden during class definition.\n\nExample:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  init() {\n    alert(`Name is ${this.get('name')}`);\n  }\n});\n\nlet steve = Person.create({\n  name: 'Steve'\n});\n\n// alerts 'Name is Steve'.\n```\n\nNOTE: If you do override `init` for a framework class like `Component`\nfrom `@ember/component`, be sure to call `this._super(...arguments)`\nin your `init` declaration!\nIf you don't, Ember may not have an opportunity to\ndo important setup work, and you'll see strange behavior in your\napplication.",
       "itemtype": "method",
       "name": "init",
@@ -15237,7 +15284,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 351,
+      "line": 352,
       "description": "Defines the properties that will be concatenated from the superclass\n(instead of overridden).\n\nBy default, when you extend an Ember class a property defined in\nthe subclass overrides a property with the same name that is defined\nin the superclass. However, there are some cases where it is preferable\nto build up a property's value by combining the superclass' property\nvalue with the subclass' value. An example of this in use within Ember\nis the `classNames` property of `Component` from `@ember/component`.\n\nHere is some sample code showing the difference between a concatenated\nproperty and a normal one:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Bar = EmberObject.extend({\n  // Configure which properties to concatenate\n  concatenatedProperties: ['concatenatedProperty'],\n\n  someNonConcatenatedProperty: ['bar'],\n  concatenatedProperty: ['bar']\n});\n\nconst FooBar = Bar.extend({\n  someNonConcatenatedProperty: ['foo'],\n  concatenatedProperty: ['foo']\n});\n\nlet fooBar = FooBar.create();\nfooBar.get('someNonConcatenatedProperty'); // ['foo']\nfooBar.get('concatenatedProperty'); // ['bar', 'foo']\n```\n\nThis behavior extends to object creation as well. Continuing the\nabove example:\n\n```javascript\nlet fooBar = FooBar.create({\n  someNonConcatenatedProperty: ['baz'],\n  concatenatedProperty: ['baz']\n})\nfooBar.get('someNonConcatenatedProperty'); // ['baz']\nfooBar.get('concatenatedProperty'); // ['bar', 'foo', 'baz']\n```\n\nAdding a single property that is not an array will just add it in the array:\n\n```javascript\nlet fooBar = FooBar.create({\n  concatenatedProperty: 'baz'\n})\nview.get('concatenatedProperty'); // ['bar', 'foo', 'baz']\n```\n\nUsing the `concatenatedProperties` property, we can tell Ember to mix the\ncontent of the properties.\n\nIn `Component` the `classNames`, `classNameBindings` and\n`attributeBindings` properties are concatenated.\n\nThis feature is available for you to use throughout the Ember object model,\nalthough typical app developers are likely to use it infrequently. Since\nit changes expectations about behavior of properties, you should properly\ndocument its usage in each individual concatenated property (to not\nmislead your users to think they can override the property in a subclass).",
       "itemtype": "property",
       "name": "concatenatedProperties",
@@ -15250,7 +15297,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 425,
+      "line": 426,
       "description": "Defines the properties that will be merged from the superclass\n(instead of overridden).\n\nBy default, when you extend an Ember class a property defined in\nthe subclass overrides a property with the same name that is defined\nin the superclass. However, there are some cases where it is preferable\nto build up a property's value by merging the superclass property value\nwith the subclass property's value. An example of this in use within Ember\nis the `queryParams` property of routes.\n\nHere is some sample code showing the difference between a merged\nproperty and a normal one:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Bar = EmberObject.extend({\n  // Configure which properties are to be merged\n  mergedProperties: ['mergedProperty'],\n\n  someNonMergedProperty: {\n    nonMerged: 'superclass value of nonMerged'\n  },\n  mergedProperty: {\n    page: { replace: false },\n    limit: { replace: true }\n  }\n});\n\nconst FooBar = Bar.extend({\n  someNonMergedProperty: {\n    completelyNonMerged: 'subclass value of nonMerged'\n  },\n  mergedProperty: {\n    limit: { replace: false }\n  }\n});\n\nlet fooBar = FooBar.create();\n\nfooBar.get('someNonMergedProperty');\n// => { completelyNonMerged: 'subclass value of nonMerged' }\n//\n// Note the entire object, including the nonMerged property of\n// the superclass object, has been replaced\n\nfooBar.get('mergedProperty');\n// => {\n//   page: {replace: false},\n//   limit: {replace: false}\n// }\n//\n// Note the page remains from the superclass, and the\n// `limit` property's value of `false` has been merged from\n// the subclass.\n```\n\nThis behavior is not available during object `create` calls. It is only\navailable at `extend` time.\n\nIn `Route` the `queryParams` property is merged.\n\nThis feature is available for you to use throughout the Ember object model,\nalthough typical app developers are likely to use it infrequently. Since\nit changes expectations about behavior of properties, you should properly\ndocument its usage in each individual merged property (to not\nmislead your users to think they can override the property in a subclass).",
       "itemtype": "property",
       "name": "mergedProperties",
@@ -15263,7 +15310,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 500,
+      "line": 501,
       "description": "Destroyed object property flag.\n\nif this property is `true` the observers and bindings were already\nremoved by the effect of calling the `destroy()` method.",
       "itemtype": "property",
       "name": "isDestroyed",
@@ -15275,7 +15322,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 518,
+      "line": 519,
       "description": "Destruction scheduled flag. The `destroy()` method has been called.\n\nThe object stays intact until the end of the run loop at which point\nthe `isDestroyed` flag is set.",
       "itemtype": "property",
       "name": "isDestroying",
@@ -15287,7 +15334,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 536,
+      "line": 537,
       "description": "Destroys an object by setting the `isDestroyed` flag and removing its\nmetadata, which effectively destroys observers and bindings.\n\nIf you try to set a property on a destroyed object, an exception will be\nraised.\n\nNote that destruction is scheduled for the end of the run loop and does not\nhappen immediately.  It will set an isDestroying flag immediately.",
       "itemtype": "method",
       "name": "destroy",
@@ -15302,7 +15349,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 563,
+      "line": 564,
       "description": "Override to implement teardown.",
       "itemtype": "method",
       "name": "willDestroy",
@@ -15313,7 +15360,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 571,
+      "line": 572,
       "description": "Returns a string representation which attempts to provide more information\nthan Javascript's `toString` typically does, in a generic way for all Ember\nobjects.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend();\nperson = Person.create();\nperson.toString(); //=> \"<Person:ember1024>\"\n```\n\nIf the object's class is not defined on an Ember namespace, it will\nindicate it is a subclass of the registered superclass:\n\n```javascript\nconst Student = Person.extend();\nlet student = Student.create();\nstudent.toString(); //=> \"<(subclass of Person):ember1025>\"\n```\n\nIf the method `toStringExtension` is defined, its return value will be\nincluded in the output.\n\n```javascript\nconst Teacher = Person.extend({\n  toStringExtension() {\n    return this.get('fullName');\n  }\n});\nteacher = Teacher.create();\nteacher.toString(); //=> \"<Teacher:ember1026:Tom Dale>\"\n```",
       "itemtype": "method",
       "name": "toString",
@@ -15328,7 +15375,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 616,
+      "line": 617,
       "description": "Creates a new subclass.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    alert(thing);\n   }\n});\n```\n\nThis defines a new subclass of EmberObject: `Person`. It contains one method: `say()`.\n\nYou can also create a subclass from any existing class by calling its `extend()` method.\nFor example, you might want to create a subclass of Ember's built-in `Component` class:\n\n```javascript\nimport Component from '@ember/component';\n\nconst PersonComponent = Component.extend({\n  tagName: 'li',\n  classNameBindings: ['isAdministrator']\n});\n```\n\nWhen defining a subclass, you can override methods but still access the\nimplementation of your parent class by calling the special `_super()` method:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    let name = this.get('name');\n    alert(`${name} says: ${thing}`);\n  }\n});\n\nconst Soldier = Person.extend({\n  say(thing) {\n    this._super(`${thing}, sir!`);\n  },\n  march(numberOfHours) {\n    alert(`${this.get('name')} marches for ${numberOfHours} hours.`);\n  }\n});\n\nlet yehuda = Soldier.create({\n  name: 'Yehuda Katz'\n});\n\nyehuda.say('Yes');  // alerts \"Yehuda Katz says: Yes, sir!\"\n```\n\nThe `create()` on line #17 creates an *instance* of the `Soldier` class.\nThe `extend()` on line #8 creates a *subclass* of `Person`. Any instance\nof the `Person` class will *not* have the `march()` method.\n\nYou can also pass `Mixin` classes to add additional properties to the subclass.\n\n```javascript\nimport EmberObject from '@ember/object';\nimport Mixin from '@ember/object/mixin';\n\nconst Person = EmberObject.extend({\n  say(thing) {\n    alert(`${this.get('name')} says: ${thing}`);\n  }\n});\n\nconst SingingMixin = Mixin.create({\n  sing(thing) {\n    alert(`${this.get('name')} sings: la la la ${thing}`);\n  }\n});\n\nconst BroadwayStar = Person.extend(SingingMixin, {\n  dance() {\n    alert(`${this.get('name')} dances: tap tap tap tap `);\n  }\n});\n```\n\nThe `BroadwayStar` class contains three methods: `say()`, `sing()`, and `dance()`.",
       "itemtype": "method",
       "name": "extend",
@@ -15356,7 +15403,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 720,
+      "line": 721,
       "description": "Creates an instance of a class. Accepts either no arguments, or an object\ncontaining values to initialize the newly instantiated object with.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  helloWorld() {\n    alert(`Hi, my name is ${this.get('name')}`);\n  }\n});\n\nlet tom = Person.create({\n  name: 'Tom Dale'\n});\n\ntom.helloWorld(); // alerts \"Hi, my name is Tom Dale\".\n```\n\n`create` will call the `init` function if defined during\n`AnyObject.extend`\n\nIf no arguments are passed to `create`, it will not set values to the new\ninstance during initialization:\n\n```javascript\nlet noName = Person.create();\nnoName.helloWorld(); // alerts undefined\n```\n\nNOTE: For performance reasons, you cannot declare methods or computed\nproperties during `create`. You should instead declare methods and computed\nproperties when using `extend`.",
       "itemtype": "method",
       "name": "create",
@@ -15376,7 +15423,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 805,
+      "line": 806,
       "description": "Augments a constructor's prototype with additional\nproperties and functions:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst MyObject = EmberObject.extend({\n  name: 'an object'\n});\n\no = MyObject.create();\no.get('name'); // 'an object'\n\nMyObject.reopen({\n  say(msg) {\n    console.log(msg);\n  }\n});\n\no2 = MyObject.create();\no2.say('hello'); // logs \"hello\"\n\no.say('goodbye'); // logs \"goodbye\"\n```\n\nTo add functions and properties to the constructor itself,\nsee `reopenClass`",
       "itemtype": "method",
       "name": "reopen",
@@ -15388,7 +15435,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 859,
+      "line": 860,
       "description": "Augments a constructor's own properties and functions:\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst MyObject = EmberObject.extend({\n  name: 'an object'\n});\n\nMyObject.reopenClass({\n  canBuild: false\n});\n\nMyObject.canBuild; // false\no = MyObject.create();\n```\n\nIn other words, this creates static properties and functions for the class.\nThese are only available on the class and not on any instance of that class.\n\n```javascript\nimport EmberObject from '@ember/object';\n\nconst Person = EmberObject.extend({\n  name: '',\n  sayHello() {\n    alert(`Hello. My name is ${this.get('name')}`);\n  }\n});\n\nPerson.reopenClass({\n  species: 'Homo sapiens',\n\n  createPerson(name) {\n    return Person.create({ name });\n  }\n});\n\nlet tom = Person.create({\n  name: 'Tom Dale'\n});\nlet yehuda = Person.createPerson('Yehuda Katz');\n\ntom.sayHello(); // \"Hello. My name is Tom Dale\"\nyehuda.sayHello(); // \"Hello. My name is Yehuda Katz\"\nalert(Person.species); // \"Homo sapiens\"\n```\n\nNote that `species` and `createPerson` are *not* valid on the `tom` and `yehuda`\nvariables. They are only valid on `Person`.\n\nTo add functions and properties to instances of\na constructor by extending the constructor's prototype\nsee `reopen`",
       "itemtype": "method",
       "name": "reopenClass",
@@ -15400,7 +15447,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 945,
+      "line": 946,
       "description": "In some cases, you may want to annotate computed properties with additional\nmetadata about how they function or what values they operate on. For\nexample, computed property functions may close over variables that are then\nno longer available for introspection.\n\nYou can pass a hash of these values to a computed property like this:\n\n```javascript\nimport { computed } from '@ember/object';\n\nperson: computed(function() {\n  let personId = this.get('personId');\n  return Person.create({ id: personId });\n}).meta({ type: Person })\n```\n\nOnce you've done this, you can retrieve the values saved to the computed\nproperty from your class like this:\n\n```javascript\nMyClass.metaForProperty('person');\n```\n\nThis will return the original hash that was passed to `meta()`.",
       "static": 1,
       "itemtype": "method",
@@ -15419,7 +15466,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 988,
+      "line": 989,
       "description": "Iterate over each computed property for the class, passing its name\nand any associated metadata (see `metaForProperty`) to the callback.",
       "static": 1,
       "itemtype": "method",
@@ -15443,7 +15490,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 1080,
+      "line": 1081,
       "description": "Provides lookup-time type validation for injected properties.",
       "access": "private",
       "tagname": "",
@@ -15454,7 +15501,7 @@
     },
     {
       "file": "packages/@ember/object/core.ts",
-      "line": 1101,
+      "line": 1102,
       "description": "Returns a hash of property names and container names that injected\nproperties will lookup on the container lazily.",
       "itemtype": "method",
       "name": "_lazyInjections",
@@ -15469,10 +15516,12 @@
     },
     {
       "file": "packages/@ember/object/evented.ts",
-      "line": 56,
+      "line": 59,
       "description": "Subscribes to a named event with given function.\n\n```javascript\nperson.on('didLoad', function() {\n  // fired once the person has loaded\n});\n```\n\nAn optional target can be passed in as the 2nd argument that will\nbe set as the \"this\" for the callback. This is a good way to give your\nfunction access to the object triggering the event. When the target\nparameter is used the callback method becomes the third argument.",
       "itemtype": "method",
       "name": "on",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "name",
@@ -15501,10 +15550,12 @@
     },
     {
       "file": "packages/@ember/object/evented.ts",
-      "line": 83,
+      "line": 87,
       "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.\n\nThis function takes an optional 2nd argument that will become the \"this\"\nvalue for the callback. When the target parameter is used the callback method\nbecomes the third argument.",
       "itemtype": "method",
       "name": "one",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "name",
@@ -15533,10 +15584,12 @@
     },
     {
       "file": "packages/@ember/object/evented.ts",
-      "line": 105,
+      "line": 110,
       "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.\n\n```javascript\nperson.on('didEat', function(food) {\n  console.log('person ate some ' + food);\n});\n\nperson.trigger('didEat', 'broccoli');\n\n// outputs: person ate some broccoli\n```",
       "itemtype": "method",
       "name": "trigger",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "name",
@@ -15556,10 +15609,12 @@
     },
     {
       "file": "packages/@ember/object/evented.ts",
-      "line": 126,
+      "line": 132,
       "description": "Cancels subscription for given name, target, and method.",
       "itemtype": "method",
       "name": "off",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "name",
@@ -15587,10 +15642,12 @@
     },
     {
       "file": "packages/@ember/object/evented.ts",
-      "line": 142,
+      "line": 149,
       "description": "Checks to see if object has any subscriptions for named event.",
       "itemtype": "method",
       "name": "has",
+      "deprecated": true,
+      "deprecationMessage": "Use native JavaScript events or a dedicated event library instead.",
       "params": [
         {
           "name": "name",
@@ -15660,7 +15717,7 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 440,
+      "line": 442,
       "itemtype": "method",
       "name": "mixin",
       "params": [
@@ -15684,43 +15741,43 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 537,
+      "line": 539,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 540,
+      "line": 542,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 543,
+      "line": 545,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 546,
+      "line": 548,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 549,
+      "line": 551,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 554,
+      "line": 556,
       "class": "Mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 572,
+      "line": 574,
       "itemtype": "method",
       "name": "create",
       "static": 1,
@@ -15738,13 +15795,19 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 587,
+      "line": 589,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 605,
+      "line": 598,
+      "class": "@ember/object/mixin",
+      "module": "@ember/object/mixin"
+    },
+    {
+      "file": "packages/@ember/object/mixin.ts",
+      "line": 616,
       "itemtype": "method",
       "name": "reopen",
       "params": [
@@ -15762,7 +15825,7 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 628,
+      "line": 639,
       "itemtype": "method",
       "name": "apply",
       "params": [
@@ -15782,13 +15845,13 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 644,
+      "line": 655,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 649,
+      "line": 660,
       "itemtype": "method",
       "name": "detect",
       "params": [
@@ -15809,25 +15872,25 @@
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 670,
+      "line": 681,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 677,
+      "line": 688,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/mixin.ts",
-      "line": 684,
+      "line": 695,
       "class": "@ember/object/mixin",
       "module": "@ember/object/mixin"
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 96,
+      "line": 97,
       "description": "Retrieves the value of a property from the object.\n\nThis method is usually similar to using `object[keyName]` or `object.keyName`,\nhowever it supports both computed properties and the unknownProperty\nhandler.\n\nBecause `get` unifies the syntax for accessing all these kinds\nof properties, it can make many refactorings easier, such as replacing a\nsimple property with a computed property, or vice versa.\n\n### Computed Properties\n\nComputed properties are methods defined with the `property` modifier\ndeclared at the end, such as:\n\n```javascript\nimport { computed } from '@ember/object';\n\nfullName: computed('firstName', 'lastName', function() {\n  return this.get('firstName') + ' ' + this.get('lastName');\n})\n```\n\nWhen you call `get` on a computed property, the function will be\ncalled and the return value will be returned instead of the function\nitself.\n\n### Unknown Properties\n\nLikewise, if you try to call `get` on a property whose value is\n`undefined`, the `unknownProperty()` method will be called on the object.\nIf this method returns any value other than `undefined`, it will be returned\ninstead. This allows you to implement \"virtual\" properties that are\nnot defined upfront.",
       "itemtype": "method",
       "name": "get",
@@ -15849,7 +15912,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 140,
+      "line": 141,
       "description": "To get the values of multiple properties at once, call `getProperties`\nwith a list of strings or an array:\n\n```javascript\nrecord.getProperties('firstName', 'lastName', 'zipCode');\n// { firstName: 'John', lastName: 'Doe', zipCode: '10011' }\n```\n\nis equivalent to:\n\n```javascript\nrecord.getProperties(['firstName', 'lastName', 'zipCode']);\n// { firstName: 'John', lastName: 'Doe', zipCode: '10011' }\n```",
       "itemtype": "method",
       "name": "getProperties",
@@ -15871,7 +15934,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 167,
+      "line": 168,
       "description": "Sets the provided key or path to the value.\n\n```javascript\nrecord.set(\"key\", value);\n```\n\nThis method is generally very similar to calling `object[\"key\"] = value` or\n`object.key = value`, except that it provides support for computed\nproperties, the `setUnknownProperty()` method and property observers.\n\n### Computed Properties\n\nIf you try to set a value on a key that has a computed property handler\ndefined (see the `get()` method for an example), then `set()` will call\nthat method, passing both the value and key instead of simply changing\nthe value itself. This is useful for those times when you need to\nimplement a property that is composed of one or more member\nproperties.\n\n### Unknown Properties\n\nIf you try to set a value on a key that is undefined in the target\nobject, then the `setUnknownProperty()` handler will be called instead. This\ngives you an opportunity to implement complex \"virtual\" properties that\nare not predefined on the object. If `setUnknownProperty()` returns\nundefined, then `set()` will simply set the value on the object.\n\n### Property Observers\n\nIn addition to changing the property, `set()` will also register a property\nchange with the object. Unless you have placed this call inside of a\n`beginPropertyChanges()` and `endPropertyChanges(),` any \"local\" observers\n(i.e. observer methods declared on the same object), will be called\nimmediately. Any \"remote\" observers (i.e. observer methods declared on\nanother object) will be placed in a queue and called at a later time in a\ncoalesced manner.",
       "itemtype": "method",
       "name": "set",
@@ -15898,7 +15961,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 215,
+      "line": 216,
       "description": "Sets a list of properties at once. These properties are set inside\na single `beginPropertyChanges` and `endPropertyChanges` batch, so\nobservers will be buffered.\n\n```javascript\nrecord.setProperties({ firstName: 'Charles', lastName: 'Jolley' });\n```",
       "itemtype": "method",
       "name": "setProperties",
@@ -15920,7 +15983,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 232,
+      "line": 233,
       "description": "Convenience method to call `propertyWillChange` and `propertyDidChange` in\nsuccession.\n\nNotify the observer system that a property has just changed.\n\nSometimes you need to change a value directly or indirectly without\nactually calling `get()` or `set()` on it. In this case, you can use this\nmethod instead. Calling this method will notify all observers that the\nproperty has potentially changed value.",
       "itemtype": "method",
       "name": "notifyPropertyChange",
@@ -15942,7 +16005,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 250,
+      "line": 251,
       "description": "Adds an observer on a property.\n\nThis is the core method used to register an observer for a property.\n\nOnce you call this method, any time the key's value is set, your observer\nwill be notified. Note that the observers are triggered any time the\nvalue is set, regardless of whether it has actually changed. Your\nobserver should be prepared to handle that.\n\nThere are two common invocation patterns for `.addObserver()`:\n\n- Passing two arguments:\n  - the name of the property to observe (as a string)\n  - the function to invoke (an actual function)\n- Passing three arguments:\n  - the name of the property to observe (as a string)\n  - the target object (will be used to look up and invoke a\n    function on)\n  - the name of the function to invoke on the target object\n    (as a string).\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  init() {\n    this._super(...arguments);\n\n    // the following are equivalent:\n\n    // using three arguments\n    this.addObserver('foo', this, 'fooDidChange');\n\n    // using two arguments\n    this.addObserver('foo', (...args) => {\n      this.fooDidChange(...args);\n    });\n  },\n\n  fooDidChange() {\n    // your custom logic code\n  }\n});\n```\n\n### Observer Methods\n\nObserver methods have the following signature:\n\n```app/components/my-component.js\nimport Component from '@ember/component';\n\nexport default Component.extend({\n  init() {\n    this._super(...arguments);\n    this.addObserver('foo', this, 'fooDidChange');\n  },\n\n  fooDidChange(sender, key, value, rev) {\n    // your code\n  }\n});\n```\n\nThe `sender` is the object that changed. The `key` is the property that\nchanges. The `value` property is currently reserved and unused. The `rev`\nis the last property revision of the object when it changed, which you can\nuse to detect if the key value has really changed or not.\n\nUsually you will not need the value or revision parameters at\nthe end. In this case, it is common to write observer methods that take\nonly a sender and key value as parameters or, if you aren't interested in\nany of these values, to write an observer that has no parameters at all.\n\nWhile observers are still supported, there are [plans to deprecate them](https://github.com/emberjs/rfcs/pull/1115)\nSee the [in-progress deprecation guide](https://github.com/ember-learn/deprecation-app/pull/1407)\nfor guidance on how to avoid using observers.",
       "itemtype": "method",
       "name": "addObserver",
@@ -15979,7 +16042,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 340,
+      "line": 341,
       "description": "Remove an observer you have previously registered on this object. Pass\nthe same key, target, and method you passed to `addObserver()` and your\ntarget will no longer receive notifications.",
       "itemtype": "method",
       "name": "removeObserver",
@@ -16016,7 +16079,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 361,
+      "line": 362,
       "description": "Set the value of a property to the current value plus some amount.\n\n```javascript\nperson.incrementProperty('age');\nteam.incrementProperty('score', 2);\n```",
       "itemtype": "method",
       "name": "incrementProperty",
@@ -16043,7 +16106,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 378,
+      "line": 379,
       "description": "Set the value of a property to the current value minus some amount.\n\n```javascript\nplayer.decrementProperty('lives');\norc.decrementProperty('health', 5);\n```",
       "itemtype": "method",
       "name": "decrementProperty",
@@ -16070,7 +16133,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 395,
+      "line": 396,
       "description": "Set the value of a boolean property to the opposite of its\ncurrent value.\n\n```javascript\nstarship.toggleProperty('warpDriveEngaged');\n```",
       "itemtype": "method",
       "name": "toggleProperty",
@@ -16092,7 +16155,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 410,
+      "line": 411,
       "description": "Returns the cached value of a computed property, if it exists.\nThis allows you to inspect the value of a computed property\nwithout accidentally invoking it if it is intended to be\ngenerated lazily.",
       "itemtype": "method",
       "name": "cacheFor",
@@ -16114,7 +16177,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 440,
+      "line": 441,
       "description": "Begins a grouping of property changes.\n\nYou can use this method to group property changes so that notifications\nwill not be sent until the changes are finished. If you plan to make a\nlarge number of changes to an object at one time, you should call this\nmethod at the beginning of the changes to begin deferring change\nnotifications. When you are done making changes, call\n`endPropertyChanges()` to deliver the deferred change notifications and end\ndeferring.",
       "itemtype": "method",
       "name": "beginPropertyChanges",
@@ -16129,7 +16192,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 460,
+      "line": 461,
       "description": "Ends a grouping of property changes.\n\nYou can use this method to group property changes so that notifications\nwill not be sent until the changes are finished. If you plan to make a\nlarge number of changes to an object at one time, you should call\n`beginPropertyChanges()` at the beginning of the changes to defer change\nnotifications. When you are done making changes, call this method to\ndeliver the deferred change notifications and end deferring.",
       "itemtype": "method",
       "name": "endPropertyChanges",
@@ -16144,7 +16207,7 @@
     },
     {
       "file": "packages/@ember/object/observable.ts",
-      "line": 504,
+      "line": 505,
       "description": "Returns `true` if the object currently has observers registered for a\nparticular key. You can use this method to potentially defer performing\nan expensive action until someone begins observing a particular property\non the object.",
       "itemtype": "method",
       "name": "hasObserverFor",
@@ -16166,7 +16229,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 112,
+      "line": 115,
       "description": "If the proxied promise is rejected this will contain the reason\nprovided.",
       "itemtype": "property",
       "name": "reason",
@@ -16178,7 +16241,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 122,
+      "line": 125,
       "description": "Once the proxied promise has settled this will become `false`.",
       "itemtype": "property",
       "name": "isPending",
@@ -16190,7 +16253,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 130,
+      "line": 133,
       "description": "Once the proxied promise has settled this will become `true`.",
       "itemtype": "property",
       "name": "isSettled",
@@ -16202,7 +16265,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 139,
+      "line": 142,
       "description": "Will become `true` if the proxied promise is rejected.",
       "itemtype": "property",
       "name": "isRejected",
@@ -16214,7 +16277,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 147,
+      "line": 150,
       "description": "Will become `true` if the proxied promise is fulfilled.",
       "itemtype": "property",
       "name": "isFulfilled",
@@ -16226,7 +16289,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 156,
+      "line": 159,
       "description": "The promise whose fulfillment value is being proxied by this object.\n\nThis property must be specified upon creation, and should not be\nchanged once created.\n\nExample:\n\n```javascript\nimport ObjectProxy from '@ember/object/proxy';\nimport PromiseProxyMixin from '@ember/object/promise-proxy-mixin';\n\nObjectProxy.extend(PromiseProxyMixin).create({\n  promise: <thenable>\n});\n```",
       "itemtype": "property",
       "name": "promise",
@@ -16237,7 +16300,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 178,
+      "line": 181,
       "description": "An alias to the proxied promise's `then`.\n\nSee RSVP.Promise.then.",
       "itemtype": "method",
       "name": "then",
@@ -16259,7 +16322,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 189,
+      "line": 192,
       "description": "An alias to the proxied promise's `catch`.\n\nSee RSVP.Promise.catch.",
       "itemtype": "method",
       "name": "catch",
@@ -16282,7 +16345,7 @@
     },
     {
       "file": "packages/@ember/object/promise-proxy-mixin.ts",
-      "line": 201,
+      "line": 204,
       "description": "An alias to the proxied promise's `finally`.\n\nSee RSVP.Promise.finally.",
       "itemtype": "method",
       "name": "finally",
@@ -17332,7 +17395,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 86,
+      "line": 95,
       "description": "The `willTransition` action 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/route';\nimport { action } from '@ember/object';\n\nexport default class ContactFormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData')) {\n      this.controller.displayNavigationConfirm();\n      transition.abort();\n    }\n  }\n}\n```\n\nYou can also redirect elsewhere by calling\n`this.router.transitionTo('elsewhere')` from within `willTransition`.\nNote that `willTransition` will not be fired for the\nredirecting `transitionTo`, since `willTransition` doesn't\nfire when there is already a transition underway. If you want\nsubsequent `willTransition` actions to fire for the redirecting\ntransition, you must first explicitly call\n`transition.abort()`.\n\nTo allow the `willTransition` event to continue bubbling to the parent\nroute, use `return true;`. When the `willTransition` method has a\nreturn value of `true` then the parent route's `willTransition` method\nwill be fired, enabling \"bubbling\" behavior for the event.",
       "itemtype": "event",
       "name": "willTransition",
@@ -17351,7 +17414,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 131,
+      "line": 140,
       "description": "The `didTransition` action is fired after a transition has\nsuccessfully been completed. This occurs after the normal model\nhooks (`beforeModel`, `model`, `afterModel`, `setupController`)\nhave resolved. The `didTransition` action has no arguments,\nhowever, it can be useful for tracking page views or resetting\nstate on the controller.\n\n```app/routes/login.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class LoginRoute extends Route {\n  @action\n  didTransition() {\n    // your code there\n    return true; // Bubble the didTransition event\n  }\n}\n```",
       "itemtype": "event",
       "name": "didTransition",
@@ -17363,7 +17426,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 158,
+      "line": 167,
       "description": "The `loading` action is fired on the route when a route's `model`\nhook returns a promise that is not already resolved. The current\n`Transition` object is the first parameter and the route that\ntriggered the loading event is the second parameter.\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  loading(transition, route) {\n    let controller = this.controllerFor('foo');\n\n    // The controller may not be instantiated when initially loading\n    if (controller) {\n      controller.currentlyLoading = true;\n\n      transition.finally(function() {\n        controller.currentlyLoading = false;\n      });\n    }\n  }\n}\n```",
       "itemtype": "event",
       "name": "loading",
@@ -17387,7 +17450,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 193,
+      "line": 202,
       "description": "When attempting to transition into a route, any of the hooks\nmay return a promise that rejects, at which point an `error`\naction will be fired on the partially-entered routes, allowing\nfor per-route error handling logic, or shared error handling\nlogic defined on a parent route.\n\nHere is an example of an error handler that will be invoked\nfor rejected promises from the various hooks on the route,\nas well as any unhandled errors from child routes:\n\n```app/routes/admin.js\nimport { reject } from 'rsvp';\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\nimport { service } from '@ember/service';\n\nexport default class AdminRoute extends Route {\n  @service router;\n\n  beforeModel() {\n    return reject('bad things!');\n  }\n\n  @action\n  error(error, transition) {\n    // Assuming we got here due to the error in `beforeModel`,\n    // we can expect that error === \"bad things!\",\n    // but a promise model rejecting would also\n    // call this hook, as would any errors encountered\n    // in `afterModel`.\n\n    // The `error` hook is also provided the failed\n    // `transition`, which can be stored and later\n    // `.retry()`d if desired.\n\n    this.router.transitionTo('login');\n  }\n}\n```\n\n`error` actions that bubble up all the way to `ApplicationRoute`\nwill fire a default error handler that logs the error. You can\nspecify your own global default error handler by overriding the\n`error` handler on `ApplicationRoute`:\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  error(error, transition) {\n    this.controllerFor('banner').displayError(error.message);\n  }\n}\n```",
       "itemtype": "event",
       "name": "error",
@@ -17411,31 +17474,31 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 266,
+      "line": 281,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 268,
+      "line": 283,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 271,
+      "line": 286,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 273,
+      "line": 288,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 295,
+      "line": 310,
       "description": "A hook you can implement to convert the route's model into parameters\nfor the URL.\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\n```\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  model({ post_id }) {\n    // the server returns `{ id: 12 }`\n    return fetch(`/posts/${post_id}`;\n  }\n\n  serialize(model) {\n    // this will make the URL `/posts/12`\n    return { post_id: model.id };\n  }\n}\n```\n\nThe default `serialize` method will insert the model's `id` into the\nroute's dynamic segment (in this case, `:post_id`) if the segment contains '_id'.\nIf the route has multiple dynamic segments or does not contain '_id', `serialize`\nwill return `getProperties(model, params)`\n\nThis method is called when `transitionTo` is called with a context\nin order to populate the URL.",
       "itemtype": "method",
       "name": "serialize",
@@ -17463,7 +17526,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 363,
+      "line": 378,
       "description": "Configuration hash for this route's queryParams. The possible\nconfiguration options and their defaults are as follows\n(assuming a query param whose controller property is `page`):\n\n```javascript\nqueryParams = {\n  page: {\n    // By default, controller query param properties don't\n    // cause a full transition when they are changed, but\n    // rather only cause the URL to update. Setting\n    // `refreshModel` to true will cause an \"in-place\"\n    // transition to occur, whereby the model hooks for\n    // this route (and any child routes) will re-fire, allowing\n    // you to reload models (e.g., from the server) using the\n    // updated query param values.\n    refreshModel: false,\n\n    // By default, changes to controller query param properties\n    // cause the URL to update via `pushState`, which means an\n    // item will be added to the browser's history, allowing\n    // you to use the back button to restore the app to the\n    // previous state before the query param property was changed.\n    // Setting `replace` to true will use `replaceState` (or its\n    // hash location equivalent), which causes no browser history\n    // item to be added. This options name and default value are\n    // the same as the `link-to` helper's `replace` option.\n    replace: false,\n\n    // By default, the query param URL key is the same name as\n    // the controller property name. Use `as` to specify a\n    // different URL key.\n    as: 'page'\n  }\n};\n```",
       "itemtype": "property",
       "name": "queryParams",
@@ -17476,7 +17539,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 416,
+      "line": 431,
       "description": "The name of the template to use by default when rendering this route's\ntemplate.\n\n```app/routes/posts/list.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsListRoute extends Route {\n  templateName = 'posts/list';\n}\n```\n\n```app/routes/posts/index.js\nimport PostsListRoute from '../posts/list';\n\nexport default class PostsIndexRoute extends PostsListRoute {};\n```\n\n```app/routes/posts/archived.js\nimport PostsListRoute from '../posts/list';\n\nexport default class PostsArchivedRoute extends PostsListRoute {};\n```",
       "itemtype": "property",
       "name": "templateName",
@@ -17490,7 +17553,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 449,
+      "line": 464,
       "description": "The name of the controller to associate with this route.\n\nBy default, Ember will lookup a route's controller that matches the name\nof the route (i.e. `posts.new`). However,\nif you would like to define a specific controller to use, you can do so\nusing this property.\n\nThis is useful in many ways, as the controller specified will be:\n\n* passed to the `setupController` method.\n* used as the controller for the template being rendered by the route.\n* returned from a call to `controllerFor` for the route.",
       "itemtype": "property",
       "name": "controllerName",
@@ -17504,7 +17567,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 472,
+      "line": 487,
       "description": "The controller associated with this route.\n\nExample\n\n```app/routes/form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class FormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData') &&\n        !confirm('Are you sure you want to abandon progress?')) {\n      transition.abort();\n    } else {\n      // Bubble the `willTransition` action so that\n      // parent routes can decide whether or not to abort.\n      return true;\n    }\n  }\n}\n```",
       "itemtype": "property",
       "name": "controller",
@@ -17517,7 +17580,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 503,
+      "line": 518,
       "description": "The name of the route, dot-delimited.\n\nFor example, a route found at `app/routes/posts/post.js` will have\na `routeName` of `posts.post`.",
       "itemtype": "property",
       "name": "routeName",
@@ -17530,7 +17593,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 517,
+      "line": 532,
       "description": "The name of the route, dot-delimited, including the engine prefix\nif applicable.\n\nFor example, a route found at `addon/routes/posts/post.js` within an\nengine named `admin` will have a `fullRouteName` of `admin.posts.post`.",
       "itemtype": "property",
       "name": "fullRouteName",
@@ -17543,7 +17606,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 532,
+      "line": 547,
       "description": "Sets the name for this route, including a fully resolved name for routes\ninside engines.",
       "access": "private",
       "tagname": "",
@@ -17561,7 +17624,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 547,
+      "line": 562,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -17571,7 +17634,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 581,
+      "line": 596,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -17581,7 +17644,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 590,
+      "line": 605,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -17591,7 +17654,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 598,
+      "line": 613,
       "description": "Returns a hash containing the parameters of an ancestor route.\n\nYou may notice that `this.paramsFor` sometimes works when referring to a\nchild route, but this behavior should not be relied upon as only ancestor\nroutes are certain to be loaded in time.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('member', { path: ':name' }, function() {\n    this.route('interest', { path: ':interest' });\n  });\n});\n```\n\n```app/routes/member.js\nimport Route from '@ember/routing/route';\n\nexport default class MemberRoute extends Route {\n  queryParams = {\n    memberQp: { refreshModel: true }\n  }\n}\n```\n\n```app/routes/member/interest.js\nimport Route from '@ember/routing/route';\n\nexport default class MemberInterestRoute extends Route {\n  queryParams = {\n    interestQp: { refreshModel: true }\n  }\n\n  model() {\n    return this.paramsFor('member');\n  }\n}\n```\n\nIf we visit `/turing/maths?memberQp=member&interestQp=interest` the model for\nthe `member.interest` route is a hash with:\n\n* `name`: `turing`\n* `memberQp`: `member`",
       "itemtype": "method",
       "name": "paramsFor",
@@ -17614,7 +17677,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 679,
+      "line": 694,
       "description": "Serializes the query parameter key",
       "itemtype": "method",
       "name": "serializeQueryParamKey",
@@ -17632,7 +17695,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 690,
+      "line": 705,
       "description": "Serializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "serializeQueryParam",
@@ -17660,7 +17723,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 706,
+      "line": 721,
       "description": "Deserializes value of the query parameter based on defaultValueType",
       "itemtype": "method",
       "name": "deserializeQueryParam",
@@ -17688,7 +17751,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 722,
+      "line": 737,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -17698,7 +17761,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 739,
+      "line": 754,
       "description": "A hook you can use to reset controller values either when the model\nchanges or the route is exiting.\n\n```app/routes/articles.js\nimport Route from '@ember/routing/route';\n\nexport default class ArticlesRoute extends Route {\n  resetController(controller, isExiting, transition) {\n    if (isExiting && transition.targetName !== 'error') {\n      controller.set('page', 1);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "resetController",
@@ -17727,7 +17790,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 769,
+      "line": 784,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -17737,7 +17800,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 780,
+      "line": 836,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -17748,7 +17811,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 794,
+      "line": 850,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -17758,7 +17821,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 805,
+      "line": 861,
       "description": "This event is triggered when the router enters the route. It is\nnot executed when the model for the route changes.\n\n```app/routes/application.js\nimport { on } from '@ember/object/evented';\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  collectAnalytics: on('activate', function(){\n    collectAnalytics();\n  })\n});\n```",
       "itemtype": "event",
       "name": "activate",
@@ -17770,7 +17833,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 825,
+      "line": 881,
       "description": "This event is triggered when the router completely exits this\nroute. It is not executed when the model for the route changes.\n\n```app/routes/index.js\nimport { on } from '@ember/object/evented';\nimport Route from '@ember/routing/route';\n\nexport default Route.extend({\n  trackPageLeaveAnalytics: on('deactivate', function(){\n    trackPageLeaveAnalytics();\n  })\n});\n```",
       "itemtype": "event",
       "name": "deactivate",
@@ -17782,7 +17845,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 845,
+      "line": 901,
       "description": "This hook is executed when the router completely exits this route. It is\nnot executed when the model for the route changes.",
       "itemtype": "method",
       "name": "deactivate",
@@ -17801,7 +17864,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 856,
+      "line": 912,
       "description": "This hook is executed when the router enters the route. It is not executed\nwhen the model for the route changes.",
       "itemtype": "method",
       "name": "activate",
@@ -17820,7 +17883,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 867,
+      "line": 923,
       "description": "Perform a synchronous transition into another route without attempting\nto resolve promises, update the URL, or abort any currently active\nasynchronous transitions (i.e. regular transitions caused by\n`transitionTo` or URL changes).\n\nThis method is handy for performing intermediate transitions on the\nway to a final destination route, and is called internally by the\ndefault implementations of the `error` and `loading` handlers.",
       "itemtype": "method",
       "name": "intermediateTransitionTo",
@@ -17844,7 +17907,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 889,
+      "line": 945,
       "description": "Refresh the model on this route and any child routes, firing the\n`beforeModel`, `model`, and `afterModel` hooks in a similar fashion\nto how routes are entered when transitioning in from other route.\nThe current route params (e.g. `article_id`) will be passed in\nto the respective model hooks, and if a different model is returned,\n`setupController` and associated route hooks will re-fire as well.\n\nAn example usage of this method is re-querying the server for the\nlatest information using the same parameters as when the route\nwas first entered.\n\nNote that this will cause `model` hooks to fire even on routes\nthat were provided a model object when the route was initially\nentered.",
       "itemtype": "method",
       "name": "refresh",
@@ -17860,7 +17923,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 915,
+      "line": 971,
       "description": "This hook is the entry point for router.js",
       "access": "private",
       "tagname": "",
@@ -17871,7 +17934,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 990,
+      "line": 1046,
       "description": "This hook is the first of the route entry validation hooks\ncalled when an attempt is made to transition into a route\nor one of its children. It is called before `model` and\n`afterModel`, and is appropriate for cases when:\n\n1) A decision can be made to redirect elsewhere without\n   needing to resolve the model first.\n2) Any async operations need to occur first before the\n   model is attempted to be resolved.\n\nThis hook is provided the current `transition` attempt\nas a parameter, which can be used to `.abort()` the transition,\nsave it for a later `.retry()`, or retrieve values set\non it from a previous hook. You can also just call\n`router.transitionTo` to another route to implicitly\nabort the `transition`.\n\nYou can return a promise from this hook to pause the\ntransition until the promise resolves (or rejects). This could\nbe useful, for instance, for retrieving async code from\nthe server that is required to enter a route.",
       "itemtype": "method",
       "name": "beforeModel",
@@ -17894,7 +17957,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1025,
+      "line": 1081,
       "description": "This hook is called after this route's model has resolved.\nIt follows identical async/promise semantics to `beforeModel`\nbut is provided the route's resolved model in addition to\nthe `transition`, and is therefore suited to performing\nlogic that can only take place after the model has already\nresolved.\n\n```app/routes/posts.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class PostsRoute extends Route {\n  @service router;\n\n  afterModel(posts, transition) {\n    if (posts.get('length') === 1) {\n      this.router.transitionTo('post.show', posts.get('firstObject'));\n    }\n  }\n}\n```\n\nRefer to documentation for `beforeModel` for a description\nof transition-pausing semantics when a promise is returned\nfrom this hook.",
       "itemtype": "method",
       "name": "afterModel",
@@ -17922,7 +17985,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1069,
+      "line": 1125,
       "description": "A hook you can implement to optionally redirect to another route.\n\nCalling `this.router.transitionTo` from inside of the `redirect` hook will\nabort the current transition (into the route that has implemented `redirect`).\n\n`redirect` and `afterModel` behave very similarly and are\ncalled almost at the same time, but they have an important\ndistinction when calling `this.router.transitionTo` to a child route\nof the current route. From `afterModel`, this new transition\ninvalidates the current transition, causing `beforeModel`,\n`model`, and `afterModel` hooks to be called again. But the\nsame transition started from `redirect` does _not_ invalidate\nthe current transition. In other words, by the time the `redirect`\nhook has been called, both the resolved model and the attempted\nentry into this route are considered fully validated.",
       "itemtype": "method",
       "name": "redirect",
@@ -17946,7 +18009,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1094,
+      "line": 1150,
       "description": "Called when the context is changed by router.js.",
       "access": "private",
       "tagname": "",
@@ -17957,7 +18020,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1104,
+      "line": 1160,
       "description": "A hook you can implement to convert the URL into the model for\nthis route.\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nNote that for routes with dynamic segments, this hook is not always\nexecuted. If the route is entered through a transition (e.g. when\nusing the `link-to` helper or the `transitionTo` method\nof routes), and a model context is already provided this hook\nis not called.\n\nA model context does not include a primitive string or number,\nwhich does cause the model hook to be called.\n\nRoutes without dynamic segments will always execute the model hook.\n\n```javascript\n// no dynamic segment, model hook always called\nthis.router.transitionTo('posts');\n\n// model passed in, so model hook not called\nthePost = store.findRecord('post', 1);\nthis.router.transitionTo('post', thePost);\n\n// integer passed in, model hook is called\nthis.router.transitionTo('post', 1);\n\n// model id passed in, model hook is called\n// useful for forcing the hook to execute\nthePost = store.findRecord('post', 1);\nthis.router.transitionTo('post', thePost.id);\n```\n\nThis hook follows the asynchronous/promise semantics\ndescribed in the documentation for `beforeModel`. In particular,\nif a promise returned from `model` fails, the error will be\nhandled by the `error` hook on `Route`.\n\nNote that the legacy behavior of automatically defining a model\nhook when a dynamic segment ending in `_id` is present is\n[deprecated](https://deprecations.emberjs.com/v5.x#toc_deprecate-implicit-route-model).\nYou should explicitly define a model hook whenever any segments are\npresent.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class PostRoute extends Route {\n  @service store;\n\n  model(params) {\n    return this.store.findRecord('post', params.post_id);\n  }\n}\n```",
       "itemtype": "method",
       "name": "model",
@@ -17985,7 +18048,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1221,
+      "line": 1277,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -18011,7 +18074,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1234,
+      "line": 1290,
       "description": "A hook you can use to setup the controller for the current route.\n\nThis method is called with the controller for the current route and the\nmodel supplied by the `model` hook.\n\nBy default, the `setupController` hook sets the `model` property of\nthe controller to the specified `model` when it is not `undefined`.\n\nIf you implement the `setupController` hook in your Route, it will\nprevent this default behavior. If you want to preserve that behavior\nwhen implementing your `setupController` function, make sure to call\n`super`:\n\n```app/routes/photos.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class PhotosRoute extends Route {\n  @service store;\n\n  model() {\n    return this.store.findAll('photo');\n  }\n\n  setupController(controller, model) {\n    super.setupController(controller, model);\n\n    this.controllerFor('application').set('showingPhotos', true);\n  }\n}\n```\n\nThe provided controller will be one resolved based on the name\nof this route.\n\nIf no explicit controller is defined, Ember will automatically create one.\n\nAs an example, consider the router:\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' });\n});\n\nexport default Router;\n```\n\nIf you have defined a file for the post controller,\nthe framework will use it.\nIf it is not defined, a basic `Controller` instance would be used.\n\nExample Behavior of a basic Controller\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  setupController(controller, model) {\n    controller.set('model', model);\n  }\n});\n```",
       "itemtype": "method",
       "name": "setupController",
@@ -18041,7 +18104,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1313,
+      "line": 1369,
       "description": "Returns the controller of the current route, or a parent (or any ancestor)\nroute in a route hierarchy.\n\nThe controller instance must already have been created, either through entering the\nassociated route or using `generateController`.\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class PostRoute extends Route {\n  setupController(controller, post) {\n    super.setupController(controller, post);\n\n    this.controllerFor('posts').set('currentPost', post);\n  }\n}\n```",
       "itemtype": "method",
       "name": "controllerFor",
@@ -18064,7 +18127,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1367,
+      "line": 1423,
       "description": "Generates a controller for a route.\n\nExample\n\n```app/routes/post.js\nimport Route from '@ember/routing/route';\n\nexport default class Post extends Route {\n  setupController(controller, post) {\n    super.setupController(controller, post);\n\n    this.generateController('posts');\n  }\n}\n```",
       "itemtype": "method",
       "name": "generateController",
@@ -18082,7 +18145,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1395,
+      "line": 1451,
       "description": "Returns the resolved model of a parent (or any ancestor) route\nin a route hierarchy.  During a transition, all routes\nmust resolve a model object, and if a route\nneeds access to a parent route's model in order to\nresolve a model (or just reuse the model from a parent),\nit can call `this.modelFor(theNameOfParentRoute)` to\nretrieve it. If the ancestor route's model was a promise,\nits resolved result is returned.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('post', { path: '/posts/:post_id' }, function() {\n    this.route('comments');\n  });\n});\n\nexport default Router;\n```\n\n```app/routes/post/comments.js\nimport Route from '@ember/routing/route';\n\nexport default class PostCommentsRoute extends Route {\n  model() {\n    let post = this.modelFor('post');\n\n    return post.comments;\n  }\n}\n```",
       "itemtype": "method",
       "name": "modelFor",
@@ -18105,7 +18168,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1469,
+      "line": 1525,
       "description": "`this[RENDER]` is used to set up the rendering option for the outlet state.",
       "itemtype": "method",
       "name": "this[RENDER]",
@@ -18116,7 +18179,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1483,
+      "line": 1539,
       "access": "private",
       "tagname": "",
       "itemtype": "method",
@@ -18126,7 +18189,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1495,
+      "line": 1551,
       "description": "Allows you to produce custom metadata for the route.\nThe return value of this method will be attached to\nits corresponding RouteInfoWithAttributes object.\n\nExample\n\n```app/routes/posts/index.js\nimport Route from '@ember/routing/route';\n\nexport default class PostsIndexRoute extends Route {\n  buildRouteInfoMetadata() {\n    return { title: 'Posts Page' }\n  }\n}\n```\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { service } from '@ember/service';\n\nexport default class ApplicationRoute extends Route {\n  @service router\n\n  constructor() {\n    super(...arguments);\n\n    this.router.on('routeDidChange', transition => {\n      document.title = transition.to.metadata.title;\n      // would update document's title to \"Posts Page\"\n    });\n  }\n}\n```",
       "itemtype": "method",
       "name": "buildRouteInfoMetadata",
@@ -18141,13 +18204,13 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1546,
+      "line": 1602,
       "class": "Route",
       "module": "@ember/routing/route"
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1595,
+      "line": 1651,
       "access": "private",
       "tagname": "",
       "itemtype": "property",
@@ -18157,7 +18220,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 1734,
+      "line": 1790,
       "description": "Sends an action to the router, which will delegate it to the currently\nactive route hierarchy per the bubbling rules explained under `actions`.\n\nExample\n\n```app/router.js\n// ...\n\nRouter.map(function() {\n  this.route('index');\n});\n\nexport default Router;\n```\n\n```app/routes/application.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class ApplicationRoute extends Route {\n  @action\n  track(arg) {\n    console.log(arg, 'was clicked');\n  }\n}\n```\n\n```app/routes/index.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class IndexRoute extends Route {\n  @action\n  trackIfDebug(arg) {\n    if (debug) {\n      this.send('track', arg);\n    }\n  }\n}\n```",
       "itemtype": "method",
       "name": "send",
@@ -18181,7 +18244,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2064,
+      "line": 2120,
       "description": "The controller associated with this route.\n\nExample\n\n```app/routes/form.js\nimport Route from '@ember/routing/route';\nimport { action } from '@ember/object';\n\nexport default class FormRoute extends Route {\n  @action\n  willTransition(transition) {\n    if (this.controller.get('userHasEnteredData') &&\n        !confirm('Are you sure you want to abandon progress?')) {\n      transition.abort();\n    } else {\n      // Bubble the `willTransition` action so that\n      // parent routes can decide whether or not to abort.\n      return true;\n    }\n  }\n}\n```",
       "itemtype": "property",
       "name": "controller",
@@ -18194,7 +18257,7 @@
     },
     {
       "file": "packages/@ember/routing/route.ts",
-      "line": 2095,
+      "line": 2151,
       "description": "This action is called when one or more query params have changed. Bubbles.",
       "itemtype": "method",
       "name": "queryParamsDidChange",
@@ -18226,7 +18289,141 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 90,
+      "line": 69,
+      "description": "Subscribes to a named event with given function.",
+      "itemtype": "method",
+      "name": "on",
+      "params": [
+        {
+          "name": "name",
+          "description": "The name of the event",
+          "type": "String"
+        },
+        {
+          "name": "target",
+          "description": "The \"this\" binding for the callback",
+          "type": "Object",
+          "optional": true
+        },
+        {
+          "name": "method",
+          "description": "A function or the name of a function to be called on `target`",
+          "type": "Function|String"
+        }
+      ],
+      "return": {
+        "description": "this"
+      },
+      "class": "RouterService",
+      "module": "@ember/routing/router-service"
+    },
+    {
+      "file": "packages/@ember/routing/router-service.ts",
+      "line": 95,
+      "description": "Subscribes a function to a named event and then cancels the subscription\nafter the first time the event is triggered.",
+      "itemtype": "method",
+      "name": "one",
+      "params": [
+        {
+          "name": "name",
+          "description": "The name of the event",
+          "type": "String"
+        },
+        {
+          "name": "target",
+          "description": "The \"this\" binding for the callback",
+          "type": "Object",
+          "optional": true
+        },
+        {
+          "name": "method",
+          "description": "A function or the name of a function to be called on `target`",
+          "type": "Function|String"
+        }
+      ],
+      "return": {
+        "description": "this"
+      },
+      "class": "RouterService",
+      "module": "@ember/routing/router-service"
+    },
+    {
+      "file": "packages/@ember/routing/router-service.ts",
+      "line": 121,
+      "description": "Triggers a named event for the object.",
+      "itemtype": "method",
+      "name": "trigger",
+      "params": [
+        {
+          "name": "name",
+          "description": "The name of the event",
+          "type": "String"
+        },
+        {
+          "name": "args",
+          "description": "Optional arguments to pass on",
+          "type": "Object..."
+        }
+      ],
+      "return": {
+        "description": "true if listeners were notified, false otherwise",
+        "type": "Boolean"
+      },
+      "class": "RouterService",
+      "module": "@ember/routing/router-service"
+    },
+    {
+      "file": "packages/@ember/routing/router-service.ts",
+      "line": 133,
+      "description": "Cancels subscription for given name, target, and method.",
+      "itemtype": "method",
+      "name": "off",
+      "params": [
+        {
+          "name": "name",
+          "description": "The name of the event",
+          "type": "String"
+        },
+        {
+          "name": "target",
+          "description": "The target of the subscription",
+          "type": "Object"
+        },
+        {
+          "name": "method",
+          "description": "The function or the name of a function of the subscription",
+          "type": "Function|String"
+        }
+      ],
+      "return": {
+        "description": "this"
+      },
+      "class": "RouterService",
+      "module": "@ember/routing/router-service"
+    },
+    {
+      "file": "packages/@ember/routing/router-service.ts",
+      "line": 158,
+      "description": "Checks to see if object has any subscriptions for named event.",
+      "itemtype": "method",
+      "name": "has",
+      "params": [
+        {
+          "name": "name",
+          "description": "The name of the event",
+          "type": "String"
+        }
+      ],
+      "return": {
+        "description": "does the object have a subscription for event",
+        "type": "Boolean"
+      },
+      "class": "RouterService",
+      "module": "@ember/routing/router-service"
+    },
+    {
+      "file": "packages/@ember/routing/router-service.ts",
+      "line": 191,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:\n\nCalling `transitionTo` from the Router service will cause default query parameter values to be included in the URL.\nThis behavior is different from calling `transitionTo` on a route or `transitionToRoute` on a controller.\nSee the [Router Service RFC](https://github.com/emberjs/rfcs/blob/master/text/0095-router-service.md#query-parameter-semantics) for more info.\n\nIn the following example we use the Router service to navigate to a route with a\nspecific model from a Component in the first action, and in the second we trigger\na query-params only transition.\n\n```gjs {data-filename=\"app/components/example.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\nimport { service } from '@ember/service';\n\nexport default class extends Component {\n  @service router;\n\n  @action\n  goToComments(post) {\n    this.router.transitionTo('comments', post);\n  }\n\n  @action\n  fetchMoreComments(latestComment) {\n    this.router.transitionTo({\n      queryParams: { commentsAfter: latestComment }\n    });\n  }\n}\n```",
       "itemtype": "method",
       "name": "transitionTo",
@@ -18261,7 +18458,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 149,
+      "line": 250,
       "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';\nimport { service } from '@ember/service';\n\nexport default class extends Route {\n  @service router;\n  beforeModel() {\n    if (!authorized()){\n      this.router.replaceWith('unauthorized');\n    }\n  }\n});\n```",
       "itemtype": "method",
       "name": "replaceWith",
@@ -18294,7 +18491,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 190,
+      "line": 291,
       "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```gjs {data-filename=\"app/templates/application.gjs\"}\nimport CopyLink from '../components/copy-link';\n  \n<template>\n  <CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/copy-link.gjs\"}\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```gjs {data-filename=\"app/templates/application.gjs\"}\nimport CopyLink from '../components/copy-link';\n\n<template>\n  <CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/copy-link.gjs\"}\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",
@@ -18327,7 +18524,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 274,
+      "line": 375,
       "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```gjs {data-filename=\"app/components/posts.gjs\"}\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```gjs {data-filename=\"app/components/posts.gjs\"}\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",
@@ -18360,7 +18557,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 379,
+      "line": 480,
       "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```js\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",
@@ -18382,7 +18579,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 420,
+      "line": 521,
       "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",
@@ -18404,7 +18601,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 442,
+      "line": 543,
       "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",
@@ -18427,7 +18624,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 469,
+      "line": 570,
       "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 ContactFormRoute 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}\n```",
       "itemtype": "method",
       "name": "off",
@@ -18450,7 +18647,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 502,
+      "line": 603,
       "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",
@@ -18468,7 +18665,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 536,
+      "line": 637,
       "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",
@@ -18486,7 +18683,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 576,
+      "line": 677,
       "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",
@@ -18508,7 +18705,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 604,
+      "line": 705,
       "description": "Name of the current route.\n\n This property represents the logical name of the route,\n which is dot 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",
@@ -18520,7 +18717,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 634,
+      "line": 735,
       "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",
@@ -18532,7 +18729,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 663,
+      "line": 764,
       "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`hash`, `history`, `none`.\n\nSee [HashLocation](/ember/release/classes/HashLocation).\nSee [HistoryLocation](/ember/release/classes/HistoryLocation).\nSee [NoneLocation](/ember/release/classes/NoneLocation).",
       "itemtype": "property",
       "name": "location",
@@ -18547,7 +18744,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 702,
+      "line": 803,
       "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",
@@ -18559,7 +18756,7 @@
     },
     {
       "file": "packages/@ember/routing/router-service.ts",
-      "line": 732,
+      "line": 833,
       "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```gjs {data-filename=\"app/components/header.gjs\"}\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",
@@ -18571,7 +18768,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 146,
+      "line": 161,
       "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",
@@ -18583,7 +18780,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 157,
+      "line": 172,
       "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 `history` by the `locationType` setting of `/config/environment.js`",
       "itemtype": "property",
       "name": "location",
@@ -18598,7 +18795,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 215,
+      "line": 265,
       "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",
@@ -18615,7 +18812,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 550,
+      "line": 600,
       "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",
@@ -18626,7 +18823,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 701,
+      "line": 751,
       "description": "Transition the application into another route. The route may\nbe either a single route or route path:",
       "itemtype": "method",
       "name": "transitionTo",
@@ -18660,7 +18857,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 746,
+      "line": 796,
       "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",
@@ -18694,7 +18891,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 773,
+      "line": 823,
       "description": "Determines if the supplied route is currently active.",
       "itemtype": "method",
       "name": "isActive",
@@ -18715,7 +18912,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 785,
+      "line": 835,
       "description": "An alternative form of `isActive` that doesn't require\nmanual concatenation of the arguments into a single\narray.",
       "itemtype": "method",
       "name": "isActiveIntent",
@@ -18745,7 +18942,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 811,
+      "line": 861,
       "description": "Does this router instance have the given route.",
       "itemtype": "method",
       "name": "hasRoute",
@@ -18760,7 +18957,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 822,
+      "line": 872,
       "description": "Resets the state of the router by clearing the current route\nhandlers and deactivating them.",
       "access": "private",
       "tagname": "",
@@ -18771,7 +18968,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 921,
+      "line": 971,
       "description": "Serializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -18798,7 +18995,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 951,
+      "line": 1001,
       "description": "Serializes the value of a query parameter based on a type",
       "access": "private",
       "tagname": "",
@@ -18821,7 +19018,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 969,
+      "line": 1019,
       "description": "Deserializes the given query params according to their QP meta information.",
       "access": "private",
       "tagname": "",
@@ -18848,7 +19045,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 997,
+      "line": 1047,
       "description": "Deserializes the value of a query parameter based on a default type",
       "access": "private",
       "tagname": "",
@@ -18871,7 +19068,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1018,
+      "line": 1068,
       "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": "",
@@ -18898,7 +19095,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1100,
+      "line": 1150,
       "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": "",
@@ -18935,7 +19132,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1127,
+      "line": 1177,
       "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": "",
@@ -18957,7 +19154,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1141,
+      "line": 1191,
       "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": "",
@@ -18979,7 +19176,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1203,
+      "line": 1253,
       "description": "Maps all query param keys to their fully scoped property name of the form\n`controllerName:propName`.",
       "access": "private",
       "tagname": "",
@@ -19011,7 +19208,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1245,
+      "line": 1295,
       "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": "",
@@ -19038,7 +19235,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1416,
+      "line": 1466,
       "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\nexport default class Router extends EmberRouter {\n  location = config.locationType;\n\n  @service()\n  router;\n\n  didTransition() {\n    super.didTransition(...arguments);\n\n    ga('send', 'pageview', {\n      page: this.router.currentURL,\n      title: this.router.currentRouteName,\n    });\n  }\n}\n```",
       "itemtype": "method",
       "name": "didTransition",
@@ -19050,7 +19247,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1454,
+      "line": 1504,
       "description": "Handles notifying any listeners of an impending URL\nchange.\n\nTriggers the router level `willTransition` hook.",
       "itemtype": "method",
       "name": "willTransition",
@@ -19062,7 +19259,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1467,
+      "line": 1517,
       "description": "Represents the current URL.",
       "itemtype": "property",
       "name": "url",
@@ -19074,7 +19271,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1630,
+      "line": 1680,
       "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": "",
@@ -19099,7 +19296,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1651,
+      "line": 1701,
       "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": "",
@@ -19124,7 +19321,7 @@
     },
     {
       "file": "packages/@ember/routing/router.ts",
-      "line": 1673,
+      "line": 1723,
       "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": "",
@@ -20275,7 +20472,7 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "line": 10,
       "description": "This provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
       "internal": "This is exported so declaration emit works (if it were not emitted,\n  declarations which fall back to it would not work). It is *not* intended for\n  public usage, and the specific mechanics it uses may change at any time.\n  The location of this export *is* part of the public API, because moving it\n  will break existing declarations, but is not legal for end users to import\n  themselves, so ***DO NOT RELY ON IT***.",
@@ -20283,13 +20480,13 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "line": 30,
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "line": 62,
       "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
       "internal": "This is only exported so we can avoid duplicating it in\n  [Glint](https://github.com/typed-ember/glint) or other such tooling. It is\n  *not* intended for public usage, and the specific mechanics it uses may\n  change at any time. Although the signature produced by is part of Glimmer's\n  public API the existence and mechanics of this specific symbol are *not*,\n  so ***DO NOT RELY ON IT***.",
@@ -20297,22 +20494,22 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "line": 74,
       "internal": "we use this type for convenience internally; inference means users\n  should not normally need to name it",
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
       "line": 79,
       "description": "The `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
-      "line": 203,
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
+      "line": 205,
       "description": "Constructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
       "params": [
         {
@@ -20328,65 +20525,65 @@
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
-      "line": 212,
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
+      "line": 214,
       "description": "Named arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
-      "line": 239,
+      "file": "packages/@glimmer/component/dist/component/src/-private/component.d.ts",
+      "line": 241,
       "description": "Called before the component has been removed from the DOM.",
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/-private/ember-component-manager.d.ts",
+      "file": "packages/@glimmer/component/dist/component/src/-private/ember-component-manager.d.ts",
       "line": 4,
       "description": "This component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
       "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 32,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 25,
       "description": "This provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
       "internal": "This is exported so declaration emit works (if it were not emitted,\n  declarations which fall back to it would not work). It is *not* intended for\n  public usage, and the specific mechanics it uses may change at any time.\n  The location of this export *is* part of the public API, because moving it\n  will break existing declarations, but is not legal for end users to import\n  themselves, so ***DO NOT RELY ON IT***.",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 47,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 40,
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 49,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 42,
       "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
       "internal": "This is only exported so we can avoid duplicating it in\n  [Glint](https://github.com/typed-ember/glint) or other such tooling. It is\n  *not* intended for public usage, and the specific mechanics it uses may\n  change at any time. Although the signature produced by is part of Glimmer's\n  public API the existence and mechanics of this specific symbol are *not*,\n  so ***DO NOT RELY ON IT***.",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 66,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 59,
       "internal": "we use this type for convenience internally; inference means users\n  should not normally need to name it",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 71,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 64,
       "description": "The `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 195,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 191,
       "description": "Constructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
       "params": [
         {
@@ -20402,29 +20599,103 @@
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 212,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 206,
       "description": "Named arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 244,
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 238,
+      "description": "Called before the component has been removed from the DOM.",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/dev/index.js",
+      "line": 273,
+      "description": "This component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 13,
+      "description": "This provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
+      "internal": "This is exported so declaration emit works (if it were not emitted,\n  declarations which fall back to it would not work). It is *not* intended for\n  public usage, and the specific mechanics it uses may change at any time.\n  The location of this export *is* part of the public API, because moving it\n  will break existing declarations, but is not legal for end users to import\n  themselves, so ***DO NOT RELY ON IT***.",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 28,
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 30,
+      "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
+      "internal": "This is only exported so we can avoid duplicating it in\n  [Glint](https://github.com/typed-ember/glint) or other such tooling. It is\n  *not* intended for public usage, and the specific mechanics it uses may\n  change at any time. Although the signature produced by is part of Glimmer's\n  public API the existence and mechanics of this specific symbol are *not*,\n  so ***DO NOT RELY ON IT***.",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 47,
+      "internal": "we use this type for convenience internally; inference means users\n  should not normally need to name it",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 52,
+      "description": "The `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 179,
+      "description": "Constructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
+      "params": [
+        {
+          "name": "owner",
+          "description": ""
+        },
+        {
+          "name": "args",
+          "description": ""
+        }
+      ],
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 191,
+      "description": "Named arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 223,
       "description": "Called before the component has been removed from the DOM.",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
-      "file": "packages/@glimmer/component/dist/index.js",
-      "line": 279,
+      "file": "packages/@glimmer/component/dist/prod/index.js",
+      "line": 255,
       "description": "This component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 36,
+      "line": 29,
       "description": "This provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
       "internal": "This is exported so declaration emit works (if it were not emitted,\n  declarations which fall back to it would not work). It is *not* intended for\n  public usage, and the specific mechanics it uses may change at any time.\n  The location of this export *is* part of the public API, because moving it\n  will break existing declarations, but is not legal for end users to import\n  themselves, so ***DO NOT RELY ON IT***.",
       "class": "Keywords",
@@ -20432,13 +20703,13 @@
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 56,
+      "line": 49,
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 79,
+      "line": 72,
       "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
       "internal": "This is only exported so we can avoid duplicating it in\n  [Glint](https://github.com/typed-ember/glint) or other such tooling. It is\n  *not* intended for public usage, and the specific mechanics it uses may\n  change at any time. Although the signature produced by is part of Glimmer's\n  public API the existence and mechanics of this specific symbol are *not*,\n  so ***DO NOT RELY ON IT***.",
       "class": "Keywords",
@@ -20446,21 +20717,21 @@
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 97,
+      "line": 90,
       "internal": "we use this type for convenience internally; inference means users\n  should not normally need to name it",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 103,
+      "line": 96,
       "description": "The `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 227,
+      "line": 223,
       "description": "Constructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
       "params": [
         {
@@ -20477,14 +20748,14 @@
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 248,
+      "line": 241,
       "description": "Named arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
       "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 282,
+      "line": 275,
       "description": "Called before the component has been removed from the DOM.",
       "class": "Keywords",
       "module": "@glimmer/component"
@@ -20805,6 +21076,12 @@
       "class": "Keywords",
       "module": "@glimmer/component"
     },
+    {
+      "file": "packages/@glimmer/destroyable/index.ts",
+      "line": 241,
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 4,
@@ -21942,21 +22219,21 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 136,
+      "line": 146,
       "description": "Fetch a value from a syscall register onto the stack.\n\n## Opcodes\n\n- Append: `Fetch`\n\n## State changes\n\n[!] push Eval Stack <- $register",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 153,
+      "line": 163,
       "description": "Load a value from the stack into a syscall register.\n\n## Opcodes\n\n- Append: `Load`\n\n## State changes\n\n[!] pop Eval Stack -> `value`\n[$] $register <- `value`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 171,
+      "line": 181,
       "description": "Load a value into a syscall register.\n\n## State changes\n\n[$] $register <- `value`",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -21964,7 +22241,7 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 184,
+      "line": 194,
       "description": "Fetch a value from a register (machine or syscall).\n\n## State changes\n\n[ ] get $register",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -21972,105 +22249,105 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 327,
+      "line": 337,
       "description": "## Opcodes\n\n- Append: `BeginComponentTransaction`\n\n## State Changes\n\n[ ] create `guard` (`JumpIfNotModifiedOpcode`)\n[ ] create `tracker` (`BeginTrackFrameOpcode`)\n[!] push Updating Stack <- `guard`\n[!] push Updating Stack <- `tracker`\n[!] push Cache Stack <- `guard`\n[!] push Tracking Stack",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 352,
+      "line": 362,
       "description": "## Opcodes\n\n- Append: `CommitComponentTransaction`\n\n## State Changes\n\nCreate a new `EndTrackFrameOpcode` (`end`)\n\n[!] pop CacheStack -> `guard`\n[!] pop Tracking Stack -> `tag`\n[ ] create `end` (`EndTrackFrameOpcode`) with `guard`\n[-] consume `tag`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 376,
+      "line": 386,
       "description": "## Opcodes\n\n- Append: `Enter`\n\n## State changes\n\n[!] push Element Stack as `block`\n[ ] create `try` (`TryOpcode`) with `block`, capturing `args` from the Eval Stack\n\nDid Enter (`try`):\n[-] associate destroyable `try`\n[!] push Destroyable Stack <- `try`\n[!] push Updating List <- `try`\n[!] push Updating Stack <- `try.children`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 403,
+      "line": 413,
       "description": "## Opcodes\n\n- Append: `Iterate`\n- Update: `ListBlock`\n\n## State changes\n\nCreate a new ref for the iterator item (`value`).\nCreate a new ref for the iterator key (`key`).\n\n[ ] create `valueRef` (`Reference`) from `value`\n[ ] create `keyRef` (`Reference`) from `key`\n[!] push Eval Stack <- `valueRef`\n[!] push Eval Stack <- `keyRef`\n[!] push Element Stack <- `UpdatableBlock` as `block`\n[ ] capture `closure` with *2* items from the Eval Stack\n[ ] create `iteration` (`ListItemOpcode`) with `closure`, `block`, `key`, `keyRef` and `valueRef`\n\nDid Enter (`iteration`):\n[-] associate destroyable `iteration`\n[!] push Destroyable Stack <- `iteration`\n[!] push Updating List <- `iteration`\n[!] push Updating Stack <- `iteration.children`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 450,
+      "line": 460,
       "description": "## Opcodes\n\n- Append: `EnterList`\n\n## State changes\n\n[ ] capture `closure` with *0* items from the Eval Stack, and `$pc` from `offset`\n[ ] create `updating` (empty `Array`)\n[!] push Element Stack <- `list` (`BlockList`) with `updating`\n[ ] create `list` (`ListBlockOpcode`) with `closure`, `list`, `updating` and `iterableRef`\n[!] push List Stack <- `list`\n\nDid Enter (`list`):\n[-] associate destroyable `list`\n[!] push Destroyable Stack <- `list`\n[!] push Updating List <- `list`\n[!] push Updating Stack <- `list.children`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 483,
+      "line": 493,
       "description": "## Opcodes\n\n- Append: `Enter`\n- Append: `Iterate`\n- Append: `EnterList`\n- Update: `ListBlock`\n\n## State changes\n\n[-] associate destroyable `opcode`\n[!] push Destroyable Stack <- `opcode`\n[!] push Updating List <- `opcode`\n[!] push Updating Stack <- `opcode.children`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 506,
+      "line": 516,
       "description": "## Opcodes\n\n- Append: `Exit`\n- Append: `ExitList`\n\n## State changes\n\n[!] pop Destroyable Stack\n[!] pop Element Stack\n[!] pop Updating Stack",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 524,
+      "line": 534,
       "description": "## Opcodes\n\n- Append: `ExitList`\n\n## State changes\n\nPop List:\n[!] pop Destroyable Stack\n[!] pop Element Stack\n[!] pop Updating Stack\n\n[!] pop List Stack",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 543,
+      "line": 553,
       "description": "## Opcodes\n\n- Append: `RootScope`\n- Append: `VirtualRootScope`\n\n## State changes\n\n[!] push Scope Stack",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 559,
+      "line": 569,
       "description": "## Opcodes\n\n- Append: `ChildScope`\n\n## State changes\n\n[!] push Scope Stack <- `child` of current Scope",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 572,
+      "line": 582,
       "description": "## Opcodes\n\n- Append: `Yield`\n\n## State changes\n\n[!] push Scope Stack <- `scope`",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 585,
+      "line": 595,
       "description": "## Opcodes\n\n- Append: `PopScope`\n\n## State changes\n\n[!] pop Scope Stack",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 598,
+      "line": 608,
       "description": "## Opcodes\n\n- Append: `PushDynamicScope`\n\n## State changes:\n\n[!] push Dynamic Scope Stack <- child of current Dynamic Scope",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 613,
+      "line": 623,
       "description": "## Opcodes\n\n- Append: `BindDynamicScope`\n\n## State changes:\n\n[!] pop Dynamic Scope Stack `names.length` times",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 630,
+      "line": 640,
       "description": "## State changes\n\n- [!] push Updating Stack",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -22078,7 +22355,7 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 641,
+      "line": 651,
       "description": "## State changes\n\n[!] pop Updating Stack",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -22086,7 +22363,7 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 652,
+      "line": 662,
       "description": "## State changes\n\n[!] push Updating List",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -22094,7 +22371,7 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 667,
+      "line": 677,
       "description": "## State changes\n\n[-] associate destroyable `child`",
       "utility": "",
       "class": "@glimmer/tracking",
@@ -22102,76 +22379,76 @@
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 686,
+      "line": 696,
       "description": "Get Tree Builder",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 693,
+      "line": 703,
       "description": "Get current Scope",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 700,
+      "line": 710,
       "description": "Get current Dynamic Scope",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 811,
+      "line": 821,
       "description": "The address of the compiled template. This is converted into a\npc when the VM is created.",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 817,
+      "line": 827,
       "description": "Optionally, specify the root scope for the VM. If not specified,\nthe VM will use a root scope with no `this` reference and no\nsymbols.",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 823,
+      "line": 833,
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 832,
+      "line": 842,
       "description": "The program counter that subsequent evaluations should start from.",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 837,
+      "line": 847,
       "description": "The current value of the VM's scope (which changes whenever a component is invoked or a block\nwith block params is entered).",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 843,
+      "line": 853,
       "description": "The current value of the VM's dynamic scope",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 848,
+      "line": 858,
       "description": "A number of stack elements captured during the initial evaluation, and which should be restored\nto the stack when the block is re-evaluated.",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
-      "line": 855,
+      "line": 865,
       "description": "A closure captures the state of the VM for a particular block of code that is necessary to\nre-invoke the block in the future.\n\nIn practice, this allows us to clear the previous render and \"replay\" the block's execution,\nrendering content in the same position as the first render.",
       "class": "@glimmer/tracking",
       "module": "@ember/helper"
@@ -24096,6 +24373,13 @@
       "class": "TestAdapter",
       "module": "@glimmer/tracking"
     },
+    {
+      "file": "packages/@glimmer/util/lib/destroyable-key.ts",
+      "line": 1,
+      "description": "Classes Glimmer constructs itself declare this slot, so that\n`@glimmer/destroyable` can hold their meta directly rather than in its\n`WeakMap`. It lives here so packages below `@glimmer/destroyable` can declare\nthe slot without depending on it.\n\nNever write this onto an object Glimmer did not construct. Destroyables are\npublic through `@ember/destroyable` and can be any object a user hands in.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
     {
       "file": "packages/@glimmer/util/lib/intern.ts",
       "line": 1,
@@ -24582,15 +24866,15 @@
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:605"
+      "line": " packages/@ember/object/mixin.ts:616"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:628"
+      "line": " packages/@ember/object/mixin.ts:639"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:649"
+      "line": " packages/@ember/object/mixin.ts:660"
     },
     {
       "message": "replacing incorrect tag: returns with return",
@@ -24626,7 +24910,7 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/routing/route.ts:2095"
+      "line": " packages/@ember/routing/route.ts:2151"
     },
     {
       "message": "unknown tag: internal",
@@ -24638,39 +24922,51 @@
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:10"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:10"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:62"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:62"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:74"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:74"
+      "line": " packages/@glimmer/component/dist/dev/index.js:25"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/index.js:32"
+      "line": " packages/@glimmer/component/dist/dev/index.js:42"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/index.js:49"
+      "line": " packages/@glimmer/component/dist/dev/index.js:59"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/dist/index.js:66"
+      "line": " packages/@glimmer/component/dist/prod/index.js:13"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:36"
+      "line": " packages/@glimmer/component/dist/prod/index.js:30"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:79"
+      "line": " packages/@glimmer/component/dist/prod/index.js:47"
     },
     {
       "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:97"
+      "line": " packages/@glimmer/component/src/-private/component.ts:29"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/src/-private/component.ts:72"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/src/-private/component.ts:90"
     },
     {
       "message": "unknown tag: import",
@@ -24694,27 +24990,27 @@
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:171"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:181"
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:184"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:194"
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:640"
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:651"
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:662"
     },
     {
       "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:677"
     },
     {
       "message": "unknown tag: debug",
@@ -25106,15 +25402,15 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:21"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:22"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts:21"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts:22"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts:32"
+      "line": " packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts:33"
     },
     {
       "message": "Missing item type\nConverts a camelized string into all lower case separated by underscores.\n\n```javascript\ndecamelize('innerHTML');          // 'inner_html'\ndecamelize('action_name');        // 'action_name'\ndecamelize('css-class-name');     // 'css-class-name'\ndecamelize('my favorite items');  // 'my favorite items'\n```",
@@ -25132,6 +25428,10 @@
       "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\nKey for the internal Mixin constructor.\n\nEmber's own internals are built on mixins, so they need a way to construct\none without triggering the mixin deprecation that `Mixin.create` emits. This\nis deliberately a Symbol so that it does not show up as a discoverable\nproperty name and cannot be reached by name from application code.",
+      "line": " packages/@ember/-internals/utils/lib/internal-mixin-create.ts:1"
+    },
     {
       "message": "Missing item type",
       "line": " packages/@ember/application/index.ts:33"
@@ -25178,51 +25478,47 @@
     },
     {
       "message": "Missing item type\nThe final definition of NativeArray removes all native methods. This is the list of removed methods\nwhen run in Chrome 106.",
-      "line": " packages/@ember/array/index.ts:1855"
+      "line": " packages/@ember/array/index.ts:1856"
     },
     {
       "message": "Missing item type\nThese additional items must be redefined since `Omit` causes methods that return `this` to return the\ntype at the time of the Omit.",
-      "line": " packages/@ember/array/index.ts:1872"
+      "line": " packages/@ember/array/index.ts:1873"
     },
     {
       "message": "Missing item type\nRemove all elements from the array. This is useful if you\nwant to reuse an existing array without having to recreate it.",
-      "line": " packages/@ember/array/index.ts:1896"
+      "line": " packages/@ember/array/index.ts:1897"
     },
     {
       "message": "Missing item type\nThis will use the primitive `replace()` method to insert an object at the\nspecified index.",
-      "line": " packages/@ember/array/index.ts:1901"
+      "line": " packages/@ember/array/index.ts:1902"
     },
     {
       "message": "Missing item type\nRemove an object at the specified index using the `replace()` primitive\nmethod. You can pass either a single index, or a start and a length.",
-      "line": " packages/@ember/array/index.ts:1906"
+      "line": " packages/@ember/array/index.ts:1907"
     },
     {
       "message": "Missing item type\nAdd the objects in the passed numerable to the end of the array. Defers\nnotifying observers of the change until all objects are added.",
-      "line": " packages/@ember/array/index.ts:1911"
+      "line": " packages/@ember/array/index.ts:1912"
     },
     {
       "message": "Missing item type\nAdds the named objects to the beginning of the array. Defers notifying\nobservers until all objects have been added.",
-      "line": " packages/@ember/array/index.ts:1916"
+      "line": " packages/@ember/array/index.ts:1917"
     },
     {
       "message": "Missing item type\nReverse objects in the array. Works just like `reverse()` but it is\nKVO-compliant.",
-      "line": " packages/@ember/array/index.ts:1921"
+      "line": " packages/@ember/array/index.ts:1922"
     },
     {
       "message": "Missing item type\nReplace all the receiver's content with content of the argument.\nIf argument is an empty array receiver will be cleared.",
-      "line": " packages/@ember/array/index.ts:1926"
+      "line": " packages/@ember/array/index.ts:1927"
     },
     {
       "message": "Missing item type\nRemoves each object in the passed array from the receiver.",
-      "line": " packages/@ember/array/index.ts:1948"
+      "line": " packages/@ember/array/index.ts:1949"
     },
     {
       "message": "Missing item type\nAdds each object in the passed enumerable to the receiver.",
-      "line": " packages/@ember/array/index.ts:1969"
-    },
-    {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:178"
+      "line": " packages/@ember/array/index.ts:1970"
     },
     {
       "message": "Missing item type",
@@ -25230,7 +25526,7 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:183"
+      "line": " packages/@ember/array/proxy.ts:182"
     },
     {
       "message": "Missing item type",
@@ -25238,7 +25534,7 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:188"
+      "line": " packages/@ember/array/proxy.ts:187"
     },
     {
       "message": "Missing item type",
@@ -25260,6 +25556,10 @@
       "message": "Missing item type",
       "line": " packages/@ember/array/proxy.ts:198"
     },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:200"
+    },
     {
       "message": "Missing item type\nTemplate-only components have no backing class instance, so `this` in their\ntemplates is null. This means that you can only reference passed in arguments\n(e.g. `{{@arg}}`).",
       "line": " packages/@ember/component/template-only.ts:34"
@@ -25270,11 +25570,11 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/controller/index.ts:34"
+      "line": " packages/@ember/controller/index.ts:35"
     },
     {
       "message": "Missing item type\nA type registry for Ember `Controller`s. Meant to be declaration-merged so string\nlookups resolve to the correct type.\n\nBlueprints should include such a declaration merge for TypeScript:\n\n```ts\nimport Controller from '@ember/controller';\n\nexport default class ExampleController extends Controller {\n// ...\n}\n\ndeclare module '@ember/controller' {\n  export interface Registry {\n    example: ExampleController;\n  }\n}\n```\n\nThen `@inject` can check that the service is registered correctly, and APIs\nlike `owner.lookup('controller:example')` can return `ExampleController`.",
-      "line": " packages/@ember/controller/index.ts:373"
+      "line": " packages/@ember/controller/index.ts:374"
     },
     {
       "message": "Missing item type",
@@ -25310,55 +25610,59 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:233"
+      "line": " packages/@ember/object/core.ts:234"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/object/core.ts:238"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:237"
+      "line": " packages/@ember/object/mixin.ts:539"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:537"
+      "line": " packages/@ember/object/mixin.ts:542"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:540"
+      "line": " packages/@ember/object/mixin.ts:545"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:543"
+      "line": " packages/@ember/object/mixin.ts:548"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:546"
+      "line": " packages/@ember/object/mixin.ts:551"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:549"
+      "line": " packages/@ember/object/mixin.ts:556"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:554"
+      "line": " packages/@ember/object/mixin.ts:589"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:587"
+      "line": " packages/@ember/object/mixin.ts:598"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:644"
+      "line": " packages/@ember/object/mixin.ts:655"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:670"
+      "line": " packages/@ember/object/mixin.ts:681"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:677"
+      "line": " packages/@ember/object/mixin.ts:688"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:684"
+      "line": " packages/@ember/object/mixin.ts:695"
     },
     {
       "message": "Missing item type",
@@ -25382,35 +25686,35 @@
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:266"
+      "line": " packages/@ember/routing/route.ts:281"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:268"
+      "line": " packages/@ember/routing/route.ts:283"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:271"
+      "line": " packages/@ember/routing/route.ts:286"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:273"
+      "line": " packages/@ember/routing/route.ts:288"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:1546"
+      "line": " packages/@ember/routing/route.ts:1602"
     },
     {
       "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/routing/router.ts:1630"
+      "line": " packages/@ember/routing/router.ts:1680"
     },
     {
       "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/routing/router.ts:1651"
+      "line": " packages/@ember/routing/router.ts:1701"
     },
     {
       "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/routing/router.ts:1673"
+      "line": " packages/@ember/routing/router.ts:1723"
     },
     {
       "message": "Missing item type",
@@ -25510,107 +25814,143 @@
     },
     {
       "message": "Missing item type\nThis provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:10"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:10"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:30"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:30"
     },
     {
       "message": "Missing item type\nGiven any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:62"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:62"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:74"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:74"
     },
     {
       "message": "Missing item type\nThe `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:79"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:79"
     },
     {
       "message": "Missing item type\nConstructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:203"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:205"
     },
     {
       "message": "Missing item type\nNamed arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:212"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:214"
     },
     {
       "message": "Missing item type\nCalled before the component has been removed from the DOM.",
-      "line": " packages/@glimmer/component/dist/-private/component.d.ts:239"
+      "line": " packages/@glimmer/component/dist/component/src/-private/component.d.ts:241"
     },
     {
       "message": "Missing item type\nThis component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
-      "line": " packages/@glimmer/component/dist/-private/ember-component-manager.d.ts:4"
+      "line": " packages/@glimmer/component/dist/component/src/-private/ember-component-manager.d.ts:4"
     },
     {
       "message": "Missing item type\nThis provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
-      "line": " packages/@glimmer/component/dist/index.js:32"
+      "line": " packages/@glimmer/component/dist/dev/index.js:25"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/dist/index.js:47"
+      "line": " packages/@glimmer/component/dist/dev/index.js:40"
     },
     {
       "message": "Missing item type\nGiven any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
-      "line": " packages/@glimmer/component/dist/index.js:49"
+      "line": " packages/@glimmer/component/dist/dev/index.js:42"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/dist/index.js:66"
+      "line": " packages/@glimmer/component/dist/dev/index.js:59"
     },
     {
       "message": "Missing item type\nThe `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
-      "line": " packages/@glimmer/component/dist/index.js:71"
+      "line": " packages/@glimmer/component/dist/dev/index.js:64"
     },
     {
       "message": "Missing item type\nConstructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
-      "line": " packages/@glimmer/component/dist/index.js:195"
+      "line": " packages/@glimmer/component/dist/dev/index.js:191"
     },
     {
       "message": "Missing item type\nNamed arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
-      "line": " packages/@glimmer/component/dist/index.js:212"
+      "line": " packages/@glimmer/component/dist/dev/index.js:206"
     },
     {
       "message": "Missing item type\nCalled before the component has been removed from the DOM.",
-      "line": " packages/@glimmer/component/dist/index.js:244"
+      "line": " packages/@glimmer/component/dist/dev/index.js:238"
     },
     {
       "message": "Missing item type\nThis component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
-      "line": " packages/@glimmer/component/dist/index.js:279"
+      "line": " packages/@glimmer/component/dist/dev/index.js:273"
     },
     {
       "message": "Missing item type\nThis provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:36"
+      "line": " packages/@glimmer/component/dist/prod/index.js:13"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/src/-private/component.ts:56"
+      "line": " packages/@glimmer/component/dist/prod/index.js:28"
     },
     {
       "message": "Missing item type\nGiven any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:79"
+      "line": " packages/@glimmer/component/dist/prod/index.js:30"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/component/src/-private/component.ts:97"
+      "line": " packages/@glimmer/component/dist/prod/index.js:47"
     },
     {
       "message": "Missing item type\nThe `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:103"
+      "line": " packages/@glimmer/component/dist/prod/index.js:52"
     },
     {
       "message": "Missing item type\nConstructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:227"
+      "line": " packages/@glimmer/component/dist/prod/index.js:179"
     },
     {
       "message": "Missing item type\nNamed arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
-      "line": " packages/@glimmer/component/src/-private/component.ts:248"
+      "line": " packages/@glimmer/component/dist/prod/index.js:191"
     },
     {
       "message": "Missing item type\nCalled before the component has been removed from the DOM.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:282"
+      "line": " packages/@glimmer/component/dist/prod/index.js:223"
+    },
+    {
+      "message": "Missing item type\nThis component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
+      "line": " packages/@glimmer/component/dist/prod/index.js:255"
+    },
+    {
+      "message": "Missing item type\nThis provides us a way to have a \"fallback\" which represents an empty object,\nwithout the downsides of how TS treats `{}`. Specifically: this will\ncorrectly leverage \"excess property checking\" so that, given a component\nwhich has no named args, if someone invokes it with any named args, they will\nget a type error.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:29"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/component/src/-private/component.ts:49"
+    },
+    {
+      "message": "Missing item type\nGiven any allowed shorthand form of a signature, desugars it to its full\nexpanded type.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:72"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/component/src/-private/component.ts:90"
+    },
+    {
+      "message": "Missing item type\nThe `Component` class defines an encapsulated UI element that is rendered to\nthe DOM. A component is made up of a template and, optionally, this component\nobject.\n\n## Defining a Component\n\nTo define a component, subclass `Component` and add your own properties,\nmethods and lifecycle hooks:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n}\n```\n\n## Lifecycle Hooks\n\nLifecycle hooks allow you to respond to changes to a component, such as when\nit gets created, rendered, updated or destroyed. To add a lifecycle hook to a\ncomponent, implement the hook as a method on your component subclass.\n\nFor example, to be notified when Glimmer has rendered your component so you\ncan attach a legacy jQuery plugin, implement the `didInsertElement()` method:\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  didInsertElement() {\n    $(this.element).pickadate();\n  }\n}\n```\n\n## Data for Templates\n\n`Component`s have two different kinds of data, or state, that can be\ndisplayed in templates:\n\n1. Arguments\n2. Properties\n\nArguments are data that is passed in to a component from its parent\ncomponent. For example, if I have a `UserGreeting` component, I can pass it\na name and greeting to use:\n\n```hbs\n<UserGreeting @name=\"Ricardo\" @greeting=\"Olá\" />\n```\n\nInside my `UserGreeting` template, I can access the `@name` and `@greeting`\narguments that I've been given:\n\n```hbs\n{{@greeting}}, {{@name}}!\n```\n\nArguments are also available inside my component:\n\n```ts\nconsole.log(this.args.greeting); // prints \"Olá\"\n```\n\nProperties, on the other hand, are internal to the component and declared in\nthe class. You can use properties to store data that you want to show in the\ntemplate, or pass to another component as an argument.\n\n```ts\nimport Component from '@glimmer/component';\n\nexport default class extends Component {\n  user = {\n    name: 'Robbie'\n  }\n}\n```\n\nIn the above example, we've defined a component with a `user` property that\ncontains an object with its own `name` property.\n\nWe can render that property in our template:\n\n```hbs\nHello, {{user.name}}!\n```\n\nWe can also take that property and pass it as an argument to the\n`UserGreeting` component we defined above:\n\n```hbs\n<UserGreeting @greeting=\"Hello\" @name={{user.name}} />\n```\n\n## Arguments vs. Properties\n\nRemember, arguments are data that was given to your component by its parent\ncomponent, and properties are data your component has defined for itself.\n\nYou can tell the difference between arguments and properties in templates\nbecause arguments always start with an `@` sign (think \"A is for arguments\"):\n\n```hbs\n{{@firstName}}\n```\n\nWe know that `@firstName` came from the parent component, not the current\ncomponent, because it starts with `@` and is therefore an argument.\n\nOn the other hand, if we see:\n\n```hbs\n{{name}}\n```\n\nWe know that `name` is a property on the component. If we want to know where\nthe data is coming from, we can go look at our component class to find out.\n\nInside the component itself, arguments always show up inside the component's\n`args` property. For example, if `{{@firstName}}` is `Tom` in the template,\ninside the component `this.args.firstName` would also be `Tom`.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:96"
+    },
+    {
+      "message": "Missing item type\nConstructs a new component and assigns itself the passed properties. You\nshould not construct new components yourself. Instead, Glimmer will\ninstantiate new components automatically as it renders.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:223"
+    },
+    {
+      "message": "Missing item type\nNamed arguments passed to the component from its parent component.\nThey can be accessed in JavaScript via `this.args.argumentName` and in the template via `@argumentName`.\n\nSay you have the following component, which will have two `args`, `firstName` and `lastName`:\n\n```hbs\n<my-component @firstName=\"Arthur\" @lastName=\"Dent\" />\n```\n\nIf you needed to calculate `fullName` by combining both of them, you would do:\n\n```ts\ndidInsertElement() {\n  console.log(`Hi, my full name is ${this.args.firstName} ${this.args.lastName}`);\n}\n```\n\nWhile in the template you could do:\n\n```hbs\n<p>Welcome, {{@firstName}} {{@lastName}}!</p>\n```",
+      "line": " packages/@glimmer/component/src/-private/component.ts:241"
+    },
+    {
+      "message": "Missing item type\nCalled before the component has been removed from the DOM.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:275"
     },
     {
       "message": "Missing item type\nThis component manager runs in Ember.js environments and extends the base component manager to:\n\n1. Properly destroy the component's associated `meta` data structure\n2. Schedule destruction using Ember's runloop",
@@ -25792,6 +26132,10 @@
       "message": "Missing item type\nThis function takes an optional function and returns its result. It's\nexpected to be used with optional debug methods, in the context of an\nexisting `LOCAL_DEBUG` check.",
       "line": " packages/@glimmer/debug-util/lib/platform-utils.ts:13"
     },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/destroyable/index.ts:241"
+    },
     {
       "message": "Missing item type\nThis package contains global context functions for Glimmer. These functions\nare set by the embedding environment and must be set before initial render.\n\nThese functions should meet the following criteria:\n\n- Must be provided by the embedder, due to having framework specific\n  behaviors (e.g. interop with classic Ember behaviors that should not be\n  upstreamed) or to being out of scope for the VM (e.g. scheduling a\n  revalidation)\n- Never differ between render roots\n- Never change over time",
       "line": " packages/@glimmer/global-context/index.ts:4"
@@ -26258,135 +26602,135 @@
     },
     {
       "message": "Missing item type\nFetch a value from a syscall register onto the stack.\n\n## Opcodes\n\n- Append: `Fetch`\n\n## State changes\n\n[!] push Eval Stack <- $register",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:136"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:146"
     },
     {
       "message": "Missing item type\nLoad a value from the stack into a syscall register.\n\n## Opcodes\n\n- Append: `Load`\n\n## State changes\n\n[!] pop Eval Stack -> `value`\n[$] $register <- `value`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:153"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:163"
     },
     {
       "message": "Missing item type\nLoad a value into a syscall register.\n\n## State changes\n\n[$] $register <- `value`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:171"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:181"
     },
     {
       "message": "Missing item type\nFetch a value from a register (machine or syscall).\n\n## State changes\n\n[ ] get $register",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:184"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:194"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `BeginComponentTransaction`\n\n## State Changes\n\n[ ] create `guard` (`JumpIfNotModifiedOpcode`)\n[ ] create `tracker` (`BeginTrackFrameOpcode`)\n[!] push Updating Stack <- `guard`\n[!] push Updating Stack <- `tracker`\n[!] push Cache Stack <- `guard`\n[!] push Tracking Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:327"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:337"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `CommitComponentTransaction`\n\n## State Changes\n\nCreate a new `EndTrackFrameOpcode` (`end`)\n\n[!] pop CacheStack -> `guard`\n[!] pop Tracking Stack -> `tag`\n[ ] create `end` (`EndTrackFrameOpcode`) with `guard`\n[-] consume `tag`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:352"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:362"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `Enter`\n\n## State changes\n\n[!] push Element Stack as `block`\n[ ] create `try` (`TryOpcode`) with `block`, capturing `args` from the Eval Stack\n\nDid Enter (`try`):\n[-] associate destroyable `try`\n[!] push Destroyable Stack <- `try`\n[!] push Updating List <- `try`\n[!] push Updating Stack <- `try.children`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:376"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:386"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `Iterate`\n- Update: `ListBlock`\n\n## State changes\n\nCreate a new ref for the iterator item (`value`).\nCreate a new ref for the iterator key (`key`).\n\n[ ] create `valueRef` (`Reference`) from `value`\n[ ] create `keyRef` (`Reference`) from `key`\n[!] push Eval Stack <- `valueRef`\n[!] push Eval Stack <- `keyRef`\n[!] push Element Stack <- `UpdatableBlock` as `block`\n[ ] capture `closure` with *2* items from the Eval Stack\n[ ] create `iteration` (`ListItemOpcode`) with `closure`, `block`, `key`, `keyRef` and `valueRef`\n\nDid Enter (`iteration`):\n[-] associate destroyable `iteration`\n[!] push Destroyable Stack <- `iteration`\n[!] push Updating List <- `iteration`\n[!] push Updating Stack <- `iteration.children`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:403"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:413"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `EnterList`\n\n## State changes\n\n[ ] capture `closure` with *0* items from the Eval Stack, and `$pc` from `offset`\n[ ] create `updating` (empty `Array`)\n[!] push Element Stack <- `list` (`BlockList`) with `updating`\n[ ] create `list` (`ListBlockOpcode`) with `closure`, `list`, `updating` and `iterableRef`\n[!] push List Stack <- `list`\n\nDid Enter (`list`):\n[-] associate destroyable `list`\n[!] push Destroyable Stack <- `list`\n[!] push Updating List <- `list`\n[!] push Updating Stack <- `list.children`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:450"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:460"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `Enter`\n- Append: `Iterate`\n- Append: `EnterList`\n- Update: `ListBlock`\n\n## State changes\n\n[-] associate destroyable `opcode`\n[!] push Destroyable Stack <- `opcode`\n[!] push Updating List <- `opcode`\n[!] push Updating Stack <- `opcode.children`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:483"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:493"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `Exit`\n- Append: `ExitList`\n\n## State changes\n\n[!] pop Destroyable Stack\n[!] pop Element Stack\n[!] pop Updating Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:506"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:516"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `ExitList`\n\n## State changes\n\nPop List:\n[!] pop Destroyable Stack\n[!] pop Element Stack\n[!] pop Updating Stack\n\n[!] pop List Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:524"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:534"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `RootScope`\n- Append: `VirtualRootScope`\n\n## State changes\n\n[!] push Scope Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:543"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:553"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `ChildScope`\n\n## State changes\n\n[!] push Scope Stack <- `child` of current Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:559"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:569"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `Yield`\n\n## State changes\n\n[!] push Scope Stack <- `scope`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:572"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:582"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `PopScope`\n\n## State changes\n\n[!] pop Scope Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:585"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:595"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `PushDynamicScope`\n\n## State changes:\n\n[!] push Dynamic Scope Stack <- child of current Dynamic Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:598"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:608"
     },
     {
       "message": "Missing item type\n## Opcodes\n\n- Append: `BindDynamicScope`\n\n## State changes:\n\n[!] pop Dynamic Scope Stack `names.length` times",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:613"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:623"
     },
     {
       "message": "Missing item type\n## State changes\n\n- [!] push Updating Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:640"
     },
     {
       "message": "Missing item type\n## State changes\n\n[!] pop Updating Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:651"
     },
     {
       "message": "Missing item type\n## State changes\n\n[!] push Updating List",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:662"
     },
     {
       "message": "Missing item type\n## State changes\n\n[-] associate destroyable `child`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:677"
     },
     {
       "message": "Missing item type\nGet Tree Builder",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:686"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:696"
     },
     {
       "message": "Missing item type\nGet current Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:693"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:703"
     },
     {
       "message": "Missing item type\nGet current Dynamic Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:700"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:710"
     },
     {
       "message": "Missing item type\nThe address of the compiled template. This is converted into a\npc when the VM is created.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:811"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:821"
     },
     {
       "message": "Missing item type\nOptionally, specify the root scope for the VM. If not specified,\nthe VM will use a root scope with no `this` reference and no\nsymbols.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:817"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:827"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:823"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:833"
     },
     {
       "message": "Missing item type\nThe program counter that subsequent evaluations should start from.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:832"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:842"
     },
     {
       "message": "Missing item type\nThe current value of the VM's scope (which changes whenever a component is invoked or a block\nwith block params is entered).",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:837"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:847"
     },
     {
       "message": "Missing item type\nThe current value of the VM's dynamic scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:843"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:853"
     },
     {
       "message": "Missing item type\nA number of stack elements captured during the initial evaluation, and which should be restored\nto the stack when the block is re-evaluated.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:848"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:858"
     },
     {
       "message": "Missing item type\nA closure captures the state of the VM for a particular block of code that is necessary to\nre-invoke the block in the future.\n\nIn practice, this allows us to clear the previous render and \"replay\" the block's execution,\nrendering content in the same position as the first render.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:855"
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:865"
     },
     {
       "message": "Missing item type",
@@ -27444,6 +27788,10 @@
       "message": "Missing item type\nZip two tuples with the same type and number of elements.",
       "line": " packages/@glimmer/util/lib/array-utils.ts:36"
     },
+    {
+      "message": "Missing item type\nClasses Glimmer constructs itself declare this slot, so that\n`@glimmer/destroyable` can hold their meta directly rather than in its\n`WeakMap`. It lives here so packages below `@glimmer/destroyable` can declare\nthe slot without depending on it.\n\nNever write this onto an object Glimmer did not construct. Destroyables are\npublic through `@ember/destroyable` and can be any object a user hands in.",
+      "line": " packages/@glimmer/util/lib/destroyable-key.ts:1"
+    },
     {
       "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/@glimmer/util/lib/intern.ts:1"