From d9d99cd5a4ca956c97de823f740e64a6bd027a32 Mon Sep 17 00:00:00 2001
From: Katie Gengler <katie@kmg.io>
Date: Sat, 8 Aug 2026 14:36:48 -0400
Subject: [PATCH] Update 7.1 docs

---
 .../classes/ember-7.1.0-@ember/component.json |   21 +-
 .../classes/ember-7.1.0-@ember/helper.json    |  327 +-
 .../ember-7.1.0-@ember/object/compat.json     |    2 +-
 .../classes/ember-7.1.0-@ember/routing.json   |    8 +-
 .../ember-7.1.0-@glimmer/tracking.json        |  112 -
 ...mber-7.1.0-Ember.Templates.components.json |   81 -
 .../ember-7.1.0-Ember.Templates.helpers.json  |  385 +-
 .../7.1.0/classes/ember-7.1.0-External.json   |   60 +
 .../7.1.0/classes/ember-7.1.0-Helper.json     |    2 +-
 .../7.1.0/classes/ember-7.1.0-Keywords.json   |  749 ++
 .../classes/ember-7.1.0-RouterService.json    |   10 +-
 .../modules/ember-7.1.0-@ember/component.json |   66 +-
 .../modules/ember-7.1.0-@ember/helper.json    | 1580 +++-
 .../modules/ember-7.1.0-@ember/object.json    |    4 +-
 .../modules/ember-7.1.0-@ember/routing.json   |   35 +-
 .../7.1.0/modules/ember-7.1.0-ember.json      |    2 -
 .../7.1.0/project-versions/ember-7.1.0.json   |   16 +-
 rev-index/ember-7.1.0.json                    |    2 +-
 s3-docs/v7.1.0/ember-docs.json                | 7073 ++++++++++-------
 19 files changed, 6698 insertions(+), 3837 deletions(-)
 delete mode 100644 json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.components.json
 create mode 100644 json-docs/ember/7.1.0/classes/ember-7.1.0-External.json
 create mode 100644 json-docs/ember/7.1.0/classes/ember-7.1.0-Keywords.json

diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/component.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/component.json
index ff63faf34..847e2d9d6 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/component.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/component.json
@@ -15,12 +15,17 @@
       "methods": [
         {
           "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-          "line": 55,
-          "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Input>.\n\nSee [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
+          "line": 46,
+          "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <Input @value=\"987\" />\n</template>\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.",
           "itemtype": "method",
           "name": "Input",
-          "see": [
-            "{Ember.Templates.components.Input}"
+          "static": 1,
+          "params": [
+            {
+              "name": "options",
+              "description": "",
+              "type": "Hash"
+            }
           ],
           "access": "public",
           "tagname": "",
@@ -29,13 +34,11 @@
         },
         {
           "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-          "line": 136,
-          "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Textarea>.\n\nSee [Ember.Templates.components.Textarea](/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Textarea).",
+          "line": 10,
+          "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```gjs {data-filename=\"app/components/word-editor.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
           "itemtype": "method",
           "name": "Textarea",
-          "see": [
-            "{Ember.Templates.components.Textarea}"
-          ],
+          "static": 1,
           "access": "public",
           "tagname": "",
           "class": "@ember/component",
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/helper.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/helper.json
index 3357b5713..495b5e5da 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/helper.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/helper.json
@@ -10,91 +10,9 @@
       "extensions": [],
       "plugin_for": [],
       "extension_for": [],
-      "module": "ember",
+      "module": "@ember/helper",
       "namespace": "",
       "methods": [
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/array.ts",
-          "line": 5,
-          "description": "Use the `{{array}}` helper to create an array to pass as an option to your\ncomponents.\n\n```handlebars\n<MyComponent @people={{array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson}}\n/>\n```\n or\n```handlebars\n{{yield people=(array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson)\n}}\n```\n\nWould result in an object such as:\n\n```js\n['Tom Dale', 'Yehuda Katz', this.get('myOtherPerson')]\n```\n\nWhere the 3rd item in the array is bound to updates of the `myOtherPerson` property.\n \nThe `array` helper is built-in keyword and does not need to be imported as of v7.1.0.",
-          "itemtype": "method",
-          "name": "array",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Array"
-            }
-          ],
-          "return": {
-            "description": "Array",
-            "type": "Array"
-          },
-          "since": "3.8.0",
-          "access": "public",
-          "tagname": "",
-          "class": "@ember/helper",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/concat.ts",
-          "line": 5,
-          "description": "Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\nimport { concat } from '@ember/helper';\n  \n<template>\n  {{yield (concat firstName \" \" lastName)}}\n\n  {{! would yield name=\"<first name value> <last name value>\" to the component}}\n</template>\n```\n\nFor invocation of components, you don't need concat at all.\n\n```handlebars\n<SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n```",
-          "access": "public",
-          "tagname": "",
-          "itemtype": "method",
-          "name": "concat",
-          "since": "1.13.0",
-          "class": "@ember/helper",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/fn.ts",
-          "line": 5,
-          "description": "The `fn` helper allows you to ensure a function that you are passing off\nto another component, helper, or modifier has access to arguments that are\navailable in the template.\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```app/components/items-listing.gjs\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\n  receive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\n  will receive the `item` from the loop as its first argument and the\n  string `'foo'` as its second argument.\n\nIn the example above, we used `@action` to ensure that `handleSelected` is\nproperly bound to the `items-list`, but let's explore what happens if we\nleft out `@action`:\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\n\nexport default class ItemsList extends Component {\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when `handleSelected` is invoked inside the `display-item`\ncomponent, it will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `fn`!\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n \n`fn` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "fn",
-          "access": "public",
-          "tagname": "",
-          "since": "3.11.0",
-          "class": "@ember/helper",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/get.ts",
-          "line": 5,
-          "description": "Dynamically look up a property on an object or an element in an array.\nThe second argument to `{{get}}` should have a string or number value,\nalthough it can be bound.\n\nFor example, these two usages are equivalent:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n  \n  <template>\n    {{this.developer.name}}\n    {{get this.developer \"name\"}}\n  </template>\n}\n```\n  \nIf there were several facts about a person, the `{{get}}` helper can dynamically\npick one:\n\n```app/templates/application.gjs\nimport DeveloperDetail from '../components/developer-detail';\n\n<template>\n  <DeveloperDetail @factName=\"language\" />\n</template\n```\n\n```handlebars\n{{get this.developer @factName}}\n```\n\nFor a more complex example, this template would allow the user to switch\nbetween showing the user's name and preferred coding language with a click:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n\n  @tracked currentFact = 'name'\n\n  @action\n  showFact(fact) {\n    this.currentFact = fact;\n  }\n  \n  <template>\n    {{get this.developer this.currentFact}}\n\n    <button {{on 'click' (fn this.showFact \"name\")}}>Show name</button>\n    <button {{on 'click' (fn this.showFact \"language\")}}>Show language</button>\n  </template>\n}\n```\n\nThe `{{get}}` helper can also be used for array element access via index.\nThis would display the value of the first element in the array `this.names`:\n\n```handlebars\n{{get this.names 0}}\n```\n\nArray element access also works with a dynamic second argument:\n\n```handlebars\n{{get this.names @index}}\n```",
-          "access": "public",
-          "tagname": "",
-          "itemtype": "method",
-          "name": "get",
-          "since": "2.1.0",
-          "class": "@ember/helper",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/hash.ts",
-          "line": 5,
-          "description": "Use the `{{hash}}` helper to create a hash to pass as an option to your\ncomponents. This is especially useful for contextual components where you can\njust yield a hash:\n\n```handlebars\n{{yield (hash\n   name='Sarah'\n   title=office\n)}}\n```\n\nWould result in an object such as:\n\n```js\n{ name: 'Sarah', title: this.get('office') }\n```\n\nWhere the `title` is bound to updates of the `office` property.\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\n \nThe `hash` helper is a built-in keyword and does not need to be imported as of v7.1.0.",
-          "itemtype": "method",
-          "name": "hash",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Object"
-            }
-          ],
-          "return": {
-            "description": "Hash",
-            "type": "Object"
-          },
-          "since": "2.3.0",
-          "access": "public",
-          "tagname": "",
-          "class": "@ember/helper",
-          "module": "ember"
-        },
         {
           "file": "packages/@ember/helper/index.ts",
           "line": 26,
@@ -117,6 +35,7 @@
             "description": "The capabilities object instance",
             "type": "Capabilities"
           },
+          "since": "3.23.0",
           "access": "public",
           "tagname": "",
           "class": "@ember/helper",
@@ -124,7 +43,7 @@
         },
         {
           "file": "packages/@ember/helper/index.ts",
-          "line": 80,
+          "line": 81,
           "description": "Sets the helper manager for an object or function.\n\n```js\nsetHelperManager((owner) => new ClassHelperManager(owner), Helper)\n```\n\nWhen a value is used as a helper in a template, the helper manager is looked up\non the object by walking up its prototype chain and finding the first helper\nmanager. This manager then receives the value and can create and manage an\ninstance of a helper from it. This provides a layer of indirection that allows\nusers to design high-level helper APIs, without Ember needing to worry about the\ndetails. High-level APIs can be experimented with and iterated on while the\ncore of Ember helpers remains stable, and new APIs can be introduced gradually\nover time to existing code bases.\n\n`setHelperManager` receives two arguments:\n\n1. A factory function, which receives the `owner` and returns an instance of a\n  helper manager.\n2. A helper definition, which is the object or function to associate the factory function with.\n\nThe first time the object is looked up, the factory function will be called to\ncreate the helper manager. It will be cached, and in subsequent lookups the\ncached helper manager will be used instead.\n\nOnly one helper manager is guaranteed to exist per `owner` and per usage of\n`setHelperManager`, so many helpers will end up using the same instance of the\nhelper manager. As such, you should only store state that is related to the\nmanager itself. If you want to store state specific to a particular helper\ndefinition, you should assign a unique helper manager to that helper. In\ngeneral, most managers should either be stateless, or only have the `owner` they\nwere created with as state.\n\nHelper managers must fulfill the following interface (This example uses\n[TypeScript interfaces](https://www.typescriptlang.org/docs/handbook/interfaces.html)\nfor precision, you do not need to write helper managers using TypeScript):\n\n```ts\ninterface HelperManager<HelperStateBucket> {\n  capabilities: HelperCapabilities;\n\n  createHelper(definition: HelperDefinition, args: TemplateArgs): HelperStateBucket;\n\n  getValue?(bucket: HelperStateBucket): unknown;\n\n  runEffect?(bucket: HelperStateBucket): void;\n\n  getDestroyable?(bucket: HelperStateBucket): object;\n}\n```\n\nThe capabilities property _must_ be provided using the `capabilities()` function\nimported from the same module as `setHelperManager`:\n\n```js\nimport { capabilities } from '@ember/helper';\n\nclass MyHelperManager {\n  capabilities = capabilities('3.21.0', { hasValue: true });\n\n  // ...snip...\n}\n```\n\nBelow is a description of each of the methods on the interface and their\nfunctions.\n\n#### `createHelper`\n\n`createHelper` is a required hook on the HelperManager interface. The hook is\npassed the definition of the helper that is currently being created, and is\nexpected to return a _state bucket_. This state bucket is what represents the\ncurrent state of the helper, and will be passed to the other lifecycle hooks at\nappropriate times. It is not necessarily related to the definition of the\nhelper itself - for instance, you could return an object _containing_ an\ninstance of the helper:\n\n```js\nclass MyManager {\n  createHelper(Definition, args) {\n    return {\n      instance: new Definition(args);\n    };\n  }\n}\n```\n\nThis allows the manager to store metadata that it doesn't want to expose to the\nuser.\n\nThis hook is _not_ autotracked - changes to tracked values used within this hook\nwill _not_ result in a call to any of the other lifecycle hooks. This is because\nit is unclear what should happen if it invalidates, and rather than make a\ndecision at this point, the initial API is aiming to allow as much expressivity\nas possible. This could change in the future with changes to capabilities and\ntheir behaviors.\n\nIf users do want to autotrack some values used during construction, they can\neither create the instance of the helper in `runEffect` or `getValue`, or they\ncan use the `cache` API to autotrack the `createHelper` hook themselves. This\nprovides maximum flexibility and expressiveness to manager authors.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called as discovered during DOM construction\n- called in definition order in the template\n\n#### `getValue`\n\n`getValue` is an optional hook that should return the value of the helper. This\nis the value that is returned from the helper and passed into the template.\n\nThis hook is called when the value is requested from the helper (e.g. when the\ntemplate is rendering and the helper value is needed). The hook is autotracked,\nand will rerun whenever any tracked values used inside of it are updated.\nOtherwise it does not rerun.\n\n> Note: This means that arguments which are not _consumed_ within the hook will\n> not trigger updates.\n\nThis hook is only called for helpers with the `hasValue` capability enabled.\nThis hook has the following timing semantics:\n\n**Always**\n- called the first time the helper value is requested\n- called after autotracked state has changed\n\n**Never**\n- called if the `hasValue` capability is disabled\n\n#### `runEffect`\n\n`runEffect` is an optional hook that should run the effect that the helper is\napplying, setting it up or updating it.\n\nThis hook is scheduled to be called some time after render and prior to paint.\nThere is not a guaranteed, 1-to-1 relationship between a render pass and this\nhook firing. For instance, multiple render passes could occur, and the hook may\nonly trigger once. It may also never trigger if it was dirtied in one render\npass and then destroyed in the next.\n\nThe hook is autotracked, and will rerun whenever any tracked values used inside\nof it are updated. Otherwise it does not rerun.\n\nThe hook is also run during a time period where state mutations are _disabled_\nin Ember. Any tracked state mutation will throw an error during this time,\nincluding changes to tracked properties, changes made using `set`, updates\nto computed properties, etc. This is meant to prevent infinite rerenders and\nother antipatterns.\n\nThis hook is only called for helpers with the `hasScheduledEffect` capability\nenabled. This hook is also not called in SSR currently, though this could be\nadded as a capability in the future. It has the following timing semantics:\n\n**Always**\n- called after the helper was first created, if the helper has not been\n  destroyed since creation\n- called after autotracked state has changed, if the helper has not been\n  destroyed during render\n\n**Never**\n- called if the `hasScheduledEffect` capability is disabled\n- called in SSR\n\n#### `getDestroyable`\n\n`getDestroyable` is an optional hook that users can use to register a\ndestroyable object for the helper. This destroyable will be registered to the\ncontaining block or template parent, and will be destroyed when it is destroyed.\nSee the [Destroyables RFC](https://github.com/emberjs/rfcs/blob/master/text/0580-destroyables.md)\nfor more details.\n\n`getDestroyable` is only called if the `hasDestroyable` capability is enabled.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called immediately after the `createHelper` hook is called\n\n**Never**\n- called if the `hasDestroyable` capability is disabled",
           "itemtype": "method",
           "name": "setHelperManager",
@@ -145,6 +64,7 @@
             "description": "The definition passed into setHelperManager",
             "type": "Object"
           },
+          "since": "3.23.0",
           "access": "public",
           "tagname": "",
           "class": "@ember/helper",
@@ -152,8 +72,8 @@
         },
         {
           "file": "packages/@ember/helper/index.ts",
-          "line": 274,
-          "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```js\n// app/components/data-loader.js\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n```\n```js\n{{this.value}}\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
+          "line": 276,
+          "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```gjs {data-filename=\"app/components/data-loader.js\"}\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n\n<template>\n  {{this.value}}\n</template>\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
           "itemtype": "method",
           "name": "invokeHelper",
           "static": 1,
@@ -177,6 +97,7 @@
           "return": {
             "description": ""
           },
+          "since": "3.23.0",
           "access": "public",
           "tagname": "",
           "class": "@ember/helper",
@@ -184,227 +105,43 @@
         },
         {
           "file": "packages/@ember/helper/index.ts",
-          "line": 463,
-          "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```js\nimport { gt } from '@ember/helper';\n\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `gt` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "gt",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Number"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Number"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 486,
-          "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```js\nimport { gte } from '@ember/helper';\n\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `gte` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "gte",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Number"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Number"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 509,
-          "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```js\nimport { lt } from '@ember/helper';\n\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `lt` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "lt",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Number"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Number"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 532,
-          "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```js\nimport { lte } from '@ember/helper';\n\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `lte` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "lte",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Number"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Number"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 555,
-          "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```js\nimport { element } from '@ember/helper';\n\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.",
-          "itemtype": "method",
-          "name": "element",
-          "params": [
-            {
-              "name": "tagName",
-              "description": "",
-              "type": "String"
-            }
-          ],
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 599,
-          "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```js\nimport { eq } from '@ember/helper';\n\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `eq` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "eq",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Unknown"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Unknown"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 622,
-          "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```js\nimport { neq } from '@ember/helper';\n\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `neq` is available as a keyword and\ndoes not need to be imported.",
-          "itemtype": "method",
-          "name": "neq",
-          "params": [
-            {
-              "name": "left",
-              "description": "",
-              "type": "Unknown"
-            },
-            {
-              "name": "right",
-              "description": "",
-              "type": "Unknown"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
-          "class": "@ember/helper",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/helper/index.ts",
-          "line": 645,
-          "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```js\nimport { and } from '@ember/helper';\n\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `and` is available as a keyword and\ndoes not need to be imported.",
+          "line": 414,
+          "description": "The `{{concat}}` helper Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\n import { concat } from '@ember/helper';\n\n <template>\n   {{yield (concat firstName \" \" lastName)}}\n\n   {{! would yield name=\"<first name value> <last name value>\" to the component}}\n </template>\n ```\n\n or for angle bracket invocation, you actually don't need concat at all:\n\n ```handlebars\n <SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n ```",
           "itemtype": "method",
-          "name": "and",
-          "params": [
-            {
-              "name": "args",
-              "description": "Two or more values to evaluate",
-              "type": "Unknown"
-            }
-          ],
-          "return": {
-            "description": "The first falsy value or the last value",
-            "type": "Unknown"
-          },
+          "name": "concat",
+          "exampleimport": "import { concat } from '@ember/helper';",
+          "access": "public",
+          "tagname": "",
+          "static": 1,
+          "since": "1.13.0",
           "class": "@ember/helper",
           "module": "@ember/helper"
         },
         {
           "file": "packages/@ember/helper/index.ts",
-          "line": 668,
-          "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```js\nimport { or } from '@ember/helper';\n\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
+          "line": 445,
+          "description": "The `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
           "itemtype": "method",
-          "name": "or",
-          "params": [
-            {
-              "name": "args",
-              "description": "Two or more values to evaluate",
-              "type": "Unknown"
-            }
-          ],
-          "return": {
-            "description": "The first truthy value or the last value",
-            "type": "Unknown"
-          },
+          "name": "get",
+          "since": "2.1.0",
+          "exampleimport": "import { get } from '@ember/helper';",
+          "access": "public",
+          "tagname": "",
+          "static": 1,
           "class": "@ember/helper",
           "module": "@ember/helper"
         },
         {
           "file": "packages/@ember/helper/index.ts",
-          "line": 691,
-          "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```js\nimport { not } from '@ember/helper';\n\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
+          "line": 690,
+          "description": "Use the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```gjs\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
           "itemtype": "method",
-          "name": "not",
-          "params": [
-            {
-              "name": "value",
-              "description": "The value to negate",
-              "type": "Unknown"
-            }
-          ],
-          "return": {
-            "description": "",
-            "type": "Boolean"
-          },
+          "name": "uniqueId",
+          "access": "public",
+          "tagname": "",
+          "static": 1,
+          "exampleimport": "import { uniqueId } from '@ember/helper';",
+          "since": "4.4.0",
           "class": "@ember/helper",
           "module": "@ember/helper"
         }
@@ -421,7 +158,7 @@
       },
       "module": {
         "data": {
-          "id": "ember-7.1.0-ember",
+          "id": "ember-7.1.0-@ember/helper",
           "type": "module"
         }
       },
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/object/compat.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/object/compat.json
index aa22aeca9..e2ff80adc 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/object/compat.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/object/compat.json
@@ -16,7 +16,7 @@
         {
           "file": "packages/@ember/object/compat.ts",
           "line": 45,
-          "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nClassic Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport EmberObject, { computed, observer, set } from '@ember/object';\n\nconst Person = EmberObject.extend({\n  firstName: tracked(),\n  lastName: tracked(),\n\n  fullName: dependentKeyCompat(function() {\n    return `${this.firstName} ${this.lastName}`;\n  }),\n});\n\nconst Profile = EmberObject.extend({\n  person: null,\n\n  helloMessage: computed('person.fullName', function() {\n    return `Hello, ${this.person.fullName}!`;\n  }),\n\n  onNameUpdated: observer('person.fullName', function() {\n    console.log('person name updated!');\n  }),\n});\n```\n\n`dependentKeyCompat()` can receive a getter function or an object containing\n`get`/`set` methods when used in classic classes, like computed properties.\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
+          "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
           "access": "public",
           "tagname": "",
           "itemtype": "method",
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/routing.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/routing.json
index 0b5beb802..26603b168 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/routing.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-@ember/routing.json
@@ -15,13 +15,11 @@
       "methods": [
         {
           "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-          "line": 273,
-          "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <LinkTo>.\n\nSee [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
+          "line": 52,
+          "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```gjs\nimport { LinkTo } from '@ember/routing';\n  \n<template>\n  <LinkTo @route='photoGallery'>\n    Great Hamster Photos\n  </LinkTo>\n</template>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
           "itemtype": "method",
           "name": "LinkTo",
-          "see": [
-            "{Ember.Templates.components.LinkTo}"
-          ],
+          "static": 1,
           "access": "public",
           "tagname": "",
           "class": "@ember/routing",
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-@glimmer/tracking.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-@glimmer/tracking.json
index dd41b4887..469cdeb5c 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-@glimmer/tracking.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-@glimmer/tracking.json
@@ -49,118 +49,6 @@
           "class": "@glimmer/tracking",
           "module": "@glimmer/tracking/primitives/cache"
         },
-        {
-          "file": "packages/@glimmer/runtime/lib/component/template-only.ts",
-          "line": 59,
-          "description": "This utility function is used to declare a given component has no backing class. When the rendering engine detects this it\nis able to perform a number of optimizations. Templates that are associated with `templateOnly()` will be rendered _as is_\nwithout adding a wrapping `<div>` (or any of the other element customization behaviors of [@ember/component](/ember/release/classes/Component)).\nSpecifically, this means that the template will be rendered as \"outer HTML\".\n\nIn general, this method will be used by build time tooling and would not be directly written in an application. However,\nat times it may be useful to use directly to leverage the \"outer HTML\" semantics mentioned above. For example, if an addon would like\nto use these semantics for its templates but cannot be certain it will only be consumed by applications that have enabled the\n`template-only-glimmer-components` optional feature.",
-          "example": [
-            "\n\n```js\nimport { templateOnlyComponent } from '@glimmer/runtime';\n\nexport default templateOnlyComponent();\n```"
-          ],
-          "access": "public",
-          "tagname": "",
-          "itemtype": "method",
-          "name": "templateOnly",
-          "params": [
-            {
-              "name": "moduleName",
-              "description": "the module name that the template only component represents, this will be used for debugging purposes",
-              "type": "String"
-            }
-          ],
-          "category": [
-            "EMBER_GLIMMER_SET_COMPONENT_TEMPLATE"
-          ],
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/helpers/array.ts",
-          "line": 8,
-          "description": "Use the `{{array}}` helper to create an array to pass as an option to your\ncomponents.\n\n```handlebars\n<MyComponent @people={{array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson}}\n/>\n```\n or\n```handlebars\n{{yield people=(array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson)\n}}\n```\n\nWould result in an object such as:\n\n```js\n['Tom Dale', 'Yehuda Katz', this.get('myOtherPerson')]\n```\n\nWhere the 3rd item in the array is bound to updates of the `myOtherPerson` property.",
-          "itemtype": "method",
-          "name": "array",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Array"
-            }
-          ],
-          "return": {
-            "description": "Array",
-            "type": "Array"
-          },
-          "access": "public",
-          "tagname": "",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/helpers/concat.ts",
-          "line": 18,
-          "description": "Concatenates the given arguments into a string.\n\nExample:\n\n\n```gjs\nimport { concat } from '@ember/helper';\n\n<template>\n{{yield (concat firstName \" \" lastName)}}\n\n{{! would yield name=\"<first name value> <last name value>\" to the component}}\n</template>\n```\n\nor for angle bracket invocation, you actually don't need concat at all.\n\n```handlebars\n<SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n```",
-          "access": "public",
-          "tagname": "",
-          "itemtype": "method",
-          "name": "concat",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/helpers/fn.ts",
-          "line": 18,
-          "description": "The `fn` helper allows you to ensure a function that you are passing off\nto another component, helper, or modifier has access to arguments that are\navailable in the template.\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```app/components/items-listing.gjs\nimport DisplayItem from './display-item';\n  \n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  handleSelected = (item) => {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\n  receive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\n  will receive the `item` from the loop as its first argument and the\n  string `'foo'` as its second argument.\n\nIn the example above, we used an arrow function to ensure that\n`handleSelected` is properly bound to the `items-list`, but let's explore what\nhappens if we left out the arrow function:\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\n\nexport default class ItemsList extends Component {\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when `handleSelected` is invoked inside the `display-item`\ncomponent, it will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via an arrow function or other means) before passing into `fn`!\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\n`fn` is built-in and does not require any additional imports.",
-          "itemtype": "method",
-          "name": "fn",
-          "access": "public",
-          "tagname": "",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/helpers/get.ts",
-          "line": 12,
-          "description": "Dynamically look up a property on an object. The second argument to `{{get}}`\nshould have a string value, although it can be bound.\n\nFor example, these two usages are equivalent:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n  \n  <template>\n    {{this.developer.name}}\n    {{get this.developer \"name\"}}\n  </template>\n}\n```\n\nIf there were several facts about a person, the `{{get}}` helper can dynamically\npick one:\n\n```app/templates/application.gjs\n<template>\n  <DeveloperDetail @factName=\"language\" />\n</template>\n```\n\n```handlebars\n{{get this.developer @factName}}\n```\n\nFor a more complex example, this template would allow the user to switch\nbetween showing the user's height and weight with a click:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n  \nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n\n  @tracked currentFact = 'name'\n\n  showFact = (fact) => {\n    this.currentFact = fact;\n  }\n  \n  <template>\n    {{get this.developer this.currentFact}}\n\n    <button {{on 'click' (fn this.showFact \"name\")}}>Show name</button>\n    <button {{on 'click' (fn this.showFact \"language\")}}>Show language</button>\n  </template>\n}\n```",
-          "access": "public",
-          "tagname": "",
-          "itemtype": "method",
-          "name": "get",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/helpers/hash.ts",
-          "line": 8,
-          "description": "Use the `{{hash}}` helper to create a hash to pass as an option to your\ncomponents. This is especially useful for contextual components where you can\njust yield a hash:\n\n```handlebars\n{{yield (hash\n   name='Sarah'\n   title=office\n)}}\n```\n\nWould result in an object such as:\n\n```js\n{ name: 'Sarah', title: this.get('office') }\n```\n\nWhere the `title` is bound to updates of the `office` property.\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```",
-          "itemtype": "method",
-          "name": "hash",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Object"
-            }
-          ],
-          "return": {
-            "description": "Hash",
-            "type": "Object"
-          },
-          "access": "public",
-          "tagname": "",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
-        {
-          "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
-          "line": 249,
-          "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePostComponent extends Component {\n  saveLike = () => {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```handlebars {data-filename=app/components/like-post.hbs}\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used an arrow function to ensure that `likePost` is\nproperly bound to the `items-list`, but let's explore what happens if we\nleft out the arrow function:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\n\nexport default class LikePostComponent extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via an arrow function or other means) before passing into `on`!",
-          "itemtype": "method",
-          "name": "on",
-          "access": "public",
-          "tagname": "",
-          "class": "@glimmer/tracking",
-          "module": "@glimmer/component"
-        },
         {
           "file": "packages/@glimmer/tracking/index.ts",
           "line": 17,
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.components.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.components.json
deleted file mode 100644
index c9e5375a8..000000000
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.components.json
+++ /dev/null
@@ -1,81 +0,0 @@
-{
-  "data": {
-    "id": "ember-7.1.0-Ember.Templates.components",
-    "type": "class",
-    "attributes": {
-      "name": "Ember.Templates.components",
-      "shortname": "Ember.Templates.components",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [],
-      "module": "@ember/routing",
-      "namespace": "",
-      "methods": [
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-          "line": 67,
-          "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <Input @value=\"987\" />\n</template>\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.",
-          "itemtype": "method",
-          "name": "Input",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Hash"
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.components",
-          "module": "@ember/component"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-          "line": 48,
-          "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```gjs\nimport { LinkTo } from '@ember/routing';\n  \n<template>\n  <LinkTo @route='photoGallery'>\n    Great Hamster Photos\n  </LinkTo>\n</template>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
-          "itemtype": "method",
-          "name": "LinkTo",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.components",
-          "module": "@ember/component"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-          "line": 10,
-          "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```app/components/word-editor.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
-          "itemtype": "method",
-          "name": "Textarea",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.components",
-          "module": "@ember/component"
-        }
-      ],
-      "events": [],
-      "properties": []
-    },
-    "relationships": {
-      "parent-class": {
-        "data": null
-      },
-      "descendants": {
-        "data": []
-      },
-      "module": {
-        "data": {
-          "id": "ember-7.1.0-@ember/routing",
-          "type": "module"
-        }
-      },
-      "project-version": {
-        "data": {
-          "id": "ember-7.1.0",
-          "type": "project-version"
-        }
-      }
-    }
-  }
-}
\ No newline at end of file
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.helpers.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.helpers.json
index eaf7afd47..947076820 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.helpers.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-Ember.Templates.helpers.json
@@ -14,391 +14,10 @@
       "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).",
       "access": "public",
       "tagname": "",
-      "methods": [
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-          "line": 46,
-          "description": "See [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
-          "itemtype": "method",
-          "name": "input",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Hash"
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "@ember/component"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-          "line": 264,
-          "description": "See [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
-          "itemtype": "method",
-          "name": "link-to",
-          "see": [
-            "{Ember.Templates.components.LinkTo}"
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "@ember/routing"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-          "line": 127,
-          "description": "See [Ember.Templates.components.Textarea](/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Textarea)",
-          "itemtype": "method",
-          "name": "textarea",
-          "see": [
-            "{Ember.Templates.components.Textarea}"
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "@ember/component"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/component.ts",
-          "line": 5,
-          "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```app/components/full-name.gjs\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```app/components/person-form.gjs\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```app/components/person-form.gjs\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```app/templates/application.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
-          "itemtype": "method",
-          "name": "component",
-          "since": "1.11.0",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
-          "line": 13,
-          "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\nAssuming the `@developers` argument contains this array:\n\n```javascript\n[{ name: 'Yehuda' },{ name: 'Tom' }, { name: 'Paul' }];\n```\n\n```handlebars\n<ul>\n  {{#each @developers as |person|}}\n    <li>Hello, {{person.name}}!</li>\n  {{/each}}\n</ul>\n```\n\nThe same rules apply to arrays of primitives.\n\n```javascript\n['Yehuda', 'Tom', 'Paul']\n```\n\n```handlebars\n<ul>\n  {{#each @developerNames as |name|}}\n    <li>Hello, {{name}}!</li>\n  {{/each}}\n</ul>\n```\n\nDuring iteration, the index of each item in the array is provided as a second block\nparameter.\n\n```handlebars\n<ul>\n  {{#each @developers as |person index|}}\n    <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n  {{/each}}\n</ul>\n```\n  \n`#each` is a keyword and does not need to be imported. \n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example:\n\n```javascript\npeople.map(person => {\n  return { ...person, type: 'developer' };\n});\n```\n\nIn this case, each time the `people` array is `map`-ed over, it will produce\nan new array with completely different objects between renders. In these cases,\nyou can help Ember determine how these objects related to each other with the\n`key` option:\n\n```handlebars\n<ul>\n  {{#each @developers key=\"name\" as |person|}}\n    <li>Hello, {{person.name}}!</li>\n  {{/each}}\n</ul>\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `@developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```handlebars\n<ul>\n  {{#each @developers as |person|}}\n    <li>{{person.name}} is available!</li>\n  {{else}}\n    <li>Sorry, nobody is available for this task.</li>\n  {{/each}}\n</ul>\n```",
-          "itemtype": "method",
-          "name": "each",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
-          "line": 126,
-          "description": "The `{{#each-in}}` keyword loops over properties on an object.\n\nFor example, given this component definition:\n\n```app/components/developer-details.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked developer = {\n    \"name\": \"Shelly Sails\",\n    \"age\": 42\n  };\n  \n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n \n`#each-in` is a keyword and does not need to be imported.",
-          "itemtype": "method",
-          "name": "each-in",
-          "access": "public",
-          "tagname": "",
-          "since": "2.1.0",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/element.ts",
-          "line": 84,
-          "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```handlebars\n{{#let (element @tagName) as |Tag|}}\n  <Tag class=\"my-element\">Hello</Tag>\n{{/let}}\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\n\nWhen `@tagName` is an empty string `\"\"`, the block content is rendered without\na wrapping element.\n\nPassing `null`, `undefined`, or non-string values will throw an assertion error.\n\nChanging the tag name will tear down and recreate the element and its contents.\n \nThe `element` helper is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "element",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "@ember/helper"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/helper.ts",
-          "line": 5,
-          "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
-          "itemtype": "method",
-          "name": "helper",
-          "access": "public",
-          "tagname": "",
-          "since": "3.27.0",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts",
-          "line": 5,
-          "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```app/templates/application.gjs\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```app/components/weather.gjs\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```app/components/weather.gjs\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```app/components/weather.gjs\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```app/templates/application.gjs\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "if",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts",
-          "line": 119,
-          "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```app/components/logged-in.gjs\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```app/templates/application.gjs\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```app/templates/application.gjs\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "unless",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/log.ts",
-          "line": 5,
-          "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```",
-          "itemtype": "method",
-          "name": "log",
-          "params": [
-            {
-              "name": "params",
-              "description": "",
-              "type": "Array"
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/modifier.ts",
-          "line": 5,
-          "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.",
-          "itemtype": "method",
-          "name": "modifier",
-          "access": "public",
-          "tagname": "",
-          "since": "3.27.0",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
-          "line": 9,
-          "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```app/components/my-child.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
-          "itemtype": "method",
-          "name": "mut",
-          "params": [
-            {
-              "name": "attr",
-              "description": "the \"two-way\" attribute that can be modified.",
-              "type": "Object",
-              "optional": true
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/page-title.ts",
-          "line": 5,
-          "description": "`page-title` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport pageTitle from 'ember-page-title/helpers/page-title';\n\n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
-          "itemtype": "method",
-          "name": "page-title",
-          "params": [
-            {
-              "name": "param",
-              "description": "",
-              "type": "String"
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
-          "line": 9,
-          "description": "The `readonly` helper let's you specify that a binding is one-way only,\ninstead of two-way.\n\nThis is a vestigial helper from the days of `@ember/component` and does not apply to\ncomponents extending from `@glimmer/component`.\n  \nWhen you pass a `readonly` binding from an outer context (e.g. parent component),\nto to an inner context (e.g. child component), you are saying that changing that\nproperty in the inner context does not change the value in the outer context.\n\nTo specify that a binding is read-only, when invoking the child `Component`:\n\n```js {data-filename=app/components/my-parent.js}\nexport default class MyParent extends Component {\n  totalClicks = 3;\n}\n```\n\nNow, when you update `childClickCount`:\n\n```js {data-filename=app/components/my-child.js}\nexport default class MyChild extends Component {\n  click() {\n    this.incrementProperty('childClickCount');\n  }\n}\n```\n\nThe value updates in the child component, but not the parent component:\n\n```handlebars {data-filename=app/templates/components/my-child.hbs}\n{{log childClickCount}} //-> 4\n```\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log totalClicks}} //-> 3\n<MyChild @childClickCount={{readonly totalClicks}} />\n```\nor\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log totalClicks}} //-> 3\n{{my-child childClickCount=(readonly totalClicks)}}\n```\n\n### Objects and Arrays\n\nWhen passing a property that is a complex object (e.g. object, array) instead of a primitive object (e.g. number, string),\nonly the reference to the object is protected using the readonly helper.\nThis means that you can change properties of the object both on the parent component, as well as the child component.\nThe `readonly` binding behaves similar to the `const` keyword in JavaScript.\n\nLet's look at an example:\n\nFirst let's set up the parent component:\n\n```js {data-filename=app/components/my-parent.js}\nimport Component from '@ember/component';\n\nexport default class MyParent extends Component {\n  clicks: null,\n\n  init() {\n    this._super(...arguments);\n    this.set('clicks', { total: 3 });\n  }\n}\n```\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 3\n<MyChild @childClicks={{readonly clicks}} />\n```\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 3\n{{my-child childClicks=(readonly clicks)}}\n```\n\nNow, if you update the `total` property of `childClicks`:\n\n```js {data-filename=app/components/my-child.js}\nimport Component from '@ember/component';\n\nexport default class MyChild extends Component {\n  click() {\n    this.get('clicks').incrementProperty('total');\n  }\n}\n```\n\nYou will see the following happen:\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 4\n<MyChild @childClicks={{readonly clicks}} />\n```\nor\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 4\n{{my-child childClicks=(readonly clicks)}}\n```\n\n```handlebars {data-filename=app/templates/components/my-child.hbs}\n{{log childClicks.total}} //-> 4\n```",
-          "itemtype": "method",
-          "name": "readonly",
-          "params": [
-            {
-              "name": "attr",
-              "description": "the read-only attribute.",
-              "type": "Object",
-              "optional": true
-            }
-          ],
-          "access": "private",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
-          "line": 10,
-          "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.",
-          "itemtype": "method",
-          "name": "unbound",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts",
-          "line": 5,
-          "description": "Use the {{unique-id}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\n```handlebars\n<input id={{unique-id}} type=\"email\" />\n```\nEach invocation of {{unique-id}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```handlebars\n{{#let (unique-id) as |emailId|}}\n  <label for={{emailId}}>Email address</label>\n  <input id={{emailId}} type=\"email\" />\n{{/let}}\n```",
-          "itemtype": "method",
-          "name": "unique-id",
-          "since": "4.4.0",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/modifiers/on.ts",
-          "line": 5,
-          "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```handlebars\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!",
-          "itemtype": "method",
-          "name": "on",
-          "access": "public",
-          "tagname": "",
-          "since": "3.11.0",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/syntax/in-element.ts",
-          "line": 5,
-          "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "in-element",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/syntax/let.ts",
-          "line": 5,
-          "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "let",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
-          "line": 17,
-          "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```app/templates/application.gjs\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```handlebars\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "mount",
-          "params": [
-            {
-              "name": "name",
-              "description": "Name of the engine to mount.",
-              "type": "String"
-            },
-            {
-              "name": "model",
-              "description": "Object that will be set as\n                        the model of the engine.",
-              "type": "Object",
-              "optional": true
-            }
-          ],
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
-          "line": 28,
-          "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```app/templates/application.gjs\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
-          "itemtype": "method",
-          "name": "outlet",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/index.ts",
-          "line": 109,
-          "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```app/templates/application.gjs\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```app/components/labeled-textfield.gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally you can `yield` properties into the context for use by the consumer:\n\n```app/templates/application.gjs\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```app/components/labeled-textfield.gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```app/templates/application.gjs\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```app/components/date-ranges.gjs\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```app/templates/application.gjs\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```app/components/banner.gjs\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```app/components/banner.gjs\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```app/components/banner/subtitle.gjs\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```app/components/banner/title.gjs\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```",
-          "itemtype": "method",
-          "name": "yield",
-          "params": [
-            {
-              "name": "options",
-              "description": "",
-              "type": "Hash"
-            }
-          ],
-          "return": {
-            "description": "HTML string",
-            "type": "String"
-          },
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/index.ts",
-          "line": 370,
-          "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```app/components/my-component.gjs\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```",
-          "itemtype": "method",
-          "name": "has-block",
-          "params": [
-            {
-              "name": "the",
-              "description": "name of the block. The name (at the moment) is either \"main\" or \"inverse\" (though only curly components support inverse)",
-              "type": "String"
-            }
-          ],
-          "return": {
-            "description": "`true` if the component was invoked with a block",
-            "type": "Boolean"
-          },
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/index.ts",
-          "line": 407,
-          "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\nHi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\nHi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```app/components/my-component.gjs\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
-          "itemtype": "method",
-          "name": "has-block-params",
-          "params": [
-            {
-              "name": "the",
-              "description": "name of the block. The name (at the moment) is either \"main\" or \"inverse\" (though only curly components support inverse)",
-              "type": "String"
-            }
-          ],
-          "return": {
-            "description": "`true` if the component was invoked with block params",
-            "type": "Boolean"
-          },
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        },
-        {
-          "file": "packages/@ember/-internals/glimmer/index.ts",
-          "line": 448,
-          "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
-          "itemtype": "method",
-          "name": "debugger",
-          "access": "public",
-          "tagname": "",
-          "class": "Ember.Templates.helpers",
-          "module": "ember"
-        }
-      ],
+      "methods": [],
       "events": [],
       "properties": []
     },
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-External.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-External.json
new file mode 100644
index 000000000..e309727fd
--- /dev/null
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-External.json
@@ -0,0 +1,60 @@
+{
+  "data": {
+    "id": "ember-7.1.0-External",
+    "type": "class",
+    "attributes": {
+      "name": "External",
+      "shortname": "External",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "@ember/helper",
+      "namespace": "",
+      "methods": [
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1654,
+          "description": "`pageTitle` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport { pageTitle } from 'ember-page-title';\n  \n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
+          "itemtype": "method",
+          "name": "pageTitle",
+          "params": [
+            {
+              "name": "param",
+              "description": "",
+              "type": "String"
+            }
+          ],
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "External",
+          "module": "@ember/helper"
+        }
+      ],
+      "events": [],
+      "properties": []
+    },
+    "relationships": {
+      "parent-class": {
+        "data": null
+      },
+      "descendants": {
+        "data": []
+      },
+      "module": {
+        "data": {
+          "id": "ember-7.1.0-@ember/helper",
+          "type": "module"
+        }
+      },
+      "project-version": {
+        "data": {
+          "id": "ember-7.1.0",
+          "type": "project-version"
+        }
+      }
+    }
+  }
+}
\ No newline at end of file
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-Helper.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-Helper.json
index 0a579017f..46e2fc6fb 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-Helper.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-Helper.json
@@ -14,7 +14,7 @@
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
       "line": 57,
-      "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```app/templates/application.gjs\nimport Cost from '../components/cost';\n  \n<template>\n  <Cost @cents={{230}} />\n</template>\n```\n\n```app/components/cost.gjs\nimport formatCurrency from '../helpers/format-currency';\n  \n<template>\n  <div>{{formatCurrency @cents currency=\"$\"}}</div>\n</template>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```gjs\nimport formatCurrency from '../helpers/format-currency';\n\n<template>\n  {{if @showMoney (formatCurrency @cents currency=\"$\")}}\n</template>\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```js {data-filename=app/helpers/format-currency.js}\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
+      "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Cost from '../components/cost';\n  \n<template>\n  <Cost @cents={{230}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/cost.gjs\"}\nimport formatCurrency from '../helpers/format-currency';\n  \n<template>\n  <div>{{formatCurrency @cents currency=\"$\"}}</div>\n</template>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```gjs\nimport formatCurrency from '../helpers/format-currency';\n\n<template>\n  {{if @showMoney (formatCurrency @cents currency=\"$\")}}\n</template>\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```js {data-filename=app/helpers/format-currency.js}\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
       "extends": "CoreObject",
       "access": "public",
       "tagname": "",
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-Keywords.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-Keywords.json
new file mode 100644
index 000000000..8a667676c
--- /dev/null
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-Keywords.json
@@ -0,0 +1,749 @@
+{
+  "data": {
+    "id": "ember-7.1.0-Keywords",
+    "type": "class",
+    "attributes": {
+      "name": "Keywords",
+      "shortname": "Keywords",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "@ember/helper",
+      "namespace": "",
+      "methods": [
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+          "line": 13,
+          "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\n```gjs {data-filename=\"app/components/developer-list.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperList extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nThe same rules apply to arrays of primitives:\n\n```gjs {data-filename=\"app/components/developer-names.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperNames extends Component {\n  developerNames = ['Yehuda', 'Tom', 'Paul'];\n\n  <template>\n    <ul>\n      {{#each this.developerNames as |name|}}\n        <li>Hello, {{name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`{{#each}}` also supports native JavaScript [`Set`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)\nvalues and other iterables:\n\n```gjs {data-filename=\"app/components/developer-set.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperSet extends Component {\n  developers = new Set([\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ]);\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nDuring iteration, the index of each item in the array is provided as a second\nblock parameter:\n\n```gjs {data-filename=\"app/components/developer-list-with-index.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperListWithIndex extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person index|}}\n        <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`#each` is a keyword and does not need to be imported.\n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example, mapping over `people` produces a new array of new objects on each\nrender. Use `key` so Ember can match items across those renders:\n\n```gjs {data-filename=\"app/components/mapped-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class MappedDevelopers extends Component {\n  people = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  get developers() {\n    return this.people.map((person) => {\n      return { ...person, type: 'developer' };\n    });\n  }\n\n  <template>\n    <ul>\n      {{#each this.developers key=\"name\" as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```gjs {data-filename=\"app/components/available-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class AvailableDevelopers extends Component {\n  developers = [];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>{{person.name}} is available!</li>\n      {{else}}\n        <li>Sorry, nobody is available for this task.</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```",
+          "itemtype": "method",
+          "name": "each",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+          "line": 189,
+          "description": "The `{{#each-in}}` keyword loops over properties on an object, or entries in a\nnative JavaScript [`Map`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map).\n\nFor example, given this component definition:\n\n```gjs {data-filename=\"app/components/developer-details.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class DeveloperDetails extends Component {\n  @tracked developer = {\n    name: 'Shelly Sails',\n    age: 42,\n  };\n\n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n\nThe same pattern works with a `Map`:\n\n```gjs {data-filename=\"app/components/developer-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperMap extends Component {\n  map = new Map([\n    ['name', 'Shelly Sails'],\n    ['age', 42],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nWhen a `Map` uses object keys, you can pass `key=\"@identity\"` to explicitly\ntrack entries across re-renders using the JavaScript identity of each key:\n\n```gjs {data-filename=\"app/components/object-keyed-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class ObjectKeyedMap extends Component {\n  map = new Map([\n    [{ name: 'one' }, 'foo'],\n    [{ name: 'two' }, 'bar'],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map key=\"@identity\" as |key value|}}\n        <li>{{key.name}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\n`#each-in` is a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "each-in",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "since": "2.1.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
+          "line": 9,
+          "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```gjs {data-filename=\"app/components/my-child.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
+          "itemtype": "method",
+          "name": "mut",
+          "params": [
+            {
+              "name": "attr",
+              "description": "the \"two-way\" attribute that can be modified.",
+              "type": "Object",
+              "optional": true
+            }
+          ],
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
+          "line": 9,
+          "description": "The `readonly` helper let's you specify that a binding is one-way only,\ninstead of two-way.\n\nThis is a vestigial helper from the days of `@ember/component` and does not apply to\ncomponents extending from `@glimmer/component`.\n  \nWhen you pass a `readonly` binding from an outer context (e.g. parent component),\nto to an inner context (e.g. child component), you are saying that changing that\nproperty in the inner context does not change the value in the outer context.\n\nTo specify that a binding is read-only, when invoking the child `Component`:\n\n```js {data-filename=app/components/my-parent.js}\nexport default class MyParent extends Component {\n  totalClicks = 3;\n}\n```\n\nNow, when you update `childClickCount`:\n\n```js {data-filename=app/components/my-child.js}\nexport default class MyChild extends Component {\n  click() {\n    this.incrementProperty('childClickCount');\n  }\n}\n```\n\nThe value updates in the child component, but not the parent component:\n\n```handlebars {data-filename=app/templates/components/my-child.hbs}\n{{log childClickCount}} //-> 4\n```\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log totalClicks}} //-> 3\n<MyChild @childClickCount={{readonly totalClicks}} />\n```\nor\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log totalClicks}} //-> 3\n{{my-child childClickCount=(readonly totalClicks)}}\n```\n\n### Objects and Arrays\n\nWhen passing a property that is a complex object (e.g. object, array) instead of a primitive object (e.g. number, string),\nonly the reference to the object is protected using the readonly helper.\nThis means that you can change properties of the object both on the parent component, as well as the child component.\nThe `readonly` binding behaves similar to the `const` keyword in JavaScript.\n\nLet's look at an example:\n\nFirst let's set up the parent component:\n\n```js {data-filename=app/components/my-parent.js}\nimport Component from '@ember/component';\n\nexport default class MyParent extends Component {\n  clicks: null,\n\n  init() {\n    this._super(...arguments);\n    this.set('clicks', { total: 3 });\n  }\n}\n```\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 3\n<MyChild @childClicks={{readonly clicks}} />\n```\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 3\n{{my-child childClicks=(readonly clicks)}}\n```\n\nNow, if you update the `total` property of `childClicks`:\n\n```js {data-filename=app/components/my-child.js}\nimport Component from '@ember/component';\n\nexport default class MyChild extends Component {\n  click() {\n    this.get('clicks').incrementProperty('total');\n  }\n}\n```\n\nYou will see the following happen:\n\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 4\n<MyChild @childClicks={{readonly clicks}} />\n```\nor\n```handlebars {data-filename=app/templates/components/my-parent.hbs}\n{{log clicks.total}} //-> 4\n{{my-child childClicks=(readonly clicks)}}\n```\n\n```handlebars {data-filename=app/templates/components/my-child.hbs}\n{{log childClicks.total}} //-> 4\n```",
+          "itemtype": "method",
+          "name": "readonly",
+          "params": [
+            {
+              "name": "attr",
+              "description": "the read-only attribute.",
+              "type": "Object",
+              "optional": true
+            }
+          ],
+          "noimport": "",
+          "static": 1,
+          "access": "private",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
+          "line": 10,
+          "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.\n \n `unbound` is a template keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "unbound",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
+          "line": 17,
+          "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```handlebars\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "mount",
+          "params": [
+            {
+              "name": "name",
+              "description": "Name of the engine to mount.",
+              "type": "String"
+            },
+            {
+              "name": "model",
+              "description": "Object that will be set as\n                        the model of the engine.",
+              "type": "Object",
+              "optional": true
+            }
+          ],
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
+          "line": 32,
+          "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "outlet",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 349,
+          "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```\n\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\nThe `hash` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "hash",
+          "access": "public",
+          "tagname": "",
+          "static": 1,
+          "noimport": "",
+          "params": [
+            {
+              "name": "options",
+              "description": "",
+              "type": "Object"
+            }
+          ],
+          "return": {
+            "description": "Hash",
+            "type": "Object"
+          },
+          "since": "2.3.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 386,
+          "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```\n\nThe `array` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "array",
+          "access": "public",
+          "tagname": "",
+          "static": 1,
+          "noimport": "",
+          "params": [
+            {
+              "name": "options",
+              "description": "",
+              "type": "Array"
+            }
+          ],
+          "return": {
+            "description": "Array",
+            "type": "Array"
+          },
+          "since": "3.8.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 493,
+          "description": "`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```gjs\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```gjs {data-filename=\"app/components/items-listing.gjs\"}\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```gjs {data-filename=\"app/components/items-list.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take a look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\nreceive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\nwill receive the `item` from the loop as its first argument and the\nstring `'foo'` as its second argument.\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\nThe `fn` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "fn",
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "since": "3.11.0",
+          "static": 1,
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 562,
+          "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```gjs\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nThe `gt` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "gt",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Number"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Number"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "since": "7.1.0",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 587,
+          "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nThe `gte` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "gte",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Number"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Number"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "since": "7.1.0",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 612,
+          "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```gjs\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nThe `lt` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "lt",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Number"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Number"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "since": "7.1.0",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 637,
+          "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nThe `lte` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "lte",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Number"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Number"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "since": "7.1.0",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 662,
+          "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```gjs\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.\n\nThe `element` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "element",
+          "params": [
+            {
+              "name": "tagName",
+              "description": "",
+              "type": "String"
+            }
+          ],
+          "noimport": "",
+          "since": "7.1.0",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 718,
+          "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nThe `eq` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "eq",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Unknown"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Unknown"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "static": 1,
+          "since": "7.1.0",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 743,
+          "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nThe `neq` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "neq",
+          "params": [
+            {
+              "name": "left",
+              "description": "",
+              "type": "Unknown"
+            },
+            {
+              "name": "right",
+              "description": "",
+              "type": "Unknown"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "static": 1,
+          "since": "7.1.0",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 768,
+          "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nThe `and` helper is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "and",
+          "params": [
+            {
+              "name": "args",
+              "description": "Two or more values to evaluate",
+              "type": "Unknown"
+            }
+          ],
+          "return": {
+            "description": "The first falsy value or the last value",
+            "type": "Unknown"
+          },
+          "noimport": "",
+          "static": 1,
+          "since": "7.1.0",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 793,
+          "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
+          "itemtype": "method",
+          "name": "or",
+          "params": [
+            {
+              "name": "args",
+              "description": "Two or more values to evaluate",
+              "type": "Unknown"
+            }
+          ],
+          "return": {
+            "description": "The first truthy value or the last value",
+            "type": "Unknown"
+          },
+          "noimport": "",
+          "static": 1,
+          "since": "7.1.0",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 819,
+          "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```gjs\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
+          "itemtype": "method",
+          "name": "not",
+          "params": [
+            {
+              "name": "value",
+              "description": "The value to negate",
+              "type": "Unknown"
+            }
+          ],
+          "return": {
+            "description": "",
+            "type": "Boolean"
+          },
+          "noimport": "",
+          "static": 1,
+          "since": "7.1.0",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 844,
+          "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components, `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally, you can `yield` properties into the context for use by the consumer:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```gjs {data-filename=\"app/components/date-ranges.gjs\"}\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner/subtitle.gjs\"}\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```gjs {data-filename=\"app/components/banner/title.gjs\"}\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```\n\n`yield` is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "yield",
+          "params": [
+            {
+              "name": "options",
+              "description": "",
+              "type": "Hash"
+            }
+          ],
+          "return": {
+            "description": "HTML string",
+            "type": "String"
+          },
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1109,
+          "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```\n\n`has-block` is available as a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "has-block",
+          "params": [
+            {
+              "name": "blockName",
+              "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+              "type": "String"
+            }
+          ],
+          "return": {
+            "description": "`true` if the component was invoked with a block",
+            "type": "Boolean"
+          },
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1150,
+          "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\n  Hi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
+          "itemtype": "method",
+          "name": "has-block-params",
+          "static": 1,
+          "noimport": "",
+          "params": [
+            {
+              "name": "blockName",
+              "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+              "type": "String"
+            }
+          ],
+          "return": {
+            "description": "`true` if the component was invoked with block params",
+            "type": "Boolean"
+          },
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1193,
+          "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
+          "itemtype": "method",
+          "name": "debugger",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1238,
+          "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```gjs {data-filename=\"app/components/full-name.gjs\"}\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
+          "itemtype": "method",
+          "name": "component",
+          "since": "1.11.0",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1328,
+          "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
+          "itemtype": "method",
+          "name": "helper",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "since": "3.27.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1368,
+          "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "if",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1484,
+          "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```gjs {data-filename=\"app/components/logged-in.gjs\"}\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "unless",
+          "noimport": "",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1596,
+          "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```\n \n`log` is built-in as a template keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "log",
+          "noimport": "",
+          "static": 1,
+          "params": [
+            {
+              "name": "params",
+              "description": "",
+              "type": "Array"
+            }
+          ],
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1614,
+          "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.\n\n`modifier` is built-in as a template keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "modifier",
+          "static": 1,
+          "access": "public",
+          "tagname": "",
+          "since": "3.27.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1674,
+          "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "let",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@ember/helper/index.ts",
+          "line": 1714,
+          "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
+          "itemtype": "method",
+          "name": "in-element",
+          "params": [
+            {
+              "name": "destinationElement",
+              "description": "the DOM element to render into. It must exist at the time\n of rendering.",
+              "type": "Element"
+            },
+            {
+              "name": "insertBefore",
+              "description": "named argument, by default the DOM element's content is replaced when used as\n `destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\n append the block content to the end of any existing content. Any other value than\n `null` is currently not supported.",
+              "type": "Boolean"
+            }
+          ],
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        },
+        {
+          "file": "packages/@glimmer/runtime/lib/component/template-only.ts",
+          "line": 59,
+          "description": "This utility function is used to declare a given component has no backing class. When the rendering engine detects this it\nis able to perform a number of optimizations. Templates that are associated with `templateOnly()` will be rendered _as is_\nwithout adding a wrapping `<div>` (or any of the other element customization behaviors of [@ember/component](/ember/release/classes/Component)).\nSpecifically, this means that the template will be rendered as \"outer HTML\".\n\nIn general, this method will be used by build time tooling and would not be directly written in an application. However,\nat times it may be useful to use directly to leverage the \"outer HTML\" semantics mentioned above. For example, if an addon would like\nto use these semantics for its templates but cannot be certain it will only be consumed by applications that have enabled the\n`template-only-glimmer-components` optional feature.",
+          "example": [
+            "\n\n```js\nimport { templateOnlyComponent } from '@glimmer/runtime';\n\nexport default templateOnlyComponent();\n```"
+          ],
+          "access": "public",
+          "tagname": "",
+          "itemtype": "method",
+          "name": "templateOnly",
+          "params": [
+            {
+              "name": "moduleName",
+              "description": "the module name that the template only component represents, this will be used for debugging purposes",
+              "type": "String"
+            }
+          ],
+          "category": [
+            "EMBER_GLIMMER_SET_COMPONENT_TEMPLATE"
+          ],
+          "class": "Keywords",
+          "module": "@glimmer/component"
+        },
+        {
+          "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
+          "line": 253,
+          "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```handlebars\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!\n\nThe `on` modifier is a keyword and does not need to be imported.",
+          "itemtype": "method",
+          "name": "on",
+          "static": 1,
+          "noimport": "",
+          "access": "public",
+          "tagname": "",
+          "since": "3.11.0",
+          "class": "Keywords",
+          "module": "@ember/helper"
+        }
+      ],
+      "events": [],
+      "properties": []
+    },
+    "relationships": {
+      "parent-class": {
+        "data": null
+      },
+      "descendants": {
+        "data": []
+      },
+      "module": {
+        "data": {
+          "id": "ember-7.1.0-@ember/helper",
+          "type": "module"
+        }
+      },
+      "project-version": {
+        "data": {
+          "id": "ember-7.1.0",
+          "type": "project-version"
+        }
+      }
+    }
+  }
+}
\ No newline at end of file
diff --git a/json-docs/ember/7.1.0/classes/ember-7.1.0-RouterService.json b/json-docs/ember/7.1.0/classes/ember-7.1.0-RouterService.json
index 3bf5b3bc3..a2160758c 100644
--- a/json-docs/ember/7.1.0/classes/ember-7.1.0-RouterService.json
+++ b/json-docs/ember/7.1.0/classes/ember-7.1.0-RouterService.json
@@ -14,7 +14,7 @@
       "namespace": "",
       "file": "packages/@ember/routing/router-service.ts",
       "line": 28,
-      "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```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.",
+      "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": "",
       "extends": "Service",
@@ -22,7 +22,7 @@
         {
           "file": "packages/@ember/routing/router-service.ts",
           "line": 90,
-          "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```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```",
+          "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",
           "params": [
@@ -90,7 +90,7 @@
         {
           "file": "packages/@ember/routing/router-service.ts",
           "line": 190,
-          "description": "Generate a URL based on the supplied route name and optionally a model. The\nURL is returned as a string that can be used for any purpose.\n\nIn this example, the URL for the `author.books` route for a given author\nis copied to the clipboard.\n\n```app/templates/application.gjs\nimport CopyLink from '../components/copy-link';\n  \n<template>\n  <CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n</template>\n```\n\n```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```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```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```",
+          "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",
           "params": [
@@ -123,7 +123,7 @@
         {
           "file": "packages/@ember/routing/router-service.ts",
           "line": 274,
-          "description": "Returns `true` if `routeName/models/queryParams` is the active route, where `models` and `queryParams` are optional.\nSee [model](api/ember/release/classes/Route/methods/model?anchor=model) and\n[queryParams](/api/ember/3.7/classes/Route/properties/queryParams?anchor=queryParams) for more information about these arguments.\n\nIn the following example, `isActive` will return `true` if the current route is `/posts`.\n\n```app/components/posts.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```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.",
+          "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",
           "params": [
@@ -786,7 +786,7 @@
         {
           "file": "packages/@ember/routing/router-service.ts",
           "line": 732,
-          "description": "The `currentRoute` property contains metadata about the current leaf route.\nIt returns a `RouteInfo` object that has information like the route name,\nparams, query params and more.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nThis property is guaranteed to change whenever a route transition\nhappens (even when that transition only changes parameters\nand doesn't change the active route).\n\nUsage example:\n```app/components/header.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```",
+          "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",
           "type": "RouteInfo",
diff --git a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/component.json b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/component.json
index d3a1f1c16..3845558b1 100644
--- a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/component.json
+++ b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/component.json
@@ -7,16 +7,14 @@
       "submodules": {},
       "elements": {},
       "fors": {
-        "Ember.Templates.helpers": 1,
         "@ember/component": 1,
-        "Ember.Templates.components": 1,
         "@ember/component/helper": 1
       },
       "namespaces": {},
       "tag": "main",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
       "line": 57,
-      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\ndefault component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\ndefault for older editions of Ember (pre 3.15) but are still supported.\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the\n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```js {data-filename=app/components/person-profile.js}\nimport Component from '@ember/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked name = 'Jill'\n}\n```\n\n```handlebars {data-filename=app/components/person-profile.hbs}\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```handlebars {data-filename=app/components/person-profile.hbs}\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
+      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\ndefault component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\ndefault for older editions of Ember (pre 3.15) but are still supported.\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the\n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```js {data-filename=app/components/person-profile.js}\nimport Component from '@ember/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked name = 'Jill'\n}\n```\n\n```handlebars {data-filename=app/components/person-profile.hbs}\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```handlebars {data-filename=app/components/person-profile.hbs}\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in and importable helpers are described under the [@ember/helper](../modules/@ember%2Fhelper).\nmodule. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
       "itemtype": "main",
       "access": "public",
       "tagname": "",
@@ -28,6 +26,37 @@
       "privateclasses": [],
       "staticfunctions": {
         "@ember/component": [
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
+            "line": 46,
+            "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <Input @value=\"987\" />\n</template>\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.",
+            "itemtype": "method",
+            "name": "Input",
+            "static": 1,
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Hash"
+              }
+            ],
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/component",
+            "module": "@ember/component"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
+            "line": 10,
+            "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```gjs {data-filename=\"app/components/word-editor.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
+            "itemtype": "method",
+            "name": "Textarea",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/component",
+            "module": "@ember/component"
+          },
           {
             "file": "packages/@ember/component/index.ts",
             "line": 109,
@@ -149,6 +178,37 @@
       },
       "allstaticfunctions": {
         "@ember/component": [
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
+            "line": 46,
+            "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <Input @value=\"987\" />\n</template>\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.",
+            "itemtype": "method",
+            "name": "Input",
+            "static": 1,
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Hash"
+              }
+            ],
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/component",
+            "module": "@ember/component"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
+            "line": 10,
+            "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```gjs {data-filename=\"app/components/word-editor.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
+            "itemtype": "method",
+            "name": "Textarea",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/component",
+            "module": "@ember/component"
+          },
           {
             "file": "packages/@ember/component/index.ts",
             "line": 109,
diff --git a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/helper.json b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/helper.json
index 310471952..9987c562c 100644
--- a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/helper.json
+++ b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/helper.json
@@ -7,108 +7,1526 @@
       "submodules": {},
       "elements": {},
       "fors": {
-        "Ember.Templates.helpers": 1,
-        "@ember/helper": 1
+        "Keywords": 1,
+        "@ember/helper": 1,
+        "External": 1
       },
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@ember/helper/index.ts",
-      "line": 1,
+      "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
+      "line": 249,
       "parent": null,
       "publicclasses": [],
       "privateclasses": [],
       "staticfunctions": {
+        "Keywords": [
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 768,
+            "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nThe `and` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "and",
+            "params": [
+              {
+                "name": "args",
+                "description": "Two or more values to evaluate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "The first falsy value or the last value",
+              "type": "Unknown"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 386,
+            "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```\n\nThe `array` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "array",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Array"
+              }
+            ],
+            "return": {
+              "description": "Array",
+              "type": "Array"
+            },
+            "since": "3.8.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1238,
+            "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```gjs {data-filename=\"app/components/full-name.gjs\"}\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
+            "itemtype": "method",
+            "name": "component",
+            "since": "1.11.0",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1193,
+            "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
+            "itemtype": "method",
+            "name": "debugger",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+            "line": 13,
+            "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\n```gjs {data-filename=\"app/components/developer-list.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperList extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nThe same rules apply to arrays of primitives:\n\n```gjs {data-filename=\"app/components/developer-names.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperNames extends Component {\n  developerNames = ['Yehuda', 'Tom', 'Paul'];\n\n  <template>\n    <ul>\n      {{#each this.developerNames as |name|}}\n        <li>Hello, {{name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`{{#each}}` also supports native JavaScript [`Set`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)\nvalues and other iterables:\n\n```gjs {data-filename=\"app/components/developer-set.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperSet extends Component {\n  developers = new Set([\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ]);\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nDuring iteration, the index of each item in the array is provided as a second\nblock parameter:\n\n```gjs {data-filename=\"app/components/developer-list-with-index.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperListWithIndex extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person index|}}\n        <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`#each` is a keyword and does not need to be imported.\n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example, mapping over `people` produces a new array of new objects on each\nrender. Use `key` so Ember can match items across those renders:\n\n```gjs {data-filename=\"app/components/mapped-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class MappedDevelopers extends Component {\n  people = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  get developers() {\n    return this.people.map((person) => {\n      return { ...person, type: 'developer' };\n    });\n  }\n\n  <template>\n    <ul>\n      {{#each this.developers key=\"name\" as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```gjs {data-filename=\"app/components/available-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class AvailableDevelopers extends Component {\n  developers = [];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>{{person.name}} is available!</li>\n      {{else}}\n        <li>Sorry, nobody is available for this task.</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```",
+            "itemtype": "method",
+            "name": "each",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+            "line": 189,
+            "description": "The `{{#each-in}}` keyword loops over properties on an object, or entries in a\nnative JavaScript [`Map`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map).\n\nFor example, given this component definition:\n\n```gjs {data-filename=\"app/components/developer-details.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class DeveloperDetails extends Component {\n  @tracked developer = {\n    name: 'Shelly Sails',\n    age: 42,\n  };\n\n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n\nThe same pattern works with a `Map`:\n\n```gjs {data-filename=\"app/components/developer-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperMap extends Component {\n  map = new Map([\n    ['name', 'Shelly Sails'],\n    ['age', 42],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nWhen a `Map` uses object keys, you can pass `key=\"@identity\"` to explicitly\ntrack entries across re-renders using the JavaScript identity of each key:\n\n```gjs {data-filename=\"app/components/object-keyed-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class ObjectKeyedMap extends Component {\n  map = new Map([\n    [{ name: 'one' }, 'foo'],\n    [{ name: 'two' }, 'bar'],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map key=\"@identity\" as |key value|}}\n        <li>{{key.name}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\n`#each-in` is a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "each-in",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "2.1.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 662,
+            "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```gjs\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.\n\nThe `element` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "element",
+            "params": [
+              {
+                "name": "tagName",
+                "description": "",
+                "type": "String"
+              }
+            ],
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 718,
+            "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nThe `eq` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "eq",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Unknown"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 493,
+            "description": "`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```gjs\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```gjs {data-filename=\"app/components/items-listing.gjs\"}\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```gjs {data-filename=\"app/components/items-list.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take a look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\nreceive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\nwill receive the `item` from the loop as its first argument and the\nstring `'foo'` as its second argument.\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\nThe `fn` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "fn",
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.11.0",
+            "static": 1,
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 562,
+            "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```gjs\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nThe `gt` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "gt",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 587,
+            "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nThe `gte` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "gte",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1109,
+            "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```\n\n`has-block` is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "has-block",
+            "params": [
+              {
+                "name": "blockName",
+                "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+                "type": "String"
+              }
+            ],
+            "return": {
+              "description": "`true` if the component was invoked with a block",
+              "type": "Boolean"
+            },
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1150,
+            "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\n  Hi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
+            "itemtype": "method",
+            "name": "has-block-params",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "blockName",
+                "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+                "type": "String"
+              }
+            ],
+            "return": {
+              "description": "`true` if the component was invoked with block params",
+              "type": "Boolean"
+            },
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 349,
+            "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```\n\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\nThe `hash` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "hash",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Object"
+              }
+            ],
+            "return": {
+              "description": "Hash",
+              "type": "Object"
+            },
+            "since": "2.3.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1328,
+            "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
+            "itemtype": "method",
+            "name": "helper",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.27.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1368,
+            "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "if",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1714,
+            "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "in-element",
+            "params": [
+              {
+                "name": "destinationElement",
+                "description": "the DOM element to render into. It must exist at the time\n of rendering.",
+                "type": "Element"
+              },
+              {
+                "name": "insertBefore",
+                "description": "named argument, by default the DOM element's content is replaced when used as\n `destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\n append the block content to the end of any existing content. Any other value than\n `null` is currently not supported.",
+                "type": "Boolean"
+              }
+            ],
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1674,
+            "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "let",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1596,
+            "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```\n \n`log` is built-in as a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "log",
+            "noimport": "",
+            "static": 1,
+            "params": [
+              {
+                "name": "params",
+                "description": "",
+                "type": "Array"
+              }
+            ],
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 612,
+            "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```gjs\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nThe `lt` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "lt",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 637,
+            "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nThe `lte` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "lte",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1614,
+            "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.\n\n`modifier` is built-in as a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "modifier",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "since": "3.27.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
+            "line": 17,
+            "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```hbs\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "mount",
+            "params": [
+              {
+                "name": "name",
+                "description": "Name of the engine to mount.",
+                "type": "String"
+              },
+              {
+                "name": "model",
+                "description": "Object that will be set as\n                        the model of the engine.",
+                "type": "Object",
+                "optional": true
+              }
+            ],
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
+            "line": 9,
+            "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```gjs {data-filename=\"app/components/my-child.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
+            "itemtype": "method",
+            "name": "mut",
+            "params": [
+              {
+                "name": "attr",
+                "description": "the \"two-way\" attribute that can be modified.",
+                "type": "Object",
+                "optional": true
+              }
+            ],
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 743,
+            "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nThe `neq` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "neq",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Unknown"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 819,
+            "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```gjs\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
+            "itemtype": "method",
+            "name": "not",
+            "params": [
+              {
+                "name": "value",
+                "description": "The value to negate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
+            "line": 253,
+            "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```hbs\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!\n\nThe `on` modifier is a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "on",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.11.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 793,
+            "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
+            "itemtype": "method",
+            "name": "or",
+            "params": [
+              {
+                "name": "args",
+                "description": "Two or more values to evaluate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "The first truthy value or the last value",
+              "type": "Unknown"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
+            "line": 32,
+            "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "outlet",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
+            "line": 10,
+            "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.\n \n `unbound` is a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "unbound",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1484,
+            "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```gjs {data-filename=\"app/components/logged-in.gjs\"}\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "unless",
+            "noimport": "",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 844,
+            "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components, `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally, you can `yield` properties into the context for use by the consumer:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```gjs {data-filename=\"app/components/date-ranges.gjs\"}\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner/subtitle.gjs\"}\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```gjs {data-filename=\"app/components/banner/title.gjs\"}\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```\n\n`yield` is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "yield",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Hash"
+              }
+            ],
+            "return": {
+              "description": "HTML string",
+              "type": "String"
+            },
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          }
+        ],
         "@ember/helper": [
           {
             "file": "packages/@ember/helper/index.ts",
-            "line": 26,
-            "description": "`capabilities` returns a capabilities configuration which can be used to modify\nthe behavior of the manager. Manager capabilities _must_ be provided using the\n`capabilities` function, as the underlying implementation can change over time.\n\nThe first argument to capabilities is a version string, which is the version of\nEmber that the capabilities were defined in. Ember can add new versions at any\ntime, and these may have entirely different behaviors, but it will not remove\nold versions until the next major version.\n\n```js\ncapabilities('3.23');\n```\n\nThe second argument is an object of capabilities and boolean values indicating\nwhether they are enabled or disabled.\n\n```js\ncapabilities('3.23', {\n  hasValue: true,\n  hasDestructor: true,\n});\n```\n\nIf no value is specified, then the default value will be used.\n\n### `3.23` capabilities\n\n#### `hasDestroyable`\n\n- Default value: false\n\nDetermines if the helper has a destroyable to include in the destructor\nhierarchy. If enabled, the `getDestroyable` hook will be called, and its result\nwill be associated with the destroyable parent block.\n\n#### `hasValue`\n\n- Default value: false\n\nDetermines if the helper has a value which can be used externally. The helper's\n`getValue` hook will be run whenever the value of the helper is accessed if this\ncapability is enabled.",
+            "line": 26,
+            "description": "`capabilities` returns a capabilities configuration which can be used to modify\nthe behavior of the manager. Manager capabilities _must_ be provided using the\n`capabilities` function, as the underlying implementation can change over time.\n\nThe first argument to capabilities is a version string, which is the version of\nEmber that the capabilities were defined in. Ember can add new versions at any\ntime, and these may have entirely different behaviors, but it will not remove\nold versions until the next major version.\n\n```js\ncapabilities('3.23');\n```\n\nThe second argument is an object of capabilities and boolean values indicating\nwhether they are enabled or disabled.\n\n```js\ncapabilities('3.23', {\n  hasValue: true,\n  hasDestructor: true,\n});\n```\n\nIf no value is specified, then the default value will be used.\n\n### `3.23` capabilities\n\n#### `hasDestroyable`\n\n- Default value: false\n\nDetermines if the helper has a destroyable to include in the destructor\nhierarchy. If enabled, the `getDestroyable` hook will be called, and its result\nwill be associated with the destroyable parent block.\n\n#### `hasValue`\n\n- Default value: false\n\nDetermines if the helper has a value which can be used externally. The helper's\n`getValue` hook will be run whenever the value of the helper is accessed if this\ncapability is enabled.",
+            "itemtype": "method",
+            "name": "capabilities",
+            "static": 1,
+            "params": [
+              {
+                "name": "managerApiVersion",
+                "description": "The version of capabilities that are being used",
+                "type": "String"
+              },
+              {
+                "name": "options",
+                "description": "The capabilities values"
+              }
+            ],
+            "return": {
+              "description": "The capabilities object instance",
+              "type": "Capabilities"
+            },
+            "since": "3.23.0",
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 414,
+            "description": "The `{{concat}}` helper Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\n import { concat } from '@ember/helper';\n\n <template>\n   {{yield (concat firstName \" \" lastName)}}\n\n   {{! would yield name=\"<first name value> <last name value>\" to the component}}\n </template>\n ```\n\n or for angle bracket invocation, you actually don't need concat at all:\n\n ```handlebars\n <SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n ```",
+            "itemtype": "method",
+            "name": "concat",
+            "exampleimport": "import { concat } from '@ember/helper';",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "since": "1.13.0",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 445,
+            "description": "The `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
+            "itemtype": "method",
+            "name": "get",
+            "since": "2.1.0",
+            "exampleimport": "import { get } from '@ember/helper';",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 276,
+            "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```gjs {data-filename=\"app/components/data-loader.js\"}\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n\n<template>\n  {{this.value}}\n</template>\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
+            "itemtype": "method",
+            "name": "invokeHelper",
+            "static": 1,
+            "params": [
+              {
+                "name": "context",
+                "description": "The parent context of the helper",
+                "type": "Object"
+              },
+              {
+                "name": "definition",
+                "description": "The helper definition",
+                "type": "Object"
+              },
+              {
+                "name": "computeArgs",
+                "description": "An optional function that produces args",
+                "type": "Function"
+              }
+            ],
+            "return": {
+              "description": ""
+            },
+            "since": "3.23.0",
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 81,
+            "description": "Sets the helper manager for an object or function.\n\n```js\nsetHelperManager((owner) => new ClassHelperManager(owner), Helper)\n```\n\nWhen a value is used as a helper in a template, the helper manager is looked up\non the object by walking up its prototype chain and finding the first helper\nmanager. This manager then receives the value and can create and manage an\ninstance of a helper from it. This provides a layer of indirection that allows\nusers to design high-level helper APIs, without Ember needing to worry about the\ndetails. High-level APIs can be experimented with and iterated on while the\ncore of Ember helpers remains stable, and new APIs can be introduced gradually\nover time to existing code bases.\n\n`setHelperManager` receives two arguments:\n\n1. A factory function, which receives the `owner` and returns an instance of a\n  helper manager.\n2. A helper definition, which is the object or function to associate the factory function with.\n\nThe first time the object is looked up, the factory function will be called to\ncreate the helper manager. It will be cached, and in subsequent lookups the\ncached helper manager will be used instead.\n\nOnly one helper manager is guaranteed to exist per `owner` and per usage of\n`setHelperManager`, so many helpers will end up using the same instance of the\nhelper manager. As such, you should only store state that is related to the\nmanager itself. If you want to store state specific to a particular helper\ndefinition, you should assign a unique helper manager to that helper. In\ngeneral, most managers should either be stateless, or only have the `owner` they\nwere created with as state.\n\nHelper managers must fulfill the following interface (This example uses\n[TypeScript interfaces](https://www.typescriptlang.org/docs/handbook/interfaces.html)\nfor precision, you do not need to write helper managers using TypeScript):\n\n```ts\ninterface HelperManager<HelperStateBucket> {\n  capabilities: HelperCapabilities;\n\n  createHelper(definition: HelperDefinition, args: TemplateArgs): HelperStateBucket;\n\n  getValue?(bucket: HelperStateBucket): unknown;\n\n  runEffect?(bucket: HelperStateBucket): void;\n\n  getDestroyable?(bucket: HelperStateBucket): object;\n}\n```\n\nThe capabilities property _must_ be provided using the `capabilities()` function\nimported from the same module as `setHelperManager`:\n\n```js\nimport { capabilities } from '@ember/helper';\n\nclass MyHelperManager {\n  capabilities = capabilities('3.21.0', { hasValue: true });\n\n  // ...snip...\n}\n```\n\nBelow is a description of each of the methods on the interface and their\nfunctions.\n\n#### `createHelper`\n\n`createHelper` is a required hook on the HelperManager interface. The hook is\npassed the definition of the helper that is currently being created, and is\nexpected to return a _state bucket_. This state bucket is what represents the\ncurrent state of the helper, and will be passed to the other lifecycle hooks at\nappropriate times. It is not necessarily related to the definition of the\nhelper itself - for instance, you could return an object _containing_ an\ninstance of the helper:\n\n```js\nclass MyManager {\n  createHelper(Definition, args) {\n    return {\n      instance: new Definition(args);\n    };\n  }\n}\n```\n\nThis allows the manager to store metadata that it doesn't want to expose to the\nuser.\n\nThis hook is _not_ autotracked - changes to tracked values used within this hook\nwill _not_ result in a call to any of the other lifecycle hooks. This is because\nit is unclear what should happen if it invalidates, and rather than make a\ndecision at this point, the initial API is aiming to allow as much expressivity\nas possible. This could change in the future with changes to capabilities and\ntheir behaviors.\n\nIf users do want to autotrack some values used during construction, they can\neither create the instance of the helper in `runEffect` or `getValue`, or they\ncan use the `cache` API to autotrack the `createHelper` hook themselves. This\nprovides maximum flexibility and expressiveness to manager authors.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called as discovered during DOM construction\n- called in definition order in the template\n\n#### `getValue`\n\n`getValue` is an optional hook that should return the value of the helper. This\nis the value that is returned from the helper and passed into the template.\n\nThis hook is called when the value is requested from the helper (e.g. when the\ntemplate is rendering and the helper value is needed). The hook is autotracked,\nand will rerun whenever any tracked values used inside of it are updated.\nOtherwise it does not rerun.\n\n> Note: This means that arguments which are not _consumed_ within the hook will\n> not trigger updates.\n\nThis hook is only called for helpers with the `hasValue` capability enabled.\nThis hook has the following timing semantics:\n\n**Always**\n- called the first time the helper value is requested\n- called after autotracked state has changed\n\n**Never**\n- called if the `hasValue` capability is disabled\n\n#### `runEffect`\n\n`runEffect` is an optional hook that should run the effect that the helper is\napplying, setting it up or updating it.\n\nThis hook is scheduled to be called some time after render and prior to paint.\nThere is not a guaranteed, 1-to-1 relationship between a render pass and this\nhook firing. For instance, multiple render passes could occur, and the hook may\nonly trigger once. It may also never trigger if it was dirtied in one render\npass and then destroyed in the next.\n\nThe hook is autotracked, and will rerun whenever any tracked values used inside\nof it are updated. Otherwise it does not rerun.\n\nThe hook is also run during a time period where state mutations are _disabled_\nin Ember. Any tracked state mutation will throw an error during this time,\nincluding changes to tracked properties, changes made using `set`, updates\nto computed properties, etc. This is meant to prevent infinite rerenders and\nother antipatterns.\n\nThis hook is only called for helpers with the `hasScheduledEffect` capability\nenabled. This hook is also not called in SSR currently, though this could be\nadded as a capability in the future. It has the following timing semantics:\n\n**Always**\n- called after the helper was first created, if the helper has not been\n  destroyed since creation\n- called after autotracked state has changed, if the helper has not been\n  destroyed during render\n\n**Never**\n- called if the `hasScheduledEffect` capability is disabled\n- called in SSR\n\n#### `getDestroyable`\n\n`getDestroyable` is an optional hook that users can use to register a\ndestroyable object for the helper. This destroyable will be registered to the\ncontaining block or template parent, and will be destroyed when it is destroyed.\nSee the [Destroyables RFC](https://github.com/emberjs/rfcs/blob/master/text/0580-destroyables.md)\nfor more details.\n\n`getDestroyable` is only called if the `hasDestroyable` capability is enabled.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called immediately after the `createHelper` hook is called\n\n**Never**\n- called if the `hasDestroyable` capability is disabled",
+            "itemtype": "method",
+            "name": "setHelperManager",
+            "static": 1,
+            "params": [
+              {
+                "name": "factory",
+                "description": "A factory function which receives an optional owner, and returns a helper manager",
+                "type": "Function"
+              },
+              {
+                "name": "definition",
+                "description": "The definition to associate the manager factory with",
+                "type": "Object"
+              }
+            ],
+            "return": {
+              "description": "The definition passed into setHelperManager",
+              "type": "Object"
+            },
+            "since": "3.23.0",
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 690,
+            "description": "Use the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```gjs\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
+            "itemtype": "method",
+            "name": "uniqueId",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "exampleimport": "import { uniqueId } from '@ember/helper';",
+            "since": "4.4.0",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          }
+        ],
+        "External": [
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1654,
+            "description": "`pageTitle` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport { pageTitle } from 'ember-page-title';\n  \n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
+            "itemtype": "method",
+            "name": "pageTitle",
+            "params": [
+              {
+                "name": "param",
+                "description": "",
+                "type": "String"
+              }
+            ],
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "External",
+            "module": "@ember/helper"
+          }
+        ]
+      },
+      "allstaticfunctions": {
+        "Keywords": [
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 768,
+            "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nThe `and` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "and",
+            "params": [
+              {
+                "name": "args",
+                "description": "Two or more values to evaluate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "The first falsy value or the last value",
+              "type": "Unknown"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 386,
+            "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```\n\nThe `array` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "array",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Array"
+              }
+            ],
+            "return": {
+              "description": "Array",
+              "type": "Array"
+            },
+            "since": "3.8.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1238,
+            "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```gjs {data-filename=\"app/components/full-name.gjs\"}\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
+            "itemtype": "method",
+            "name": "component",
+            "since": "1.11.0",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1193,
+            "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
+            "itemtype": "method",
+            "name": "debugger",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+            "line": 13,
+            "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\n```gjs {data-filename=\"app/components/developer-list.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperList extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nThe same rules apply to arrays of primitives:\n\n```gjs {data-filename=\"app/components/developer-names.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperNames extends Component {\n  developerNames = ['Yehuda', 'Tom', 'Paul'];\n\n  <template>\n    <ul>\n      {{#each this.developerNames as |name|}}\n        <li>Hello, {{name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`{{#each}}` also supports native JavaScript [`Set`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)\nvalues and other iterables:\n\n```gjs {data-filename=\"app/components/developer-set.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperSet extends Component {\n  developers = new Set([\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ]);\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nDuring iteration, the index of each item in the array is provided as a second\nblock parameter:\n\n```gjs {data-filename=\"app/components/developer-list-with-index.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperListWithIndex extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person index|}}\n        <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`#each` is a keyword and does not need to be imported.\n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example, mapping over `people` produces a new array of new objects on each\nrender. Use `key` so Ember can match items across those renders:\n\n```gjs {data-filename=\"app/components/mapped-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class MappedDevelopers extends Component {\n  people = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  get developers() {\n    return this.people.map((person) => {\n      return { ...person, type: 'developer' };\n    });\n  }\n\n  <template>\n    <ul>\n      {{#each this.developers key=\"name\" as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```gjs {data-filename=\"app/components/available-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class AvailableDevelopers extends Component {\n  developers = [];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>{{person.name}} is available!</li>\n      {{else}}\n        <li>Sorry, nobody is available for this task.</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```",
+            "itemtype": "method",
+            "name": "each",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
+            "line": 189,
+            "description": "The `{{#each-in}}` keyword loops over properties on an object, or entries in a\nnative JavaScript [`Map`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map).\n\nFor example, given this component definition:\n\n```gjs {data-filename=\"app/components/developer-details.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class DeveloperDetails extends Component {\n  @tracked developer = {\n    name: 'Shelly Sails',\n    age: 42,\n  };\n\n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n\nThe same pattern works with a `Map`:\n\n```gjs {data-filename=\"app/components/developer-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperMap extends Component {\n  map = new Map([\n    ['name', 'Shelly Sails'],\n    ['age', 42],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nWhen a `Map` uses object keys, you can pass `key=\"@identity\"` to explicitly\ntrack entries across re-renders using the JavaScript identity of each key:\n\n```gjs {data-filename=\"app/components/object-keyed-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class ObjectKeyedMap extends Component {\n  map = new Map([\n    [{ name: 'one' }, 'foo'],\n    [{ name: 'two' }, 'bar'],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map key=\"@identity\" as |key value|}}\n        <li>{{key.name}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\n`#each-in` is a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "each-in",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "2.1.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 662,
+            "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```gjs\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.\n\nThe `element` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "element",
+            "params": [
+              {
+                "name": "tagName",
+                "description": "",
+                "type": "String"
+              }
+            ],
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 718,
+            "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nThe `eq` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "eq",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Unknown"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 493,
+            "description": "`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```gjs\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```gjs {data-filename=\"app/components/items-listing.gjs\"}\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```gjs {data-filename=\"app/components/items-list.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take a look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\nreceive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\nwill receive the `item` from the loop as its first argument and the\nstring `'foo'` as its second argument.\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\nThe `fn` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "fn",
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.11.0",
+            "static": 1,
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 562,
+            "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```gjs\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nThe `gt` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "gt",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 587,
+            "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nThe `gte` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "gte",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1109,
+            "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```\n\n`has-block` is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "has-block",
+            "params": [
+              {
+                "name": "blockName",
+                "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+                "type": "String"
+              }
+            ],
+            "return": {
+              "description": "`true` if the component was invoked with a block",
+              "type": "Boolean"
+            },
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1150,
+            "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\n  Hi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
+            "itemtype": "method",
+            "name": "has-block-params",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "blockName",
+                "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+                "type": "String"
+              }
+            ],
+            "return": {
+              "description": "`true` if the component was invoked with block params",
+              "type": "Boolean"
+            },
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 349,
+            "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```\n\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\nThe `hash` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "hash",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
+            "noimport": "",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Object"
+              }
+            ],
+            "return": {
+              "description": "Hash",
+              "type": "Object"
+            },
+            "since": "2.3.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1328,
+            "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
             "itemtype": "method",
-            "name": "capabilities",
+            "name": "helper",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.27.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1368,
+            "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "if",
             "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1714,
+            "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "in-element",
             "params": [
               {
-                "name": "managerApiVersion",
-                "description": "The version of capabilities that are being used",
-                "type": "String"
+                "name": "destinationElement",
+                "description": "the DOM element to render into. It must exist at the time\n of rendering.",
+                "type": "Element"
               },
               {
-                "name": "options",
-                "description": "The capabilities values"
+                "name": "insertBefore",
+                "description": "named argument, by default the DOM element's content is replaced when used as\n `destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\n append the block content to the end of any existing content. Any other value than\n `null` is currently not supported.",
+                "type": "Boolean"
+              }
+            ],
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1674,
+            "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "let",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1596,
+            "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```\n \n`log` is built-in as a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "log",
+            "noimport": "",
+            "static": 1,
+            "params": [
+              {
+                "name": "params",
+                "description": "",
+                "type": "Array"
+              }
+            ],
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 612,
+            "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```gjs\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nThe `lt` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "lt",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
               }
             ],
             "return": {
-              "description": "The capabilities object instance",
-              "type": "Capabilities"
+              "description": "",
+              "type": "Boolean"
             },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
             "access": "public",
             "tagname": "",
-            "class": "@ember/helper",
+            "class": "Keywords",
             "module": "@ember/helper"
           },
           {
             "file": "packages/@ember/helper/index.ts",
-            "line": 274,
-            "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```js\n// app/components/data-loader.js\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n```\n```js\n{{this.value}}\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
+            "line": 637,
+            "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nThe `lte` helper is available as a keyword and does not need to be imported.",
             "itemtype": "method",
-            "name": "invokeHelper",
+            "name": "lte",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Number"
+              },
+              {
+                "name": "right",
+                "description": "",
+                "type": "Number"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "since": "7.1.0",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1614,
+            "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.\n\n`modifier` is built-in as a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "modifier",
             "static": 1,
+            "access": "public",
+            "tagname": "",
+            "since": "3.27.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
+            "line": 17,
+            "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```hbs\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "mount",
             "params": [
               {
-                "name": "context",
-                "description": "The parent context of the helper",
-                "type": "Object"
+                "name": "name",
+                "description": "Name of the engine to mount.",
+                "type": "String"
               },
               {
-                "name": "definition",
-                "description": "The helper definition",
-                "type": "Object"
+                "name": "model",
+                "description": "Object that will be set as\n                        the model of the engine.",
+                "type": "Object",
+                "optional": true
+              }
+            ],
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
+            "line": 9,
+            "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```gjs {data-filename=\"app/components/my-child.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
+            "itemtype": "method",
+            "name": "mut",
+            "params": [
+              {
+                "name": "attr",
+                "description": "the \"two-way\" attribute that can be modified.",
+                "type": "Object",
+                "optional": true
+              }
+            ],
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 743,
+            "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nThe `neq` helper is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "neq",
+            "params": [
+              {
+                "name": "left",
+                "description": "",
+                "type": "Unknown"
               },
               {
-                "name": "computeArgs",
-                "description": "An optional function that produces args",
-                "type": "Function"
+                "name": "right",
+                "description": "",
+                "type": "Unknown"
               }
             ],
             "return": {
-              "description": ""
+              "description": "",
+              "type": "Boolean"
             },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
             "access": "public",
             "tagname": "",
-            "class": "@ember/helper",
+            "class": "Keywords",
             "module": "@ember/helper"
           },
           {
             "file": "packages/@ember/helper/index.ts",
-            "line": 80,
-            "description": "Sets the helper manager for an object or function.\n\n```js\nsetHelperManager((owner) => new ClassHelperManager(owner), Helper)\n```\n\nWhen a value is used as a helper in a template, the helper manager is looked up\non the object by walking up its prototype chain and finding the first helper\nmanager. This manager then receives the value and can create and manage an\ninstance of a helper from it. This provides a layer of indirection that allows\nusers to design high-level helper APIs, without Ember needing to worry about the\ndetails. High-level APIs can be experimented with and iterated on while the\ncore of Ember helpers remains stable, and new APIs can be introduced gradually\nover time to existing code bases.\n\n`setHelperManager` receives two arguments:\n\n1. A factory function, which receives the `owner` and returns an instance of a\n  helper manager.\n2. A helper definition, which is the object or function to associate the factory function with.\n\nThe first time the object is looked up, the factory function will be called to\ncreate the helper manager. It will be cached, and in subsequent lookups the\ncached helper manager will be used instead.\n\nOnly one helper manager is guaranteed to exist per `owner` and per usage of\n`setHelperManager`, so many helpers will end up using the same instance of the\nhelper manager. As such, you should only store state that is related to the\nmanager itself. If you want to store state specific to a particular helper\ndefinition, you should assign a unique helper manager to that helper. In\ngeneral, most managers should either be stateless, or only have the `owner` they\nwere created with as state.\n\nHelper managers must fulfill the following interface (This example uses\n[TypeScript interfaces](https://www.typescriptlang.org/docs/handbook/interfaces.html)\nfor precision, you do not need to write helper managers using TypeScript):\n\n```ts\ninterface HelperManager<HelperStateBucket> {\n  capabilities: HelperCapabilities;\n\n  createHelper(definition: HelperDefinition, args: TemplateArgs): HelperStateBucket;\n\n  getValue?(bucket: HelperStateBucket): unknown;\n\n  runEffect?(bucket: HelperStateBucket): void;\n\n  getDestroyable?(bucket: HelperStateBucket): object;\n}\n```\n\nThe capabilities property _must_ be provided using the `capabilities()` function\nimported from the same module as `setHelperManager`:\n\n```js\nimport { capabilities } from '@ember/helper';\n\nclass MyHelperManager {\n  capabilities = capabilities('3.21.0', { hasValue: true });\n\n  // ...snip...\n}\n```\n\nBelow is a description of each of the methods on the interface and their\nfunctions.\n\n#### `createHelper`\n\n`createHelper` is a required hook on the HelperManager interface. The hook is\npassed the definition of the helper that is currently being created, and is\nexpected to return a _state bucket_. This state bucket is what represents the\ncurrent state of the helper, and will be passed to the other lifecycle hooks at\nappropriate times. It is not necessarily related to the definition of the\nhelper itself - for instance, you could return an object _containing_ an\ninstance of the helper:\n\n```js\nclass MyManager {\n  createHelper(Definition, args) {\n    return {\n      instance: new Definition(args);\n    };\n  }\n}\n```\n\nThis allows the manager to store metadata that it doesn't want to expose to the\nuser.\n\nThis hook is _not_ autotracked - changes to tracked values used within this hook\nwill _not_ result in a call to any of the other lifecycle hooks. This is because\nit is unclear what should happen if it invalidates, and rather than make a\ndecision at this point, the initial API is aiming to allow as much expressivity\nas possible. This could change in the future with changes to capabilities and\ntheir behaviors.\n\nIf users do want to autotrack some values used during construction, they can\neither create the instance of the helper in `runEffect` or `getValue`, or they\ncan use the `cache` API to autotrack the `createHelper` hook themselves. This\nprovides maximum flexibility and expressiveness to manager authors.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called as discovered during DOM construction\n- called in definition order in the template\n\n#### `getValue`\n\n`getValue` is an optional hook that should return the value of the helper. This\nis the value that is returned from the helper and passed into the template.\n\nThis hook is called when the value is requested from the helper (e.g. when the\ntemplate is rendering and the helper value is needed). The hook is autotracked,\nand will rerun whenever any tracked values used inside of it are updated.\nOtherwise it does not rerun.\n\n> Note: This means that arguments which are not _consumed_ within the hook will\n> not trigger updates.\n\nThis hook is only called for helpers with the `hasValue` capability enabled.\nThis hook has the following timing semantics:\n\n**Always**\n- called the first time the helper value is requested\n- called after autotracked state has changed\n\n**Never**\n- called if the `hasValue` capability is disabled\n\n#### `runEffect`\n\n`runEffect` is an optional hook that should run the effect that the helper is\napplying, setting it up or updating it.\n\nThis hook is scheduled to be called some time after render and prior to paint.\nThere is not a guaranteed, 1-to-1 relationship between a render pass and this\nhook firing. For instance, multiple render passes could occur, and the hook may\nonly trigger once. It may also never trigger if it was dirtied in one render\npass and then destroyed in the next.\n\nThe hook is autotracked, and will rerun whenever any tracked values used inside\nof it are updated. Otherwise it does not rerun.\n\nThe hook is also run during a time period where state mutations are _disabled_\nin Ember. Any tracked state mutation will throw an error during this time,\nincluding changes to tracked properties, changes made using `set`, updates\nto computed properties, etc. This is meant to prevent infinite rerenders and\nother antipatterns.\n\nThis hook is only called for helpers with the `hasScheduledEffect` capability\nenabled. This hook is also not called in SSR currently, though this could be\nadded as a capability in the future. It has the following timing semantics:\n\n**Always**\n- called after the helper was first created, if the helper has not been\n  destroyed since creation\n- called after autotracked state has changed, if the helper has not been\n  destroyed during render\n\n**Never**\n- called if the `hasScheduledEffect` capability is disabled\n- called in SSR\n\n#### `getDestroyable`\n\n`getDestroyable` is an optional hook that users can use to register a\ndestroyable object for the helper. This destroyable will be registered to the\ncontaining block or template parent, and will be destroyed when it is destroyed.\nSee the [Destroyables RFC](https://github.com/emberjs/rfcs/blob/master/text/0580-destroyables.md)\nfor more details.\n\n`getDestroyable` is only called if the `hasDestroyable` capability is enabled.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called immediately after the `createHelper` hook is called\n\n**Never**\n- called if the `hasDestroyable` capability is disabled",
+            "line": 819,
+            "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```gjs\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
             "itemtype": "method",
-            "name": "setHelperManager",
+            "name": "not",
+            "params": [
+              {
+                "name": "value",
+                "description": "The value to negate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "",
+              "type": "Boolean"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
+            "line": 253,
+            "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```hbs\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!\n\nThe `on` modifier is a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "on",
             "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "since": "3.11.0",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 793,
+            "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
+            "itemtype": "method",
+            "name": "or",
             "params": [
               {
-                "name": "factory",
-                "description": "A factory function which receives an optional owner, and returns a helper manager",
-                "type": "Function"
-              },
+                "name": "args",
+                "description": "Two or more values to evaluate",
+                "type": "Unknown"
+              }
+            ],
+            "return": {
+              "description": "The first truthy value or the last value",
+              "type": "Unknown"
+            },
+            "noimport": "",
+            "static": 1,
+            "since": "7.1.0",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
+            "line": 32,
+            "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "outlet",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
+            "line": 9,
+            "description": "The `readonly` helper let's you specify that a binding is one-way only,\ninstead of two-way.\n\nThis is a vestigial helper from the days of `@ember/component` and does not apply to\ncomponents extending from `@glimmer/component`.\n  \nWhen you pass a `readonly` binding from an outer context (e.g. parent component),\nto to an inner context (e.g. child component), you are saying that changing that\nproperty in the inner context does not change the value in the outer context.\n\nTo specify that a binding is read-only, when invoking the child `Component`:\n\n```app/components/my-parent.js\nexport default class MyParent extends Component {\n  totalClicks = 3;\n}\n```\n\nNow, when you update `childClickCount`:\n\n```app/components/my-child.js\nexport default class MyChild extends Component {\n  click() {\n    this.incrementProperty('childClickCount');\n  }\n}\n```\n\nThe value updates in the child component, but not the parent component:\n\n```app/templates/components/my-child.hbs\n{{log childClickCount}} //-> 4\n```\n\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n<MyChild @childClickCount={{readonly totalClicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n{{my-child childClickCount=(readonly totalClicks)}}\n```\n\n### Objects and Arrays\n\nWhen passing a property that is a complex object (e.g. object, array) instead of a primitive object (e.g. number, string),\nonly the reference to the object is protected using the readonly helper.\nThis means that you can change properties of the object both on the parent component, as well as the child component.\nThe `readonly` binding behaves similar to the `const` keyword in JavaScript.\n\nLet's look at an example:\n\nFirst let's set up the parent component:\n\n```app/components/my-parent.js\nimport Component from '@ember/component';\n\nexport default class MyParent extends Component {\n  clicks: null,\n\n  init() {\n    this._super(...arguments);\n    this.set('clicks', { total: 3 });\n  }\n}\n```\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n<MyChild @childClicks={{readonly clicks}} />\n```\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n{{my-child childClicks=(readonly clicks)}}\n```\n\nNow, if you update the `total` property of `childClicks`:\n\n```app/components/my-child.js\nimport Component from '@ember/component';\n\nexport default class MyChild extends Component {\n  click() {\n    this.get('clicks').incrementProperty('total');\n  }\n}\n```\n\nYou will see the following happen:\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n<MyChild @childClicks={{readonly clicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n{{my-child childClicks=(readonly clicks)}}\n```\n\n```app/templates/components/my-child.hbs\n{{log childClicks.total}} //-> 4\n```",
+            "itemtype": "method",
+            "name": "readonly",
+            "params": [
               {
-                "name": "definition",
-                "description": "The definition to associate the manager factory with",
-                "type": "Object"
+                "name": "attr",
+                "description": "the read-only attribute.",
+                "type": "Object",
+                "optional": true
+              }
+            ],
+            "noimport": "",
+            "static": 1,
+            "access": "private",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
+            "line": 10,
+            "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.\n \n `unbound` is a template keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "unbound",
+            "static": 1,
+            "noimport": "",
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1484,
+            "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```gjs {data-filename=\"app/components/logged-in.gjs\"}\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
+            "itemtype": "method",
+            "name": "unless",
+            "noimport": "",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "Keywords",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 844,
+            "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components, `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally, you can `yield` properties into the context for use by the consumer:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```gjs {data-filename=\"app/components/date-ranges.gjs\"}\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner/subtitle.gjs\"}\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```gjs {data-filename=\"app/components/banner/title.gjs\"}\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```\n\n`yield` is available as a keyword and does not need to be imported.",
+            "itemtype": "method",
+            "name": "yield",
+            "params": [
+              {
+                "name": "options",
+                "description": "",
+                "type": "Hash"
               }
             ],
             "return": {
-              "description": "The definition passed into setHelperManager",
-              "type": "Object"
+              "description": "HTML string",
+              "type": "String"
             },
+            "static": 1,
+            "noimport": "",
             "access": "public",
             "tagname": "",
-            "class": "@ember/helper",
+            "class": "Keywords",
             "module": "@ember/helper"
           }
-        ]
-      },
-      "allstaticfunctions": {
+        ],
         "@ember/helper": [
           {
             "file": "packages/@ember/helper/index.ts",
@@ -132,15 +1550,44 @@
               "description": "The capabilities object instance",
               "type": "Capabilities"
             },
+            "since": "3.23.0",
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 414,
+            "description": "The `{{concat}}` helper Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\n import { concat } from '@ember/helper';\n\n <template>\n   {{yield (concat firstName \" \" lastName)}}\n\n   {{! would yield name=\"<first name value> <last name value>\" to the component}}\n </template>\n ```\n\n or for angle bracket invocation, you actually don't need concat at all:\n\n ```handlebars\n <SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n ```",
+            "itemtype": "method",
+            "name": "concat",
+            "exampleimport": "import { concat } from '@ember/helper';",
             "access": "public",
             "tagname": "",
+            "static": 1,
+            "since": "1.13.0",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 445,
+            "description": "The `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
+            "itemtype": "method",
+            "name": "get",
+            "since": "2.1.0",
+            "exampleimport": "import { get } from '@ember/helper';",
+            "access": "public",
+            "tagname": "",
+            "static": 1,
             "class": "@ember/helper",
             "module": "@ember/helper"
           },
           {
             "file": "packages/@ember/helper/index.ts",
-            "line": 274,
-            "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```js\n// app/components/data-loader.js\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n```\n```js\n{{this.value}}\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
+            "line": 276,
+            "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```gjs {data-filename=\"app/components/data-loader.js\"}\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n\n<template>\n  {{this.value}}\n</template>\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
             "itemtype": "method",
             "name": "invokeHelper",
             "static": 1,
@@ -164,6 +1611,7 @@
             "return": {
               "description": ""
             },
+            "since": "3.23.0",
             "access": "public",
             "tagname": "",
             "class": "@ember/helper",
@@ -171,7 +1619,7 @@
           },
           {
             "file": "packages/@ember/helper/index.ts",
-            "line": 80,
+            "line": 81,
             "description": "Sets the helper manager for an object or function.\n\n```js\nsetHelperManager((owner) => new ClassHelperManager(owner), Helper)\n```\n\nWhen a value is used as a helper in a template, the helper manager is looked up\non the object by walking up its prototype chain and finding the first helper\nmanager. This manager then receives the value and can create and manage an\ninstance of a helper from it. This provides a layer of indirection that allows\nusers to design high-level helper APIs, without Ember needing to worry about the\ndetails. High-level APIs can be experimented with and iterated on while the\ncore of Ember helpers remains stable, and new APIs can be introduced gradually\nover time to existing code bases.\n\n`setHelperManager` receives two arguments:\n\n1. A factory function, which receives the `owner` and returns an instance of a\n  helper manager.\n2. A helper definition, which is the object or function to associate the factory function with.\n\nThe first time the object is looked up, the factory function will be called to\ncreate the helper manager. It will be cached, and in subsequent lookups the\ncached helper manager will be used instead.\n\nOnly one helper manager is guaranteed to exist per `owner` and per usage of\n`setHelperManager`, so many helpers will end up using the same instance of the\nhelper manager. As such, you should only store state that is related to the\nmanager itself. If you want to store state specific to a particular helper\ndefinition, you should assign a unique helper manager to that helper. In\ngeneral, most managers should either be stateless, or only have the `owner` they\nwere created with as state.\n\nHelper managers must fulfill the following interface (This example uses\n[TypeScript interfaces](https://www.typescriptlang.org/docs/handbook/interfaces.html)\nfor precision, you do not need to write helper managers using TypeScript):\n\n```ts\ninterface HelperManager<HelperStateBucket> {\n  capabilities: HelperCapabilities;\n\n  createHelper(definition: HelperDefinition, args: TemplateArgs): HelperStateBucket;\n\n  getValue?(bucket: HelperStateBucket): unknown;\n\n  runEffect?(bucket: HelperStateBucket): void;\n\n  getDestroyable?(bucket: HelperStateBucket): object;\n}\n```\n\nThe capabilities property _must_ be provided using the `capabilities()` function\nimported from the same module as `setHelperManager`:\n\n```js\nimport { capabilities } from '@ember/helper';\n\nclass MyHelperManager {\n  capabilities = capabilities('3.21.0', { hasValue: true });\n\n  // ...snip...\n}\n```\n\nBelow is a description of each of the methods on the interface and their\nfunctions.\n\n#### `createHelper`\n\n`createHelper` is a required hook on the HelperManager interface. The hook is\npassed the definition of the helper that is currently being created, and is\nexpected to return a _state bucket_. This state bucket is what represents the\ncurrent state of the helper, and will be passed to the other lifecycle hooks at\nappropriate times. It is not necessarily related to the definition of the\nhelper itself - for instance, you could return an object _containing_ an\ninstance of the helper:\n\n```js\nclass MyManager {\n  createHelper(Definition, args) {\n    return {\n      instance: new Definition(args);\n    };\n  }\n}\n```\n\nThis allows the manager to store metadata that it doesn't want to expose to the\nuser.\n\nThis hook is _not_ autotracked - changes to tracked values used within this hook\nwill _not_ result in a call to any of the other lifecycle hooks. This is because\nit is unclear what should happen if it invalidates, and rather than make a\ndecision at this point, the initial API is aiming to allow as much expressivity\nas possible. This could change in the future with changes to capabilities and\ntheir behaviors.\n\nIf users do want to autotrack some values used during construction, they can\neither create the instance of the helper in `runEffect` or `getValue`, or they\ncan use the `cache` API to autotrack the `createHelper` hook themselves. This\nprovides maximum flexibility and expressiveness to manager authors.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called as discovered during DOM construction\n- called in definition order in the template\n\n#### `getValue`\n\n`getValue` is an optional hook that should return the value of the helper. This\nis the value that is returned from the helper and passed into the template.\n\nThis hook is called when the value is requested from the helper (e.g. when the\ntemplate is rendering and the helper value is needed). The hook is autotracked,\nand will rerun whenever any tracked values used inside of it are updated.\nOtherwise it does not rerun.\n\n> Note: This means that arguments which are not _consumed_ within the hook will\n> not trigger updates.\n\nThis hook is only called for helpers with the `hasValue` capability enabled.\nThis hook has the following timing semantics:\n\n**Always**\n- called the first time the helper value is requested\n- called after autotracked state has changed\n\n**Never**\n- called if the `hasValue` capability is disabled\n\n#### `runEffect`\n\n`runEffect` is an optional hook that should run the effect that the helper is\napplying, setting it up or updating it.\n\nThis hook is scheduled to be called some time after render and prior to paint.\nThere is not a guaranteed, 1-to-1 relationship between a render pass and this\nhook firing. For instance, multiple render passes could occur, and the hook may\nonly trigger once. It may also never trigger if it was dirtied in one render\npass and then destroyed in the next.\n\nThe hook is autotracked, and will rerun whenever any tracked values used inside\nof it are updated. Otherwise it does not rerun.\n\nThe hook is also run during a time period where state mutations are _disabled_\nin Ember. Any tracked state mutation will throw an error during this time,\nincluding changes to tracked properties, changes made using `set`, updates\nto computed properties, etc. This is meant to prevent infinite rerenders and\nother antipatterns.\n\nThis hook is only called for helpers with the `hasScheduledEffect` capability\nenabled. This hook is also not called in SSR currently, though this could be\nadded as a capability in the future. It has the following timing semantics:\n\n**Always**\n- called after the helper was first created, if the helper has not been\n  destroyed since creation\n- called after autotracked state has changed, if the helper has not been\n  destroyed during render\n\n**Never**\n- called if the `hasScheduledEffect` capability is disabled\n- called in SSR\n\n#### `getDestroyable`\n\n`getDestroyable` is an optional hook that users can use to register a\ndestroyable object for the helper. This destroyable will be registered to the\ncontaining block or template parent, and will be destroyed when it is destroyed.\nSee the [Destroyables RFC](https://github.com/emberjs/rfcs/blob/master/text/0580-destroyables.md)\nfor more details.\n\n`getDestroyable` is only called if the `hasDestroyable` capability is enabled.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called immediately after the `createHelper` hook is called\n\n**Never**\n- called if the `hasDestroyable` capability is disabled",
             "itemtype": "method",
             "name": "setHelperManager",
@@ -192,11 +1640,47 @@
               "description": "The definition passed into setHelperManager",
               "type": "Object"
             },
+            "since": "3.23.0",
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/helper",
+            "module": "@ember/helper"
+          },
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 690,
+            "description": "Use the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```gjs\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
+            "itemtype": "method",
+            "name": "uniqueId",
             "access": "public",
             "tagname": "",
+            "static": 1,
+            "exampleimport": "import { uniqueId } from '@ember/helper';",
+            "since": "4.4.0",
             "class": "@ember/helper",
             "module": "@ember/helper"
           }
+        ],
+        "External": [
+          {
+            "file": "packages/@ember/helper/index.ts",
+            "line": 1654,
+            "description": "`pageTitle` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport { pageTitle } from 'ember-page-title';\n  \n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
+            "itemtype": "method",
+            "name": "pageTitle",
+            "params": [
+              {
+                "name": "param",
+                "description": "",
+                "type": "String"
+              }
+            ],
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "External",
+            "module": "@ember/helper"
+          }
         ]
       },
       "version": "7.1.0"
diff --git a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/object.json b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/object.json
index e30d22a7d..00575e816 100644
--- a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/object.json
+++ b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/object.json
@@ -1359,7 +1359,7 @@
           {
             "file": "packages/@ember/object/compat.ts",
             "line": 45,
-            "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nClassic Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport EmberObject, { computed, observer, set } from '@ember/object';\n\nconst Person = EmberObject.extend({\n  firstName: tracked(),\n  lastName: tracked(),\n\n  fullName: dependentKeyCompat(function() {\n    return `${this.firstName} ${this.lastName}`;\n  }),\n});\n\nconst Profile = EmberObject.extend({\n  person: null,\n\n  helloMessage: computed('person.fullName', function() {\n    return `Hello, ${this.person.fullName}!`;\n  }),\n\n  onNameUpdated: observer('person.fullName', function() {\n    console.log('person name updated!');\n  }),\n});\n```\n\n`dependentKeyCompat()` can receive a getter function or an object containing\n`get`/`set` methods when used in classic classes, like computed properties.\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
+            "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
             "access": "public",
             "tagname": "",
             "itemtype": "method",
@@ -2767,7 +2767,7 @@
           {
             "file": "packages/@ember/object/compat.ts",
             "line": 45,
-            "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nClassic Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport EmberObject, { computed, observer, set } from '@ember/object';\n\nconst Person = EmberObject.extend({\n  firstName: tracked(),\n  lastName: tracked(),\n\n  fullName: dependentKeyCompat(function() {\n    return `${this.firstName} ${this.lastName}`;\n  }),\n});\n\nconst Profile = EmberObject.extend({\n  person: null,\n\n  helloMessage: computed('person.fullName', function() {\n    return `Hello, ${this.person.fullName}!`;\n  }),\n\n  onNameUpdated: observer('person.fullName', function() {\n    console.log('person name updated!');\n  }),\n});\n```\n\n`dependentKeyCompat()` can receive a getter function or an object containing\n`get`/`set` methods when used in classic classes, like computed properties.\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
+            "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
             "access": "public",
             "tagname": "",
             "itemtype": "method",
diff --git a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/routing.json b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/routing.json
index bd8bfb0ff..41887b302 100644
--- a/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/routing.json
+++ b/json-docs/ember/7.1.0/modules/ember-7.1.0-@ember/routing.json
@@ -7,7 +7,6 @@
       "submodules": {},
       "elements": {},
       "fors": {
-        "Ember.Templates.helpers": 1,
         "@ember/routing": 1,
         "Ember": 1
       },
@@ -18,8 +17,38 @@
       "parent": null,
       "publicclasses": [],
       "privateclasses": [],
-      "staticfunctions": {},
-      "allstaticfunctions": {},
+      "staticfunctions": {
+        "@ember/routing": [
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
+            "line": 52,
+            "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```gjs\nimport { LinkTo } from '@ember/routing';\n  \n<template>\n  <LinkTo @route='photoGallery'>\n    Great Hamster Photos\n  </LinkTo>\n</template>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
+            "itemtype": "method",
+            "name": "LinkTo",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/routing",
+            "module": "@ember/routing"
+          }
+        ]
+      },
+      "allstaticfunctions": {
+        "@ember/routing": [
+          {
+            "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
+            "line": 52,
+            "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```gjs\nimport { LinkTo } from '@ember/routing';\n  \n<template>\n  <LinkTo @route='photoGallery'>\n    Great Hamster Photos\n  </LinkTo>\n</template>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
+            "itemtype": "method",
+            "name": "LinkTo",
+            "static": 1,
+            "access": "public",
+            "tagname": "",
+            "class": "@ember/routing",
+            "module": "@ember/routing"
+          }
+        ]
+      },
       "version": "7.1.0"
     },
     "relationships": {
diff --git a/json-docs/ember/7.1.0/modules/ember-7.1.0-ember.json b/json-docs/ember/7.1.0/modules/ember-7.1.0-ember.json
index 343e00220..05c2f1786 100644
--- a/json-docs/ember/7.1.0/modules/ember-7.1.0-ember.json
+++ b/json-docs/ember/7.1.0/modules/ember-7.1.0-ember.json
@@ -7,8 +7,6 @@
       "submodules": {},
       "elements": {},
       "fors": {
-        "@ember/helper": 1,
-        "Ember.Templates.helpers": 1,
         "Ember": 1,
         "@ember/object": 1
       },
diff --git a/json-docs/ember/7.1.0/project-versions/ember-7.1.0.json b/json-docs/ember/7.1.0/project-versions/ember-7.1.0.json
index 82808c2a2..03a7cba31 100644
--- a/json-docs/ember/7.1.0/project-versions/ember-7.1.0.json
+++ b/json-docs/ember/7.1.0/project-versions/ember-7.1.0.json
@@ -28,10 +28,6 @@
             "id": "ember-7.1.0-EmberENV",
             "type": "class"
           },
-          {
-            "id": "ember-7.1.0-Ember.Templates.helpers",
-            "type": "class"
-          },
           {
             "id": "ember-7.1.0-ComponentStateBucket",
             "type": "class"
@@ -52,6 +48,10 @@
             "id": "ember-7.1.0-Helper",
             "type": "class"
           },
+          {
+            "id": "ember-7.1.0-Ember.Templates.helpers",
+            "type": "class"
+          },
           {
             "id": "ember-7.1.0-ComputedProperty",
             "type": "class"
@@ -690,10 +690,6 @@
             "id": "ember-7.1.0-EmberENV",
             "type": "class"
           },
-          {
-            "id": "ember-7.1.0-Ember.Templates.helpers",
-            "type": "class"
-          },
           {
             "id": "ember-7.1.0-TrustedHTML",
             "type": "class"
@@ -710,6 +706,10 @@
             "id": "ember-7.1.0-Helper",
             "type": "class"
           },
+          {
+            "id": "ember-7.1.0-Ember.Templates.helpers",
+            "type": "class"
+          },
           {
             "id": "ember-7.1.0-ComputedProperty",
             "type": "class"
diff --git a/rev-index/ember-7.1.0.json b/rev-index/ember-7.1.0.json
index 7ed4e0393..ccef17c33 100644
--- a/rev-index/ember-7.1.0.json
+++ b/rev-index/ember-7.1.0.json
@@ -1 +1 @@
-{"data":{"id":"ember-7.1.0","type":"project-version","attributes":{"version":"7.1.0"},"relationships":{"classes":{"data":[{"id":"ember-7.1.0-Promise","type":"class"},{"id":"ember-7.1.0-EventTarget","type":"class"},{"id":"ember-7.1.0-Container","type":"class"},{"id":"ember-7.1.0-Registry","type":"class"},{"id":"ember-7.1.0-EmberENV","type":"class"},{"id":"ember-7.1.0-Ember.Templates.helpers","type":"class"},{"id":"ember-7.1.0-ComponentStateBucket","type":"class"},{"id":"ember-7.1.0-TrustedHTML","type":"class"},{"id":"ember-7.1.0-SafeString","type":"class"},{"id":"ember-7.1.0-Component","type":"class"},{"id":"ember-7.1.0-Helper","type":"class"},{"id":"ember-7.1.0-ComputedProperty","type":"class"},{"id":"ember-7.1.0-Descriptor","type":"class"},{"id":"ember-7.1.0-Ember.InjectedProperty","type":"class"},{"id":"ember-7.1.0-Libraries","type":"class"},{"id":"ember-7.1.0-FullName","type":"class"},{"id":"ember-7.1.0-BasicRegistry","type":"class"},{"id":"ember-7.1.0-BasicContainer","type":"class"},{"id":"ember-7.1.0-Owner","type":"class"},{"id":"ember-7.1.0-RegisterOptions","type":"class"},{"id":"ember-7.1.0-Factory","type":"class"},{"id":"ember-7.1.0-FactoryManager","type":"class"},{"id":"ember-7.1.0-Resolver","type":"class"},{"id":"ember-7.1.0-InternalFactory","type":"class"},{"id":"ember-7.1.0-ContainerProxy","type":"class"},{"id":"ember-7.1.0-RegistryProxy","type":"class"},{"id":"ember-7.1.0-Ember.ProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.ActionHandler","type":"class"},{"id":"ember-7.1.0-Ember.Comparable","type":"class"},{"id":"ember-7.1.0-ContainerProxyMixin","type":"class"},{"id":"ember-7.1.0-RegistryProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.TargetActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.String","type":"class"},{"id":"ember-7.1.0-Ember.ActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.EventDispatcher","type":"class"},{"id":"ember-7.1.0-Ember.CoreView","type":"class"},{"id":"ember-7.1.0-Application","type":"class"},{"id":"ember-7.1.0-ApplicationInstance","type":"class"},{"id":"ember-7.1.0-ApplicationInstance.BootOptions","type":"class"},{"id":"ember-7.1.0-Namespace","type":"class"},{"id":"ember-7.1.0-EmberArray","type":"class"},{"id":"ember-7.1.0-MutableArray","type":"class"},{"id":"ember-7.1.0-Ember.NativeArray","type":"class"},{"id":"ember-7.1.0-ArrayProxy","type":"class"},{"id":"ember-7.1.0-Ember.ControllerMixin","type":"class"},{"id":"ember-7.1.0-Ember.Controller","type":"class"},{"id":"ember-7.1.0-ContainerDebugAdapter","type":"class"},{"id":"ember-7.1.0-DataAdapter","type":"class"},{"id":"ember-7.1.0-Engine","type":"class"},{"id":"ember-7.1.0-EngineInstance","type":"class"},{"id":"ember-7.1.0-Enumerable","type":"class"},{"id":"ember-7.1.0-Ember.MutableEnumerable","type":"class"},{"id":"ember-7.1.0-CoreObject","type":"class"},{"id":"ember-7.1.0-Evented","type":"class"},{"id":"ember-7.1.0-EmberObject","type":"class"},{"id":"ember-7.1.0-Mixin","type":"class"},{"id":"ember-7.1.0-Observable","type":"class"},{"id":"ember-7.1.0-PromiseProxyMixin","type":"class"},{"id":"ember-7.1.0-ObjectProxy","type":"class"},{"id":"ember-7.1.0-Renderer","type":"class"},{"id":"ember-7.1.0-BucketCache","type":"class"},{"id":"ember-7.1.0-RoutingService","type":"class"},{"id":"ember-7.1.0-HashLocation","type":"class"},{"id":"ember-7.1.0-HistoryLocation","type":"class"},{"id":"ember-7.1.0-Location","type":"class"},{"id":"ember-7.1.0-NoneLocation","type":"class"},{"id":"ember-7.1.0-RouteInfo","type":"class"},{"id":"ember-7.1.0-RouteInfoWithAttributes","type":"class"},{"id":"ember-7.1.0-Route","type":"class"},{"id":"ember-7.1.0-RouterService","type":"class"},{"id":"ember-7.1.0-EmberRouter","type":"class"},{"id":"ember-7.1.0-Transition","type":"class"},{"id":"ember-7.1.0-Service","type":"class"},{"id":"ember-7.1.0-AssertAgainstAttrs","type":"class"},{"id":"ember-7.1.0-AssertAgainstNamedOutlets","type":"class"},{"id":"ember-7.1.0-TransformActionSyntax","type":"class"},{"id":"ember-7.1.0-TransformHasBlockSyntax","type":"class"},{"id":"ember-7.1.0-TransformInElement","type":"class"},{"id":"ember-7.1.0-TransformResolutions","type":"class"},{"id":"ember-7.1.0-TestAdapter","type":"class"},{"id":"ember-7.1.0-Ember.Test","type":"class"}]},"namespaces":{"data":[{"id":"ember-7.1.0-FEATURES","type":"namespace"},{"id":"ember-7.1.0-Instrumentation","type":"namespace"}]},"modules":{"data":[{"id":"ember-7.1.0-rsvp","type":"module"},{"id":"ember-7.1.0-@ember/component","type":"module"},{"id":"ember-7.1.0-@ember/routing","type":"module"},{"id":"ember-7.1.0-ember","type":"module"},{"id":"ember-7.1.0-@ember/helper","type":"module"},{"id":"ember-7.1.0-@ember/template","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking","type":"module"},{"id":"ember-7.1.0-@ember/renderer","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking/primitives/cache","type":"module"},{"id":"ember-7.1.0-@ember/object","type":"module"},{"id":"ember-7.1.0-@ember/owner","type":"module"},{"id":"ember-7.1.0-@ember/utils","type":"module"},{"id":"ember-7.1.0-@ember/application","type":"module"},{"id":"ember-7.1.0-@ember/application/namespace","type":"module"},{"id":"ember-7.1.0-@ember/array","type":"module"},{"id":"ember-7.1.0-@ember/array/proxy","type":"module"},{"id":"ember-7.1.0-@ember/canary-features","type":"module"},{"id":"ember-7.1.0-@ember/component/template-only","type":"module"},{"id":"ember-7.1.0-@ember/controller","type":"module"},{"id":"ember-7.1.0-@ember/debug","type":"module"},{"id":"ember-7.1.0-@ember/debug/container-debug-adapter","type":"module"},{"id":"ember-7.1.0-@ember/debug/data-adapter","type":"module"},{"id":"ember-7.1.0-@ember/destroyable","type":"module"},{"id":"ember-7.1.0-@ember/engine","type":"module"},{"id":"ember-7.1.0-@ember/enumerable","type":"module"},{"id":"ember-7.1.0-@ember/instrumentation","type":"module"},{"id":"ember-7.1.0-@ember/object/core","type":"module"},{"id":"ember-7.1.0-@ember/object/evented","type":"module"},{"id":"ember-7.1.0-@ember/object/mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/observable","type":"module"},{"id":"ember-7.1.0-@ember/object/promise-proxy-mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/proxy","type":"module"},{"id":"ember-7.1.0-@ember/reactive/collections","type":"module"},{"id":"ember-7.1.0-@ember/reactive","type":"module"},{"id":"ember-7.1.0-@ember/routing/hash-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/history-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/location","type":"module"},{"id":"ember-7.1.0-@ember/routing/none-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/route-info","type":"module"},{"id":"ember-7.1.0-@ember/routing/route","type":"module"},{"id":"ember-7.1.0-@ember/routing/router-service","type":"module"},{"id":"ember-7.1.0-@ember/routing/router","type":"module"},{"id":"ember-7.1.0-@ember/routing/transition","type":"module"},{"id":"ember-7.1.0-@ember/runloop","type":"module"},{"id":"ember-7.1.0-@ember/service","type":"module"},{"id":"ember-7.1.0-@glimmer/component","type":"module"},{"id":"ember-7.1.0-@ember/test","type":"module"}]},"project":{"data":{"id":"ember","type":"project"}},"private-classes":{"data":[{"id":"ember-7.1.0-Container","type":"class"},{"id":"ember-7.1.0-Registry","type":"class"},{"id":"ember-7.1.0-ComponentStateBucket","type":"class"},{"id":"ember-7.1.0-Descriptor","type":"class"},{"id":"ember-7.1.0-Ember.InjectedProperty","type":"class"},{"id":"ember-7.1.0-Libraries","type":"class"},{"id":"ember-7.1.0-BasicRegistry","type":"class"},{"id":"ember-7.1.0-BasicContainer","type":"class"},{"id":"ember-7.1.0-InternalFactory","type":"class"},{"id":"ember-7.1.0-ContainerProxy","type":"class"},{"id":"ember-7.1.0-RegistryProxy","type":"class"},{"id":"ember-7.1.0-Ember.ProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.ActionHandler","type":"class"},{"id":"ember-7.1.0-Ember.Comparable","type":"class"},{"id":"ember-7.1.0-ContainerProxyMixin","type":"class"},{"id":"ember-7.1.0-RegistryProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.TargetActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.String","type":"class"},{"id":"ember-7.1.0-Ember.ActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.EventDispatcher","type":"class"},{"id":"ember-7.1.0-Ember.CoreView","type":"class"},{"id":"ember-7.1.0-Ember.ControllerMixin","type":"class"},{"id":"ember-7.1.0-Enumerable","type":"class"},{"id":"ember-7.1.0-Ember.MutableEnumerable","type":"class"},{"id":"ember-7.1.0-BucketCache","type":"class"},{"id":"ember-7.1.0-RoutingService","type":"class"},{"id":"ember-7.1.0-AssertAgainstAttrs","type":"class"},{"id":"ember-7.1.0-AssertAgainstNamedOutlets","type":"class"},{"id":"ember-7.1.0-TransformActionSyntax","type":"class"},{"id":"ember-7.1.0-TransformHasBlockSyntax","type":"class"},{"id":"ember-7.1.0-TransformInElement","type":"class"},{"id":"ember-7.1.0-TransformResolutions","type":"class"}]},"public-classes":{"data":[{"id":"ember-7.1.0-Promise","type":"class"},{"id":"ember-7.1.0-EventTarget","type":"class"},{"id":"ember-7.1.0-EmberENV","type":"class"},{"id":"ember-7.1.0-Ember.Templates.helpers","type":"class"},{"id":"ember-7.1.0-TrustedHTML","type":"class"},{"id":"ember-7.1.0-SafeString","type":"class"},{"id":"ember-7.1.0-Component","type":"class"},{"id":"ember-7.1.0-Helper","type":"class"},{"id":"ember-7.1.0-ComputedProperty","type":"class"},{"id":"ember-7.1.0-FullName","type":"class"},{"id":"ember-7.1.0-Owner","type":"class"},{"id":"ember-7.1.0-RegisterOptions","type":"class"},{"id":"ember-7.1.0-Factory","type":"class"},{"id":"ember-7.1.0-FactoryManager","type":"class"},{"id":"ember-7.1.0-Resolver","type":"class"},{"id":"ember-7.1.0-Application","type":"class"},{"id":"ember-7.1.0-ApplicationInstance","type":"class"},{"id":"ember-7.1.0-ApplicationInstance.BootOptions","type":"class"},{"id":"ember-7.1.0-Namespace","type":"class"},{"id":"ember-7.1.0-EmberArray","type":"class"},{"id":"ember-7.1.0-MutableArray","type":"class"},{"id":"ember-7.1.0-Ember.NativeArray","type":"class"},{"id":"ember-7.1.0-ArrayProxy","type":"class"},{"id":"ember-7.1.0-Ember.Controller","type":"class"},{"id":"ember-7.1.0-ContainerDebugAdapter","type":"class"},{"id":"ember-7.1.0-DataAdapter","type":"class"},{"id":"ember-7.1.0-Engine","type":"class"},{"id":"ember-7.1.0-EngineInstance","type":"class"},{"id":"ember-7.1.0-CoreObject","type":"class"},{"id":"ember-7.1.0-Evented","type":"class"},{"id":"ember-7.1.0-EmberObject","type":"class"},{"id":"ember-7.1.0-Mixin","type":"class"},{"id":"ember-7.1.0-Observable","type":"class"},{"id":"ember-7.1.0-PromiseProxyMixin","type":"class"},{"id":"ember-7.1.0-ObjectProxy","type":"class"},{"id":"ember-7.1.0-Renderer","type":"class"},{"id":"ember-7.1.0-HashLocation","type":"class"},{"id":"ember-7.1.0-HistoryLocation","type":"class"},{"id":"ember-7.1.0-Location","type":"class"},{"id":"ember-7.1.0-NoneLocation","type":"class"},{"id":"ember-7.1.0-RouteInfo","type":"class"},{"id":"ember-7.1.0-RouteInfoWithAttributes","type":"class"},{"id":"ember-7.1.0-Route","type":"class"},{"id":"ember-7.1.0-RouterService","type":"class"},{"id":"ember-7.1.0-EmberRouter","type":"class"},{"id":"ember-7.1.0-Transition","type":"class"},{"id":"ember-7.1.0-Service","type":"class"},{"id":"ember-7.1.0-TestAdapter","type":"class"},{"id":"ember-7.1.0-Ember.Test","type":"class"}]},"private-namespaces":{"data":[{"id":"ember-7.1.0-Instrumentation","type":"namespace"}]},"public-namespaces":{"data":[{"id":"ember-7.1.0-FEATURES","type":"namespace"}]},"private-modules":{"data":[{"id":"ember-7.1.0-ember","type":"module"},{"id":"ember-7.1.0-@ember/enumerable","type":"module"},{"id":"ember-7.1.0-@ember/instrumentation","type":"module"}]},"public-modules":{"data":[{"id":"ember-7.1.0-rsvp","type":"module"},{"id":"ember-7.1.0-@ember/component","type":"module"},{"id":"ember-7.1.0-@ember/routing","type":"module"},{"id":"ember-7.1.0-@ember/helper","type":"module"},{"id":"ember-7.1.0-@ember/template","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking","type":"module"},{"id":"ember-7.1.0-@ember/renderer","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking/primitives/cache","type":"module"},{"id":"ember-7.1.0-@ember/object","type":"module"},{"id":"ember-7.1.0-@ember/owner","type":"module"},{"id":"ember-7.1.0-@ember/utils","type":"module"},{"id":"ember-7.1.0-@ember/application","type":"module"},{"id":"ember-7.1.0-@ember/application/namespace","type":"module"},{"id":"ember-7.1.0-@ember/array","type":"module"},{"id":"ember-7.1.0-@ember/array/proxy","type":"module"},{"id":"ember-7.1.0-@ember/canary-features","type":"module"},{"id":"ember-7.1.0-@ember/component/template-only","type":"module"},{"id":"ember-7.1.0-@ember/controller","type":"module"},{"id":"ember-7.1.0-@ember/debug","type":"module"},{"id":"ember-7.1.0-@ember/debug/container-debug-adapter","type":"module"},{"id":"ember-7.1.0-@ember/debug/data-adapter","type":"module"},{"id":"ember-7.1.0-@ember/destroyable","type":"module"},{"id":"ember-7.1.0-@ember/engine","type":"module"},{"id":"ember-7.1.0-@ember/object/core","type":"module"},{"id":"ember-7.1.0-@ember/object/evented","type":"module"},{"id":"ember-7.1.0-@ember/object/mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/observable","type":"module"},{"id":"ember-7.1.0-@ember/object/promise-proxy-mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/proxy","type":"module"},{"id":"ember-7.1.0-@ember/reactive/collections","type":"module"},{"id":"ember-7.1.0-@ember/reactive","type":"module"},{"id":"ember-7.1.0-@ember/routing/hash-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/history-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/location","type":"module"},{"id":"ember-7.1.0-@ember/routing/none-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/route-info","type":"module"},{"id":"ember-7.1.0-@ember/routing/route","type":"module"},{"id":"ember-7.1.0-@ember/routing/router-service","type":"module"},{"id":"ember-7.1.0-@ember/routing/router","type":"module"},{"id":"ember-7.1.0-@ember/routing/transition","type":"module"},{"id":"ember-7.1.0-@ember/runloop","type":"module"},{"id":"ember-7.1.0-@ember/service","type":"module"},{"id":"ember-7.1.0-@glimmer/component","type":"module"},{"id":"ember-7.1.0-@ember/test","type":"module"}]}}},"meta":{"class":{"ember-7.1.0-Promise":"ember-7.1.0-Promise","ember-7.1.0-EventTarget":"ember-7.1.0-EventTarget","ember-7.1.0-Container":"ember-7.1.0-Container","ember-7.1.0-Registry":"ember-7.1.0-Registry","ember-7.1.0-EmberENV":"ember-7.1.0-EmberENV","ember-7.1.0-Ember.Templates.helpers":"ember-7.1.0-Ember.Templates.helpers","ember-7.1.0-ComponentStateBucket":"ember-7.1.0-ComponentStateBucket","ember-7.1.0-TrustedHTML":"ember-7.1.0-TrustedHTML","ember-7.1.0-SafeString":"ember-7.1.0-SafeString","ember-7.1.0-Component":"ember-7.1.0-Component","ember-7.1.0-Helper":"ember-7.1.0-Helper","ember-7.1.0-ComputedProperty":"ember-7.1.0-ComputedProperty","ember-7.1.0-Descriptor":"ember-7.1.0-Descriptor","ember-7.1.0-Ember.InjectedProperty":"ember-7.1.0-Ember.InjectedProperty","ember-7.1.0-Libraries":"ember-7.1.0-Libraries","ember-7.1.0-FullName":"ember-7.1.0-FullName","ember-7.1.0-BasicRegistry":"ember-7.1.0-BasicRegistry","ember-7.1.0-BasicContainer":"ember-7.1.0-BasicContainer","ember-7.1.0-Owner":"ember-7.1.0-Owner","ember-7.1.0-RegisterOptions":"ember-7.1.0-RegisterOptions","ember-7.1.0-Factory":"ember-7.1.0-Factory","ember-7.1.0-FactoryManager":"ember-7.1.0-FactoryManager","ember-7.1.0-Resolver":"ember-7.1.0-Resolver","ember-7.1.0-InternalFactory":"ember-7.1.0-InternalFactory","ember-7.1.0-ContainerProxy":"ember-7.1.0-ContainerProxy","ember-7.1.0-RegistryProxy":"ember-7.1.0-RegistryProxy","ember-7.1.0-Ember.ProxyMixin":"ember-7.1.0-Ember.ProxyMixin","ember-7.1.0-Ember.ActionHandler":"ember-7.1.0-Ember.ActionHandler","ember-7.1.0-Ember.Comparable":"ember-7.1.0-Ember.Comparable","ember-7.1.0-ContainerProxyMixin":"ember-7.1.0-ContainerProxyMixin","ember-7.1.0-RegistryProxyMixin":"ember-7.1.0-RegistryProxyMixin","ember-7.1.0-Ember.TargetActionSupport":"ember-7.1.0-Ember.TargetActionSupport","ember-7.1.0-Ember.String":"ember-7.1.0-Ember.String","ember-7.1.0-Ember.ActionSupport":"ember-7.1.0-Ember.ActionSupport","ember-7.1.0-Ember.EventDispatcher":"ember-7.1.0-Ember.EventDispatcher","ember-7.1.0-Ember.CoreView":"ember-7.1.0-Ember.CoreView","ember-7.1.0-Application":"ember-7.1.0-Application","ember-7.1.0-ApplicationInstance":"ember-7.1.0-ApplicationInstance","ember-7.1.0-ApplicationInstance.BootOptions":"ember-7.1.0-ApplicationInstance.BootOptions","ember-7.1.0-Namespace":"ember-7.1.0-Namespace","ember-7.1.0-EmberArray":"ember-7.1.0-EmberArray","ember-7.1.0-MutableArray":"ember-7.1.0-MutableArray","ember-7.1.0-Ember.NativeArray":"ember-7.1.0-Ember.NativeArray","ember-7.1.0-ArrayProxy":"ember-7.1.0-ArrayProxy","ember-7.1.0-Ember.ControllerMixin":"ember-7.1.0-Ember.ControllerMixin","ember-7.1.0-Ember.Controller":"ember-7.1.0-Ember.Controller","ember-7.1.0-ContainerDebugAdapter":"ember-7.1.0-ContainerDebugAdapter","ember-7.1.0-DataAdapter":"ember-7.1.0-DataAdapter","ember-7.1.0-Engine":"ember-7.1.0-Engine","ember-7.1.0-EngineInstance":"ember-7.1.0-EngineInstance","ember-7.1.0-Enumerable":"ember-7.1.0-Enumerable","ember-7.1.0-Ember.MutableEnumerable":"ember-7.1.0-Ember.MutableEnumerable","ember-7.1.0-CoreObject":"ember-7.1.0-CoreObject","ember-7.1.0-Evented":"ember-7.1.0-Evented","ember-7.1.0-EmberObject":"ember-7.1.0-EmberObject","ember-7.1.0-Mixin":"ember-7.1.0-Mixin","ember-7.1.0-Observable":"ember-7.1.0-Observable","ember-7.1.0-PromiseProxyMixin":"ember-7.1.0-PromiseProxyMixin","ember-7.1.0-ObjectProxy":"ember-7.1.0-ObjectProxy","ember-7.1.0-Renderer":"ember-7.1.0-Renderer","ember-7.1.0-BucketCache":"ember-7.1.0-BucketCache","ember-7.1.0-RoutingService":"ember-7.1.0-RoutingService","ember-7.1.0-HashLocation":"ember-7.1.0-HashLocation","ember-7.1.0-HistoryLocation":"ember-7.1.0-HistoryLocation","ember-7.1.0-Location":"ember-7.1.0-Location","ember-7.1.0-NoneLocation":"ember-7.1.0-NoneLocation","ember-7.1.0-RouteInfo":"ember-7.1.0-RouteInfo","ember-7.1.0-RouteInfoWithAttributes":"ember-7.1.0-RouteInfoWithAttributes","ember-7.1.0-Route":"ember-7.1.0-Route","ember-7.1.0-RouterService":"ember-7.1.0-RouterService","ember-7.1.0-EmberRouter":"ember-7.1.0-EmberRouter","ember-7.1.0-Transition":"ember-7.1.0-Transition","ember-7.1.0-Service":"ember-7.1.0-Service","ember-7.1.0-AssertAgainstAttrs":"ember-7.1.0-AssertAgainstAttrs","ember-7.1.0-AssertAgainstNamedOutlets":"ember-7.1.0-AssertAgainstNamedOutlets","ember-7.1.0-TransformActionSyntax":"ember-7.1.0-TransformActionSyntax","ember-7.1.0-TransformHasBlockSyntax":"ember-7.1.0-TransformHasBlockSyntax","ember-7.1.0-TransformInElement":"ember-7.1.0-TransformInElement","ember-7.1.0-TransformResolutions":"ember-7.1.0-TransformResolutions","ember-7.1.0-TestAdapter":"ember-7.1.0-TestAdapter","ember-7.1.0-Ember.Test":"ember-7.1.0-Ember.Test","ember-7.1.0-Ember":"ember-7.1.0-Ember","ember-7.1.0-Ember.Templates.components":"ember-7.1.0-Ember.Templates.components","ember-7.1.0-rsvp":"ember-7.1.0-rsvp","ember-7.1.0-@ember/array":"ember-7.1.0-@ember/array","ember-7.1.0-@ember/component":"ember-7.1.0-@ember/component","ember-7.1.0-@ember/component/helper":"ember-7.1.0-@ember/component/helper","ember-7.1.0-@ember/component/template-only":"ember-7.1.0-@ember/component/template-only","ember-7.1.0-@ember/debug":"ember-7.1.0-@ember/debug","ember-7.1.0-@ember/destroyable":"ember-7.1.0-@ember/destroyable","ember-7.1.0-@ember/engine":"ember-7.1.0-@ember/engine","ember-7.1.0-@ember/helper":"ember-7.1.0-@ember/helper","ember-7.1.0-@ember/instrumentation":"ember-7.1.0-@ember/instrumentation","ember-7.1.0-@ember/object":"ember-7.1.0-@ember/object","ember-7.1.0-@ember/object/compat":"ember-7.1.0-@ember/object/compat","ember-7.1.0-@ember/object/computed":"ember-7.1.0-@ember/object/computed","ember-7.1.0-@ember/object/evented":"ember-7.1.0-@ember/object/evented","ember-7.1.0-@ember/object/events":"ember-7.1.0-@ember/object/events","ember-7.1.0-@ember/object/internals":"ember-7.1.0-@ember/object/internals","ember-7.1.0-@ember/object/mixin":"ember-7.1.0-@ember/object/mixin","ember-7.1.0-@ember/object/observers":"ember-7.1.0-@ember/object/observers","ember-7.1.0-@ember/owner":"ember-7.1.0-@ember/owner","ember-7.1.0-@ember/reactive/collections":"ember-7.1.0-@ember/reactive/collections","ember-7.1.0-@ember/renderer":"ember-7.1.0-@ember/renderer","ember-7.1.0-@ember/routing":"ember-7.1.0-@ember/routing","ember-7.1.0-@ember/routing/location":"ember-7.1.0-@ember/routing/location","ember-7.1.0-@ember/runloop":"ember-7.1.0-@ember/runloop","ember-7.1.0-@ember/service":"ember-7.1.0-@ember/service","ember-7.1.0-@ember/template":"ember-7.1.0-@ember/template","ember-7.1.0-@ember/test":"ember-7.1.0-@ember/test","ember-7.1.0-@ember/utils":"ember-7.1.0-@ember/utils","ember-7.1.0-@glimmer/tracking":"ember-7.1.0-@glimmer/tracking","ember-7.1.0-@glimmer/tracking/primitives/cache":"ember-7.1.0-@glimmer/tracking/primitives/cache","ember-7.1.0-Ember.@ember/controller":"ember-7.1.0-Ember.@ember/controller"},"namespace":{"ember-7.1.0-FEATURES":"ember-7.1.0-FEATURES","ember-7.1.0-Instrumentation":"ember-7.1.0-Instrumentation"},"module":{"ember-7.1.0-rsvp":"ember-7.1.0-rsvp","ember-7.1.0-@ember/component":"ember-7.1.0-@ember/component","ember-7.1.0-@ember/routing":"ember-7.1.0-@ember/routing","ember-7.1.0-ember":"ember-7.1.0-ember","ember-7.1.0-@ember/helper":"ember-7.1.0-@ember/helper","ember-7.1.0-@ember/template":"ember-7.1.0-@ember/template","ember-7.1.0-@glimmer/tracking":"ember-7.1.0-@glimmer/tracking","ember-7.1.0-@ember/renderer":"ember-7.1.0-@ember/renderer","ember-7.1.0-@glimmer/tracking/primitives/cache":"ember-7.1.0-@glimmer/tracking/primitives/cache","ember-7.1.0-@ember/object":"ember-7.1.0-@ember/object","ember-7.1.0-@ember/owner":"ember-7.1.0-@ember/owner","ember-7.1.0-@ember/utils":"ember-7.1.0-@ember/utils","ember-7.1.0-@ember/application":"ember-7.1.0-@ember/application","ember-7.1.0-@ember/application/namespace":"ember-7.1.0-@ember/application/namespace","ember-7.1.0-@ember/array":"ember-7.1.0-@ember/array","ember-7.1.0-@ember/array/proxy":"ember-7.1.0-@ember/array/proxy","ember-7.1.0-@ember/canary-features":"ember-7.1.0-@ember/canary-features","ember-7.1.0-@ember/component/template-only":"ember-7.1.0-@ember/component/template-only","ember-7.1.0-@ember/controller":"ember-7.1.0-@ember/controller","ember-7.1.0-@ember/debug":"ember-7.1.0-@ember/debug","ember-7.1.0-@ember/debug/container-debug-adapter":"ember-7.1.0-@ember/debug/container-debug-adapter","ember-7.1.0-@ember/debug/data-adapter":"ember-7.1.0-@ember/debug/data-adapter","ember-7.1.0-@ember/destroyable":"ember-7.1.0-@ember/destroyable","ember-7.1.0-@ember/engine":"ember-7.1.0-@ember/engine","ember-7.1.0-@ember/enumerable":"ember-7.1.0-@ember/enumerable","ember-7.1.0-@ember/instrumentation":"ember-7.1.0-@ember/instrumentation","ember-7.1.0-@ember/object/core":"ember-7.1.0-@ember/object/core","ember-7.1.0-@ember/object/evented":"ember-7.1.0-@ember/object/evented","ember-7.1.0-@ember/object/mixin":"ember-7.1.0-@ember/object/mixin","ember-7.1.0-@ember/object/observable":"ember-7.1.0-@ember/object/observable","ember-7.1.0-@ember/object/promise-proxy-mixin":"ember-7.1.0-@ember/object/promise-proxy-mixin","ember-7.1.0-@ember/object/proxy":"ember-7.1.0-@ember/object/proxy","ember-7.1.0-@ember/reactive/collections":"ember-7.1.0-@ember/reactive/collections","ember-7.1.0-@ember/reactive":"ember-7.1.0-@ember/reactive","ember-7.1.0-@ember/routing/hash-location":"ember-7.1.0-@ember/routing/hash-location","ember-7.1.0-@ember/routing/history-location":"ember-7.1.0-@ember/routing/history-location","ember-7.1.0-@ember/routing/location":"ember-7.1.0-@ember/routing/location","ember-7.1.0-@ember/routing/none-location":"ember-7.1.0-@ember/routing/none-location","ember-7.1.0-@ember/routing/route-info":"ember-7.1.0-@ember/routing/route-info","ember-7.1.0-@ember/routing/route":"ember-7.1.0-@ember/routing/route","ember-7.1.0-@ember/routing/router-service":"ember-7.1.0-@ember/routing/router-service","ember-7.1.0-@ember/routing/router":"ember-7.1.0-@ember/routing/router","ember-7.1.0-@ember/routing/transition":"ember-7.1.0-@ember/routing/transition","ember-7.1.0-@ember/runloop":"ember-7.1.0-@ember/runloop","ember-7.1.0-@ember/service":"ember-7.1.0-@ember/service","ember-7.1.0-@glimmer/component":"ember-7.1.0-@glimmer/component","ember-7.1.0-@ember/test":"ember-7.1.0-@ember/test"},"missing":{"Ember.Namespace":"Ember.Namespace"}}}
\ No newline at end of file
+{"data":{"id":"ember-7.1.0","type":"project-version","attributes":{"version":"7.1.0"},"relationships":{"classes":{"data":[{"id":"ember-7.1.0-Promise","type":"class"},{"id":"ember-7.1.0-EventTarget","type":"class"},{"id":"ember-7.1.0-Container","type":"class"},{"id":"ember-7.1.0-Registry","type":"class"},{"id":"ember-7.1.0-EmberENV","type":"class"},{"id":"ember-7.1.0-ComponentStateBucket","type":"class"},{"id":"ember-7.1.0-TrustedHTML","type":"class"},{"id":"ember-7.1.0-SafeString","type":"class"},{"id":"ember-7.1.0-Component","type":"class"},{"id":"ember-7.1.0-Helper","type":"class"},{"id":"ember-7.1.0-Ember.Templates.helpers","type":"class"},{"id":"ember-7.1.0-ComputedProperty","type":"class"},{"id":"ember-7.1.0-Descriptor","type":"class"},{"id":"ember-7.1.0-Ember.InjectedProperty","type":"class"},{"id":"ember-7.1.0-Libraries","type":"class"},{"id":"ember-7.1.0-FullName","type":"class"},{"id":"ember-7.1.0-BasicRegistry","type":"class"},{"id":"ember-7.1.0-BasicContainer","type":"class"},{"id":"ember-7.1.0-Owner","type":"class"},{"id":"ember-7.1.0-RegisterOptions","type":"class"},{"id":"ember-7.1.0-Factory","type":"class"},{"id":"ember-7.1.0-FactoryManager","type":"class"},{"id":"ember-7.1.0-Resolver","type":"class"},{"id":"ember-7.1.0-InternalFactory","type":"class"},{"id":"ember-7.1.0-ContainerProxy","type":"class"},{"id":"ember-7.1.0-RegistryProxy","type":"class"},{"id":"ember-7.1.0-Ember.ProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.ActionHandler","type":"class"},{"id":"ember-7.1.0-Ember.Comparable","type":"class"},{"id":"ember-7.1.0-ContainerProxyMixin","type":"class"},{"id":"ember-7.1.0-RegistryProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.TargetActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.String","type":"class"},{"id":"ember-7.1.0-Ember.ActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.EventDispatcher","type":"class"},{"id":"ember-7.1.0-Ember.CoreView","type":"class"},{"id":"ember-7.1.0-Application","type":"class"},{"id":"ember-7.1.0-ApplicationInstance","type":"class"},{"id":"ember-7.1.0-ApplicationInstance.BootOptions","type":"class"},{"id":"ember-7.1.0-Namespace","type":"class"},{"id":"ember-7.1.0-EmberArray","type":"class"},{"id":"ember-7.1.0-MutableArray","type":"class"},{"id":"ember-7.1.0-Ember.NativeArray","type":"class"},{"id":"ember-7.1.0-ArrayProxy","type":"class"},{"id":"ember-7.1.0-Ember.ControllerMixin","type":"class"},{"id":"ember-7.1.0-Ember.Controller","type":"class"},{"id":"ember-7.1.0-ContainerDebugAdapter","type":"class"},{"id":"ember-7.1.0-DataAdapter","type":"class"},{"id":"ember-7.1.0-Engine","type":"class"},{"id":"ember-7.1.0-EngineInstance","type":"class"},{"id":"ember-7.1.0-Enumerable","type":"class"},{"id":"ember-7.1.0-Ember.MutableEnumerable","type":"class"},{"id":"ember-7.1.0-CoreObject","type":"class"},{"id":"ember-7.1.0-Evented","type":"class"},{"id":"ember-7.1.0-EmberObject","type":"class"},{"id":"ember-7.1.0-Mixin","type":"class"},{"id":"ember-7.1.0-Observable","type":"class"},{"id":"ember-7.1.0-PromiseProxyMixin","type":"class"},{"id":"ember-7.1.0-ObjectProxy","type":"class"},{"id":"ember-7.1.0-Renderer","type":"class"},{"id":"ember-7.1.0-BucketCache","type":"class"},{"id":"ember-7.1.0-RoutingService","type":"class"},{"id":"ember-7.1.0-HashLocation","type":"class"},{"id":"ember-7.1.0-HistoryLocation","type":"class"},{"id":"ember-7.1.0-Location","type":"class"},{"id":"ember-7.1.0-NoneLocation","type":"class"},{"id":"ember-7.1.0-RouteInfo","type":"class"},{"id":"ember-7.1.0-RouteInfoWithAttributes","type":"class"},{"id":"ember-7.1.0-Route","type":"class"},{"id":"ember-7.1.0-RouterService","type":"class"},{"id":"ember-7.1.0-EmberRouter","type":"class"},{"id":"ember-7.1.0-Transition","type":"class"},{"id":"ember-7.1.0-Service","type":"class"},{"id":"ember-7.1.0-AssertAgainstAttrs","type":"class"},{"id":"ember-7.1.0-AssertAgainstNamedOutlets","type":"class"},{"id":"ember-7.1.0-TransformActionSyntax","type":"class"},{"id":"ember-7.1.0-TransformHasBlockSyntax","type":"class"},{"id":"ember-7.1.0-TransformInElement","type":"class"},{"id":"ember-7.1.0-TransformResolutions","type":"class"},{"id":"ember-7.1.0-TestAdapter","type":"class"},{"id":"ember-7.1.0-Ember.Test","type":"class"}]},"namespaces":{"data":[{"id":"ember-7.1.0-FEATURES","type":"namespace"},{"id":"ember-7.1.0-Instrumentation","type":"namespace"}]},"modules":{"data":[{"id":"ember-7.1.0-rsvp","type":"module"},{"id":"ember-7.1.0-@ember/component","type":"module"},{"id":"ember-7.1.0-@ember/routing","type":"module"},{"id":"ember-7.1.0-ember","type":"module"},{"id":"ember-7.1.0-@ember/helper","type":"module"},{"id":"ember-7.1.0-@ember/template","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking","type":"module"},{"id":"ember-7.1.0-@ember/renderer","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking/primitives/cache","type":"module"},{"id":"ember-7.1.0-@ember/object","type":"module"},{"id":"ember-7.1.0-@ember/owner","type":"module"},{"id":"ember-7.1.0-@ember/utils","type":"module"},{"id":"ember-7.1.0-@ember/application","type":"module"},{"id":"ember-7.1.0-@ember/application/namespace","type":"module"},{"id":"ember-7.1.0-@ember/array","type":"module"},{"id":"ember-7.1.0-@ember/array/proxy","type":"module"},{"id":"ember-7.1.0-@ember/canary-features","type":"module"},{"id":"ember-7.1.0-@ember/component/template-only","type":"module"},{"id":"ember-7.1.0-@ember/controller","type":"module"},{"id":"ember-7.1.0-@ember/debug","type":"module"},{"id":"ember-7.1.0-@ember/debug/container-debug-adapter","type":"module"},{"id":"ember-7.1.0-@ember/debug/data-adapter","type":"module"},{"id":"ember-7.1.0-@ember/destroyable","type":"module"},{"id":"ember-7.1.0-@ember/engine","type":"module"},{"id":"ember-7.1.0-@ember/enumerable","type":"module"},{"id":"ember-7.1.0-@ember/instrumentation","type":"module"},{"id":"ember-7.1.0-@ember/object/core","type":"module"},{"id":"ember-7.1.0-@ember/object/evented","type":"module"},{"id":"ember-7.1.0-@ember/object/mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/observable","type":"module"},{"id":"ember-7.1.0-@ember/object/promise-proxy-mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/proxy","type":"module"},{"id":"ember-7.1.0-@ember/reactive/collections","type":"module"},{"id":"ember-7.1.0-@ember/reactive","type":"module"},{"id":"ember-7.1.0-@ember/routing/hash-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/history-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/location","type":"module"},{"id":"ember-7.1.0-@ember/routing/none-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/route-info","type":"module"},{"id":"ember-7.1.0-@ember/routing/route","type":"module"},{"id":"ember-7.1.0-@ember/routing/router-service","type":"module"},{"id":"ember-7.1.0-@ember/routing/router","type":"module"},{"id":"ember-7.1.0-@ember/routing/transition","type":"module"},{"id":"ember-7.1.0-@ember/runloop","type":"module"},{"id":"ember-7.1.0-@ember/service","type":"module"},{"id":"ember-7.1.0-@glimmer/component","type":"module"},{"id":"ember-7.1.0-@ember/test","type":"module"}]},"project":{"data":{"id":"ember","type":"project"}},"private-classes":{"data":[{"id":"ember-7.1.0-Container","type":"class"},{"id":"ember-7.1.0-Registry","type":"class"},{"id":"ember-7.1.0-ComponentStateBucket","type":"class"},{"id":"ember-7.1.0-Descriptor","type":"class"},{"id":"ember-7.1.0-Ember.InjectedProperty","type":"class"},{"id":"ember-7.1.0-Libraries","type":"class"},{"id":"ember-7.1.0-BasicRegistry","type":"class"},{"id":"ember-7.1.0-BasicContainer","type":"class"},{"id":"ember-7.1.0-InternalFactory","type":"class"},{"id":"ember-7.1.0-ContainerProxy","type":"class"},{"id":"ember-7.1.0-RegistryProxy","type":"class"},{"id":"ember-7.1.0-Ember.ProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.ActionHandler","type":"class"},{"id":"ember-7.1.0-Ember.Comparable","type":"class"},{"id":"ember-7.1.0-ContainerProxyMixin","type":"class"},{"id":"ember-7.1.0-RegistryProxyMixin","type":"class"},{"id":"ember-7.1.0-Ember.TargetActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.String","type":"class"},{"id":"ember-7.1.0-Ember.ActionSupport","type":"class"},{"id":"ember-7.1.0-Ember.EventDispatcher","type":"class"},{"id":"ember-7.1.0-Ember.CoreView","type":"class"},{"id":"ember-7.1.0-Ember.ControllerMixin","type":"class"},{"id":"ember-7.1.0-Enumerable","type":"class"},{"id":"ember-7.1.0-Ember.MutableEnumerable","type":"class"},{"id":"ember-7.1.0-BucketCache","type":"class"},{"id":"ember-7.1.0-RoutingService","type":"class"},{"id":"ember-7.1.0-AssertAgainstAttrs","type":"class"},{"id":"ember-7.1.0-AssertAgainstNamedOutlets","type":"class"},{"id":"ember-7.1.0-TransformActionSyntax","type":"class"},{"id":"ember-7.1.0-TransformHasBlockSyntax","type":"class"},{"id":"ember-7.1.0-TransformInElement","type":"class"},{"id":"ember-7.1.0-TransformResolutions","type":"class"}]},"public-classes":{"data":[{"id":"ember-7.1.0-Promise","type":"class"},{"id":"ember-7.1.0-EventTarget","type":"class"},{"id":"ember-7.1.0-EmberENV","type":"class"},{"id":"ember-7.1.0-TrustedHTML","type":"class"},{"id":"ember-7.1.0-SafeString","type":"class"},{"id":"ember-7.1.0-Component","type":"class"},{"id":"ember-7.1.0-Helper","type":"class"},{"id":"ember-7.1.0-Ember.Templates.helpers","type":"class"},{"id":"ember-7.1.0-ComputedProperty","type":"class"},{"id":"ember-7.1.0-FullName","type":"class"},{"id":"ember-7.1.0-Owner","type":"class"},{"id":"ember-7.1.0-RegisterOptions","type":"class"},{"id":"ember-7.1.0-Factory","type":"class"},{"id":"ember-7.1.0-FactoryManager","type":"class"},{"id":"ember-7.1.0-Resolver","type":"class"},{"id":"ember-7.1.0-Application","type":"class"},{"id":"ember-7.1.0-ApplicationInstance","type":"class"},{"id":"ember-7.1.0-ApplicationInstance.BootOptions","type":"class"},{"id":"ember-7.1.0-Namespace","type":"class"},{"id":"ember-7.1.0-EmberArray","type":"class"},{"id":"ember-7.1.0-MutableArray","type":"class"},{"id":"ember-7.1.0-Ember.NativeArray","type":"class"},{"id":"ember-7.1.0-ArrayProxy","type":"class"},{"id":"ember-7.1.0-Ember.Controller","type":"class"},{"id":"ember-7.1.0-ContainerDebugAdapter","type":"class"},{"id":"ember-7.1.0-DataAdapter","type":"class"},{"id":"ember-7.1.0-Engine","type":"class"},{"id":"ember-7.1.0-EngineInstance","type":"class"},{"id":"ember-7.1.0-CoreObject","type":"class"},{"id":"ember-7.1.0-Evented","type":"class"},{"id":"ember-7.1.0-EmberObject","type":"class"},{"id":"ember-7.1.0-Mixin","type":"class"},{"id":"ember-7.1.0-Observable","type":"class"},{"id":"ember-7.1.0-PromiseProxyMixin","type":"class"},{"id":"ember-7.1.0-ObjectProxy","type":"class"},{"id":"ember-7.1.0-Renderer","type":"class"},{"id":"ember-7.1.0-HashLocation","type":"class"},{"id":"ember-7.1.0-HistoryLocation","type":"class"},{"id":"ember-7.1.0-Location","type":"class"},{"id":"ember-7.1.0-NoneLocation","type":"class"},{"id":"ember-7.1.0-RouteInfo","type":"class"},{"id":"ember-7.1.0-RouteInfoWithAttributes","type":"class"},{"id":"ember-7.1.0-Route","type":"class"},{"id":"ember-7.1.0-RouterService","type":"class"},{"id":"ember-7.1.0-EmberRouter","type":"class"},{"id":"ember-7.1.0-Transition","type":"class"},{"id":"ember-7.1.0-Service","type":"class"},{"id":"ember-7.1.0-TestAdapter","type":"class"},{"id":"ember-7.1.0-Ember.Test","type":"class"}]},"private-namespaces":{"data":[{"id":"ember-7.1.0-Instrumentation","type":"namespace"}]},"public-namespaces":{"data":[{"id":"ember-7.1.0-FEATURES","type":"namespace"}]},"private-modules":{"data":[{"id":"ember-7.1.0-ember","type":"module"},{"id":"ember-7.1.0-@ember/enumerable","type":"module"},{"id":"ember-7.1.0-@ember/instrumentation","type":"module"}]},"public-modules":{"data":[{"id":"ember-7.1.0-rsvp","type":"module"},{"id":"ember-7.1.0-@ember/component","type":"module"},{"id":"ember-7.1.0-@ember/routing","type":"module"},{"id":"ember-7.1.0-@ember/helper","type":"module"},{"id":"ember-7.1.0-@ember/template","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking","type":"module"},{"id":"ember-7.1.0-@ember/renderer","type":"module"},{"id":"ember-7.1.0-@glimmer/tracking/primitives/cache","type":"module"},{"id":"ember-7.1.0-@ember/object","type":"module"},{"id":"ember-7.1.0-@ember/owner","type":"module"},{"id":"ember-7.1.0-@ember/utils","type":"module"},{"id":"ember-7.1.0-@ember/application","type":"module"},{"id":"ember-7.1.0-@ember/application/namespace","type":"module"},{"id":"ember-7.1.0-@ember/array","type":"module"},{"id":"ember-7.1.0-@ember/array/proxy","type":"module"},{"id":"ember-7.1.0-@ember/canary-features","type":"module"},{"id":"ember-7.1.0-@ember/component/template-only","type":"module"},{"id":"ember-7.1.0-@ember/controller","type":"module"},{"id":"ember-7.1.0-@ember/debug","type":"module"},{"id":"ember-7.1.0-@ember/debug/container-debug-adapter","type":"module"},{"id":"ember-7.1.0-@ember/debug/data-adapter","type":"module"},{"id":"ember-7.1.0-@ember/destroyable","type":"module"},{"id":"ember-7.1.0-@ember/engine","type":"module"},{"id":"ember-7.1.0-@ember/object/core","type":"module"},{"id":"ember-7.1.0-@ember/object/evented","type":"module"},{"id":"ember-7.1.0-@ember/object/mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/observable","type":"module"},{"id":"ember-7.1.0-@ember/object/promise-proxy-mixin","type":"module"},{"id":"ember-7.1.0-@ember/object/proxy","type":"module"},{"id":"ember-7.1.0-@ember/reactive/collections","type":"module"},{"id":"ember-7.1.0-@ember/reactive","type":"module"},{"id":"ember-7.1.0-@ember/routing/hash-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/history-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/location","type":"module"},{"id":"ember-7.1.0-@ember/routing/none-location","type":"module"},{"id":"ember-7.1.0-@ember/routing/route-info","type":"module"},{"id":"ember-7.1.0-@ember/routing/route","type":"module"},{"id":"ember-7.1.0-@ember/routing/router-service","type":"module"},{"id":"ember-7.1.0-@ember/routing/router","type":"module"},{"id":"ember-7.1.0-@ember/routing/transition","type":"module"},{"id":"ember-7.1.0-@ember/runloop","type":"module"},{"id":"ember-7.1.0-@ember/service","type":"module"},{"id":"ember-7.1.0-@glimmer/component","type":"module"},{"id":"ember-7.1.0-@ember/test","type":"module"}]}}},"meta":{"class":{"ember-7.1.0-Promise":"ember-7.1.0-Promise","ember-7.1.0-EventTarget":"ember-7.1.0-EventTarget","ember-7.1.0-Container":"ember-7.1.0-Container","ember-7.1.0-Registry":"ember-7.1.0-Registry","ember-7.1.0-EmberENV":"ember-7.1.0-EmberENV","ember-7.1.0-ComponentStateBucket":"ember-7.1.0-ComponentStateBucket","ember-7.1.0-TrustedHTML":"ember-7.1.0-TrustedHTML","ember-7.1.0-SafeString":"ember-7.1.0-SafeString","ember-7.1.0-Component":"ember-7.1.0-Component","ember-7.1.0-Helper":"ember-7.1.0-Helper","ember-7.1.0-Ember.Templates.helpers":"ember-7.1.0-Ember.Templates.helpers","ember-7.1.0-ComputedProperty":"ember-7.1.0-ComputedProperty","ember-7.1.0-Descriptor":"ember-7.1.0-Descriptor","ember-7.1.0-Ember.InjectedProperty":"ember-7.1.0-Ember.InjectedProperty","ember-7.1.0-Libraries":"ember-7.1.0-Libraries","ember-7.1.0-FullName":"ember-7.1.0-FullName","ember-7.1.0-BasicRegistry":"ember-7.1.0-BasicRegistry","ember-7.1.0-BasicContainer":"ember-7.1.0-BasicContainer","ember-7.1.0-Owner":"ember-7.1.0-Owner","ember-7.1.0-RegisterOptions":"ember-7.1.0-RegisterOptions","ember-7.1.0-Factory":"ember-7.1.0-Factory","ember-7.1.0-FactoryManager":"ember-7.1.0-FactoryManager","ember-7.1.0-Resolver":"ember-7.1.0-Resolver","ember-7.1.0-InternalFactory":"ember-7.1.0-InternalFactory","ember-7.1.0-ContainerProxy":"ember-7.1.0-ContainerProxy","ember-7.1.0-RegistryProxy":"ember-7.1.0-RegistryProxy","ember-7.1.0-Ember.ProxyMixin":"ember-7.1.0-Ember.ProxyMixin","ember-7.1.0-Ember.ActionHandler":"ember-7.1.0-Ember.ActionHandler","ember-7.1.0-Ember.Comparable":"ember-7.1.0-Ember.Comparable","ember-7.1.0-ContainerProxyMixin":"ember-7.1.0-ContainerProxyMixin","ember-7.1.0-RegistryProxyMixin":"ember-7.1.0-RegistryProxyMixin","ember-7.1.0-Ember.TargetActionSupport":"ember-7.1.0-Ember.TargetActionSupport","ember-7.1.0-Ember.String":"ember-7.1.0-Ember.String","ember-7.1.0-Ember.ActionSupport":"ember-7.1.0-Ember.ActionSupport","ember-7.1.0-Ember.EventDispatcher":"ember-7.1.0-Ember.EventDispatcher","ember-7.1.0-Ember.CoreView":"ember-7.1.0-Ember.CoreView","ember-7.1.0-Application":"ember-7.1.0-Application","ember-7.1.0-ApplicationInstance":"ember-7.1.0-ApplicationInstance","ember-7.1.0-ApplicationInstance.BootOptions":"ember-7.1.0-ApplicationInstance.BootOptions","ember-7.1.0-Namespace":"ember-7.1.0-Namespace","ember-7.1.0-EmberArray":"ember-7.1.0-EmberArray","ember-7.1.0-MutableArray":"ember-7.1.0-MutableArray","ember-7.1.0-Ember.NativeArray":"ember-7.1.0-Ember.NativeArray","ember-7.1.0-ArrayProxy":"ember-7.1.0-ArrayProxy","ember-7.1.0-Ember.ControllerMixin":"ember-7.1.0-Ember.ControllerMixin","ember-7.1.0-Ember.Controller":"ember-7.1.0-Ember.Controller","ember-7.1.0-ContainerDebugAdapter":"ember-7.1.0-ContainerDebugAdapter","ember-7.1.0-DataAdapter":"ember-7.1.0-DataAdapter","ember-7.1.0-Engine":"ember-7.1.0-Engine","ember-7.1.0-EngineInstance":"ember-7.1.0-EngineInstance","ember-7.1.0-Enumerable":"ember-7.1.0-Enumerable","ember-7.1.0-Ember.MutableEnumerable":"ember-7.1.0-Ember.MutableEnumerable","ember-7.1.0-CoreObject":"ember-7.1.0-CoreObject","ember-7.1.0-Evented":"ember-7.1.0-Evented","ember-7.1.0-EmberObject":"ember-7.1.0-EmberObject","ember-7.1.0-Mixin":"ember-7.1.0-Mixin","ember-7.1.0-Observable":"ember-7.1.0-Observable","ember-7.1.0-PromiseProxyMixin":"ember-7.1.0-PromiseProxyMixin","ember-7.1.0-ObjectProxy":"ember-7.1.0-ObjectProxy","ember-7.1.0-Renderer":"ember-7.1.0-Renderer","ember-7.1.0-BucketCache":"ember-7.1.0-BucketCache","ember-7.1.0-RoutingService":"ember-7.1.0-RoutingService","ember-7.1.0-HashLocation":"ember-7.1.0-HashLocation","ember-7.1.0-HistoryLocation":"ember-7.1.0-HistoryLocation","ember-7.1.0-Location":"ember-7.1.0-Location","ember-7.1.0-NoneLocation":"ember-7.1.0-NoneLocation","ember-7.1.0-RouteInfo":"ember-7.1.0-RouteInfo","ember-7.1.0-RouteInfoWithAttributes":"ember-7.1.0-RouteInfoWithAttributes","ember-7.1.0-Route":"ember-7.1.0-Route","ember-7.1.0-RouterService":"ember-7.1.0-RouterService","ember-7.1.0-EmberRouter":"ember-7.1.0-EmberRouter","ember-7.1.0-Transition":"ember-7.1.0-Transition","ember-7.1.0-Service":"ember-7.1.0-Service","ember-7.1.0-AssertAgainstAttrs":"ember-7.1.0-AssertAgainstAttrs","ember-7.1.0-AssertAgainstNamedOutlets":"ember-7.1.0-AssertAgainstNamedOutlets","ember-7.1.0-TransformActionSyntax":"ember-7.1.0-TransformActionSyntax","ember-7.1.0-TransformHasBlockSyntax":"ember-7.1.0-TransformHasBlockSyntax","ember-7.1.0-TransformInElement":"ember-7.1.0-TransformInElement","ember-7.1.0-TransformResolutions":"ember-7.1.0-TransformResolutions","ember-7.1.0-TestAdapter":"ember-7.1.0-TestAdapter","ember-7.1.0-Ember.Test":"ember-7.1.0-Ember.Test","ember-7.1.0-Ember":"ember-7.1.0-Ember","ember-7.1.0-External":"ember-7.1.0-External","ember-7.1.0-Keywords":"ember-7.1.0-Keywords","ember-7.1.0-rsvp":"ember-7.1.0-rsvp","ember-7.1.0-@ember/array":"ember-7.1.0-@ember/array","ember-7.1.0-@ember/component":"ember-7.1.0-@ember/component","ember-7.1.0-@ember/component/helper":"ember-7.1.0-@ember/component/helper","ember-7.1.0-@ember/component/template-only":"ember-7.1.0-@ember/component/template-only","ember-7.1.0-@ember/debug":"ember-7.1.0-@ember/debug","ember-7.1.0-@ember/destroyable":"ember-7.1.0-@ember/destroyable","ember-7.1.0-@ember/engine":"ember-7.1.0-@ember/engine","ember-7.1.0-@ember/helper":"ember-7.1.0-@ember/helper","ember-7.1.0-@ember/instrumentation":"ember-7.1.0-@ember/instrumentation","ember-7.1.0-@ember/object":"ember-7.1.0-@ember/object","ember-7.1.0-@ember/object/compat":"ember-7.1.0-@ember/object/compat","ember-7.1.0-@ember/object/computed":"ember-7.1.0-@ember/object/computed","ember-7.1.0-@ember/object/evented":"ember-7.1.0-@ember/object/evented","ember-7.1.0-@ember/object/events":"ember-7.1.0-@ember/object/events","ember-7.1.0-@ember/object/internals":"ember-7.1.0-@ember/object/internals","ember-7.1.0-@ember/object/mixin":"ember-7.1.0-@ember/object/mixin","ember-7.1.0-@ember/object/observers":"ember-7.1.0-@ember/object/observers","ember-7.1.0-@ember/owner":"ember-7.1.0-@ember/owner","ember-7.1.0-@ember/reactive/collections":"ember-7.1.0-@ember/reactive/collections","ember-7.1.0-@ember/renderer":"ember-7.1.0-@ember/renderer","ember-7.1.0-@ember/routing":"ember-7.1.0-@ember/routing","ember-7.1.0-@ember/routing/location":"ember-7.1.0-@ember/routing/location","ember-7.1.0-@ember/runloop":"ember-7.1.0-@ember/runloop","ember-7.1.0-@ember/service":"ember-7.1.0-@ember/service","ember-7.1.0-@ember/template":"ember-7.1.0-@ember/template","ember-7.1.0-@ember/test":"ember-7.1.0-@ember/test","ember-7.1.0-@ember/utils":"ember-7.1.0-@ember/utils","ember-7.1.0-@glimmer/tracking":"ember-7.1.0-@glimmer/tracking","ember-7.1.0-@glimmer/tracking/primitives/cache":"ember-7.1.0-@glimmer/tracking/primitives/cache","ember-7.1.0-Ember.@ember/controller":"ember-7.1.0-Ember.@ember/controller"},"namespace":{"ember-7.1.0-FEATURES":"ember-7.1.0-FEATURES","ember-7.1.0-Instrumentation":"ember-7.1.0-Instrumentation"},"module":{"ember-7.1.0-rsvp":"ember-7.1.0-rsvp","ember-7.1.0-@ember/component":"ember-7.1.0-@ember/component","ember-7.1.0-@ember/routing":"ember-7.1.0-@ember/routing","ember-7.1.0-ember":"ember-7.1.0-ember","ember-7.1.0-@ember/helper":"ember-7.1.0-@ember/helper","ember-7.1.0-@ember/template":"ember-7.1.0-@ember/template","ember-7.1.0-@glimmer/tracking":"ember-7.1.0-@glimmer/tracking","ember-7.1.0-@ember/renderer":"ember-7.1.0-@ember/renderer","ember-7.1.0-@glimmer/tracking/primitives/cache":"ember-7.1.0-@glimmer/tracking/primitives/cache","ember-7.1.0-@ember/object":"ember-7.1.0-@ember/object","ember-7.1.0-@ember/owner":"ember-7.1.0-@ember/owner","ember-7.1.0-@ember/utils":"ember-7.1.0-@ember/utils","ember-7.1.0-@ember/application":"ember-7.1.0-@ember/application","ember-7.1.0-@ember/application/namespace":"ember-7.1.0-@ember/application/namespace","ember-7.1.0-@ember/array":"ember-7.1.0-@ember/array","ember-7.1.0-@ember/array/proxy":"ember-7.1.0-@ember/array/proxy","ember-7.1.0-@ember/canary-features":"ember-7.1.0-@ember/canary-features","ember-7.1.0-@ember/component/template-only":"ember-7.1.0-@ember/component/template-only","ember-7.1.0-@ember/controller":"ember-7.1.0-@ember/controller","ember-7.1.0-@ember/debug":"ember-7.1.0-@ember/debug","ember-7.1.0-@ember/debug/container-debug-adapter":"ember-7.1.0-@ember/debug/container-debug-adapter","ember-7.1.0-@ember/debug/data-adapter":"ember-7.1.0-@ember/debug/data-adapter","ember-7.1.0-@ember/destroyable":"ember-7.1.0-@ember/destroyable","ember-7.1.0-@ember/engine":"ember-7.1.0-@ember/engine","ember-7.1.0-@ember/enumerable":"ember-7.1.0-@ember/enumerable","ember-7.1.0-@ember/instrumentation":"ember-7.1.0-@ember/instrumentation","ember-7.1.0-@ember/object/core":"ember-7.1.0-@ember/object/core","ember-7.1.0-@ember/object/evented":"ember-7.1.0-@ember/object/evented","ember-7.1.0-@ember/object/mixin":"ember-7.1.0-@ember/object/mixin","ember-7.1.0-@ember/object/observable":"ember-7.1.0-@ember/object/observable","ember-7.1.0-@ember/object/promise-proxy-mixin":"ember-7.1.0-@ember/object/promise-proxy-mixin","ember-7.1.0-@ember/object/proxy":"ember-7.1.0-@ember/object/proxy","ember-7.1.0-@ember/reactive/collections":"ember-7.1.0-@ember/reactive/collections","ember-7.1.0-@ember/reactive":"ember-7.1.0-@ember/reactive","ember-7.1.0-@ember/routing/hash-location":"ember-7.1.0-@ember/routing/hash-location","ember-7.1.0-@ember/routing/history-location":"ember-7.1.0-@ember/routing/history-location","ember-7.1.0-@ember/routing/location":"ember-7.1.0-@ember/routing/location","ember-7.1.0-@ember/routing/none-location":"ember-7.1.0-@ember/routing/none-location","ember-7.1.0-@ember/routing/route-info":"ember-7.1.0-@ember/routing/route-info","ember-7.1.0-@ember/routing/route":"ember-7.1.0-@ember/routing/route","ember-7.1.0-@ember/routing/router-service":"ember-7.1.0-@ember/routing/router-service","ember-7.1.0-@ember/routing/router":"ember-7.1.0-@ember/routing/router","ember-7.1.0-@ember/routing/transition":"ember-7.1.0-@ember/routing/transition","ember-7.1.0-@ember/runloop":"ember-7.1.0-@ember/runloop","ember-7.1.0-@ember/service":"ember-7.1.0-@ember/service","ember-7.1.0-@glimmer/component":"ember-7.1.0-@glimmer/component","ember-7.1.0-@ember/test":"ember-7.1.0-@ember/test"},"missing":{"Ember.Namespace":"Ember.Namespace"}}}
\ No newline at end of file
diff --git a/s3-docs/v7.1.0/ember-docs.json b/s3-docs/v7.1.0/ember-docs.json
index 5d9d056d6..479aeba4d 100644
--- a/s3-docs/v7.1.0/ember-docs.json
+++ b/s3-docs/v7.1.0/ember-docs.json
@@ -228,9 +228,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1,
-        "@ember/component": 1,
-        "Ember.Templates.components": 1
+        "@ember/component": 1
       },
       "namespaces": {}
     },
@@ -246,8 +244,6 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.components": 1,
-        "Ember.Templates.helpers": 1,
         "@ember/routing": 1
       },
       "namespaces": {}
@@ -257,8 +253,6 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.components": 1,
-        "Ember.Templates.helpers": 1,
         "@ember/component": 1
       },
       "namespaces": {}
@@ -284,39 +278,12 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@ember/-internals/glimmer/lib/helpers/array.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/array.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "@ember/helper": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/component.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/component.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/concat.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/concat.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "@ember/helper": 1
-      },
-      "namespaces": {}
-    },
     "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts": {
       "name": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -324,72 +291,7 @@
       "name": "packages/@ember/-internals/glimmer/lib/helpers/element.ts",
       "modules": {},
       "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/fn.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/fn.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "@ember/helper": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/get.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/get.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "@ember/helper": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/hash.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/hash.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "@ember/helper": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/helper.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/helper.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/log.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/log.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/modifier.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/modifier.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
+      "fors": {},
       "namespaces": {}
     },
     "packages/@ember/-internals/glimmer/lib/helpers/mut.ts": {
@@ -397,16 +299,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/page-title.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/page-title.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -415,7 +308,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -424,43 +317,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/modifiers/on.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/modifiers/on.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/syntax/in-element.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/syntax/in-element.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
-      "namespaces": {}
-    },
-    "packages/@ember/-internals/glimmer/lib/syntax/let.ts": {
-      "name": "packages/@ember/-internals/glimmer/lib/syntax/let.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -469,7 +326,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -478,7 +335,7 @@
       "modules": {},
       "classes": {},
       "fors": {
-        "Ember.Templates.helpers": 1
+        "Keywords": 1
       },
       "namespaces": {}
     },
@@ -586,9 +443,7 @@
       "classes": {
         "Ember.Templates.helpers": 1
       },
-      "fors": {
-        "Ember.Templates.helpers": 1
-      },
+      "fors": {},
       "namespaces": {}
     },
     "packages/@ember/-internals/meta/lib/meta.ts": {
@@ -1195,12 +1050,12 @@
     },
     "packages/@ember/helper/index.ts": {
       "name": "packages/@ember/helper/index.ts",
-      "modules": {
-        "@ember/helper": 1
-      },
+      "modules": {},
       "classes": {},
       "fors": {
-        "@ember/helper": 1
+        "@ember/helper": 1,
+        "Keywords": 1,
+        "External": 1
       },
       "namespaces": {}
     },
@@ -1761,6 +1616,36 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/component/dist/-private/component.d.ts": {
+      "name": "packages/@glimmer/component/dist/-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",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
+    "packages/@glimmer/component/dist/index.d.ts": {
+      "name": "packages/@glimmer/component/dist/index.d.ts",
+      "modules": {
+        "@glimmer/component": 1
+      },
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
+    "packages/@glimmer/component/dist/index.js": {
+      "name": "packages/@glimmer/component/dist/index.js",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/component/src/-private/component.ts": {
       "name": "packages/@glimmer/component/src/-private/component.ts",
       "modules": {},
@@ -1777,9 +1662,7 @@
     },
     "packages/@glimmer/component/src/index.ts": {
       "name": "packages/@glimmer/component/src/index.ts",
-      "modules": {
-        "@glimmer/component": 1
-      },
+      "modules": {},
       "classes": {},
       "fors": {},
       "namespaces": {}
@@ -2106,20 +1989,6 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/runtime/lib/helpers/array.ts": {
-      "name": "packages/@glimmer/runtime/lib/helpers/array.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
-    "packages/@glimmer/runtime/lib/helpers/concat.ts": {
-      "name": "packages/@glimmer/runtime/lib/helpers/concat.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
     "packages/@glimmer/runtime/lib/helpers/eq.ts": {
       "name": "packages/@glimmer/runtime/lib/helpers/eq.ts",
       "modules": {},
@@ -2127,20 +1996,6 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/runtime/lib/helpers/fn.ts": {
-      "name": "packages/@glimmer/runtime/lib/helpers/fn.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
-    "packages/@glimmer/runtime/lib/helpers/get.ts": {
-      "name": "packages/@glimmer/runtime/lib/helpers/get.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
     "packages/@glimmer/runtime/lib/helpers/gt.ts": {
       "name": "packages/@glimmer/runtime/lib/helpers/gt.ts",
       "modules": {},
@@ -2155,13 +2010,6 @@
       "fors": {},
       "namespaces": {}
     },
-    "packages/@glimmer/runtime/lib/helpers/hash.ts": {
-      "name": "packages/@glimmer/runtime/lib/helpers/hash.ts",
-      "modules": {},
-      "classes": {},
-      "fors": {},
-      "namespaces": {}
-    },
     "packages/@glimmer/runtime/lib/helpers/lt.ts": {
       "name": "packages/@glimmer/runtime/lib/helpers/lt.ts",
       "modules": {},
@@ -2185,9 +2033,13 @@
     },
     "packages/@glimmer/runtime/lib/modifiers/on.ts": {
       "name": "packages/@glimmer/runtime/lib/modifiers/on.ts",
-      "modules": {},
+      "modules": {
+        "@ember/helper": 1
+      },
       "classes": {},
-      "fors": {},
+      "fors": {
+        "Keywords": 1
+      },
       "namespaces": {}
     },
     "packages/@glimmer/runtime/lib/vm/append.ts": {
@@ -2225,6 +2077,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/syntax/dist/es/index.js": {
+      "name": "packages/@glimmer/syntax/dist/es/index.js",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/syntax/lib/generation/printer.ts": {
       "name": "packages/@glimmer/syntax/lib/generation/printer.ts",
       "modules": {},
@@ -2565,16 +2424,14 @@
         "@ember/component/helper": 1
       },
       "fors": {
-        "Ember.Templates.helpers": 1,
         "@ember/component": 1,
-        "Ember.Templates.components": 1,
         "@ember/component/helper": 1
       },
       "namespaces": {},
       "tag": "main",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
       "line": 57,
-      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\ndefault component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\ndefault for older editions of Ember (pre 3.15) but are still supported.\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the\n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked name = 'Jill'\n}\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in helpers are described under the [Ember.Templates.helpers](/ember/release/classes/Ember.Templates.helpers)\nnamespace. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
+      "description": "[Glimmer](https://github.com/tildeio/glimmer) is a templating engine used by Ember.js that is compatible with a subset of the [Handlebars](http://handlebarsjs.com/) syntax.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\ndefault component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\ndefault for older editions of Ember (pre 3.15) but are still supported.\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the\n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n### Showing a property\n\nTemplates manage the flow of an application's UI, and display state (through\nthe DOM) to a user. For example, given a component with the property \"name\",\nthat component's template can use the name in several ways:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked name = 'Jill'\n}\n```\n\n```app/components/person-profile.hbs\n{{this.name}}\n<div>{{this.name}}</div>\n<span data-name={{this.name}}></span>\n```\n\nAny time the \"name\" property on the component changes, the DOM will be\nupdated.\n\nProperties can be chained as well:\n\n```handlebars\n{{@aUserModel.name}}\n<div>{{@listOfUsers.firstObject.name}}</div>\n```\n\n### Using Ember helpers\n\nWhen content is passed in mustaches `{{}}`, Ember will first try to find a helper\nor component with that name. For example, the `if` helper:\n\n```app/components/person-profile.hbs\n{{if this.name \"I have a name\" \"I have no name\"}}\n<span data-has-name={{if this.name true}}></span>\n```\n\nThe returned value is placed where the `{{}}` is called. The above style is\ncalled \"inline\". A second style of helper usage is called \"block\". For example:\n\n```handlebars\n{{#if this.name}}\n  I have a name\n{{else}}\n  I have no name\n{{/if}}\n```\n\nThe block form of helpers allows you to control how the UI is created based\non the values of properties.\nA third form of helper is called \"nested\". For example here the concat\nhelper will add \" Doe\" to a displayed name if the person has no last name:\n\n```handlebars\n<span data-name={{concat this.firstName (\n  if this.lastName (concat \" \" this.lastName) \"Doe\"\n)}}></span>\n```\n\nEmber's built-in and importable helpers are described under the [@ember/helper](../modules/@ember%2Fhelper).\nmodule. Documentation on creating custom helpers can be found under\n[helper](/ember/release/functions/@ember%2Fcomponent%2Fhelper/helper) (or\nunder [Helper](/ember/release/classes/Helper) if a helper requires access to\ndependency injection).\n\n### Invoking a Component\n\nEmber components represent state to the UI of an application. Further\nreading on components can be found under [Component](/ember/release/classes/Component).",
       "itemtype": "main",
       "access": "public",
       "tagname": ""
@@ -2584,11 +2441,9 @@
       "submodules": {},
       "elements": {},
       "classes": {
-        "Ember.Templates.components": 1,
         "@ember/routing": 1
       },
       "fors": {
-        "Ember.Templates.helpers": 1,
         "@ember/routing": 1,
         "Ember": 1
       },
@@ -2605,9 +2460,8 @@
       "elements": {},
       "classes": {
         "@ember/array": 1,
-        "Ember.Templates.helpers": 1,
-        "@ember/helper": 1,
         "ComponentStateBucket": 1,
+        "Ember.Templates.helpers": 1,
         "Ember.InjectedProperty": 1,
         "Libraries": 1,
         "Ember.ProxyMixin": 1,
@@ -2632,8 +2486,6 @@
         "Ember.Test": 1
       },
       "fors": {
-        "@ember/helper": 1,
-        "Ember.Templates.helpers": 1,
         "Ember": 1,
         "@ember/object": 1
       },
@@ -2650,15 +2502,20 @@
       "name": "@ember/helper",
       "submodules": {},
       "elements": {},
-      "classes": {},
+      "classes": {
+        "Keywords": 1,
+        "@ember/helper": 1,
+        "External": 1
+      },
       "fors": {
-        "Ember.Templates.helpers": 1,
-        "@ember/helper": 1
+        "Keywords": 1,
+        "@ember/helper": 1,
+        "External": 1
       },
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@ember/helper/index.ts",
-      "line": 1
+      "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
+      "line": 249
     },
     "@ember/template": {
       "name": "@ember/template",
@@ -3318,9 +3175,9 @@
       "fors": {},
       "namespaces": {},
       "tag": "module",
-      "file": "packages/@glimmer/component/src/index.ts",
-      "line": 7,
-      "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```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```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```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```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```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```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```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```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```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.",
+      "file": "packages/@glimmer/component/dist/index.d.ts",
+      "line": 3,
+      "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default components for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Template-only and Glimmer components. If you\nare looking for the API documentation for Classic components, it is\n[available here](/ember/release/classes/Component). The source code for\nGlimmer components can be found in [`@glimmer/component`](https://github.com/glimmerjs/glimmer.js/tree/master/packages/%40glimmer/component).\n\n## Defining a Template-only Component\n\nThe simplest way to create a component is to create a template file in\n`app/templates/components`. For example, if you name a template\n`app/templates/components/person-profile.hbs`:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n<img src={{@person.avatar}}>\n<p class='signature'>{{@person.signature}}</p>\n```\n\nYou will be able to use `<PersonProfile />` to invoke this component elsewhere\nin your application:\n\n```app/templates/application.hbs\n<PersonProfile @person={{this.currentUser}} />\n```\n\nNote that component names are capitalized here in order to distinguish them\nfrom regular HTML elements, but they are dasherized in the file system.\n\nWhile the angle bracket invocation form is generally preferred, it is also\npossible to invoke the same component with the `{{person-profile}}` syntax:\n\n```app/templates/application.hbs\n{{person-profile person=this.currentUser}}\n```\n\nNote that with this syntax, you use dashes in the component name and\narguments are passed without the `@` sign.\n\nIn both cases, Ember will render the content of the component template we\ncreated above. The end result will be something like this:\n\n```html\n<h1>Tomster</h1>\n<img src=\"https://emberjs.com/tomster.jpg\">\n<p class='signature'>Out of office this week</p>\n```\n\n## File System Nesting\n\nComponents can be nested inside sub-folders for logical groupping. For\nexample, if we placed our template in\n`app/templates/components/person/short-profile.hbs`, we can invoke it as\n`<Person::ShortProfile />`:\n\n```app/templates/application.hbs\n<Person::ShortProfile @person={{this.currentUser}} />\n```\n\nOr equivalently, `{{person/short-profile}}`:\n\n```app/templates/application.hbs\n{{person/short-profile person=this.currentUser}}\n```\n\n## Using Blocks\n\nYou can use `yield` inside a template to include the **contents** of any block\nattached to the component. For instance, if we added a `{{yield}}` to our\ncomponent like so:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield}}\n```\n\nWe could then invoke it like this:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <p>Admin mode</p>\n</PersonProfile>\n```\n\nor with curly syntax like this:\n\n```handlebars\n{{#person-profile person=this.currentUser}}\n  <p>Admin mode</p>\n{{/person-profile}}\n```\n\nAnd the content passed in between the brackets of the component would be\nrendered in the same place as the `{{yield}}` within it, replacing it.\n\nBlocks are executed in their original context, meaning they have access to the\nscope and any in-scope variables where they were defined.\n\n### Passing parameters to blocks\n\nYou can also pass positional parameters to `{{yield}}`, which are then made\navailable in the block:\n\n```app/templates/components/person-profile.hbs\n<h1>{{@person.name}}</h1>\n{{yield @person.signature}}\n```\n\nWe can then use this value in the block like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n```\n\n### Passing multiple blocks\n\nYou can pass multiple blocks to a component by giving them names, and\nspecifying which block you are yielding to with `{{yield}}`. For instance, if\nwe wanted to add a way for users to customize the title of our\n`<PersonProfile>` component, we could add a named block inside of the header:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield to=\"title\"}}</h1>\n{{yield}}\n```\n\nThis component could then be invoked like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title>{{this.currentUser.name}}</:title>\n  <:default>{{this.currentUser.signature}}</:default>\n</PersonProfile>\n```\n\nWhen passing named blocks, you must name every block, including the `default`\nblock, which is the block that is defined if you do not pass a `to` parameter\nto `{{yield}}`. Whenever you invoke a component without passing explicitly\nnamed blocks, the passed block is considered the `default` block.\n\n### Passing parameters to named blocks\n\nYou can also pass parameters to named blocks:\n\n```app/templates/components/person-profile.hbs\n<h1>{{yield @person.name to=\"title\"}}</h1>\n{{yield @person.signature}}\n```\n\nThese parameters can then be used like so:\n\n```handlebars\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n```\n\n### Checking to see if a block exists\n\nYou can also check to see if a block exists using the `(has-block)` keyword,\nand conditionally use it, or provide a default template instead.\n\n```app/templates/components/person-profile.hbs\n<h1>\n  {{#if (has-block \"title\")}}\n    {{yield @person.name to=\"title\"}}\n  {{else}}\n    {{@person.name}}\n  {{/if}}\n</h1>\n\n{{#if (has-block)}}\n  {{yield @person.signature}}\n{{else}}\n  {{@person.signature}}\n{{/if}}\n```\n\nWith this template, we can then optionally pass in one block, both blocks, or\nnone at all:\n\n```handlebars\n{{! passing both blocks }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n  <:default as |signature|>{{signature}}</:default>\n</PersonProfile>\n\n{{! passing just the title block }}\n<PersonProfile @person={{this.currentUser}}>\n  <:title as |name|>{{name}}</:title>\n</PersonProfile>\n\n{{! passing just the default block }}\n<PersonProfile @person={{this.currentUser}} as |signature|>\n  {{signature}}\n</PersonProfile>\n\n{{! not passing any blocks }}\n<PersonProfile @person={{this.currentUser}}/>\n```\n\n### Checking to see if a block has parameters\n\nWe can also check if a block receives parameters using the `(has-block-params)`\nkeyword, and conditionally yield different values if so.\n\n```app/templates/components/person-profile.hbs\n{{#if (has-block-params)}}\n  {{yield @person.signature}}\n{{else}}\n  {{yield}}\n{{/if}}\n```\n\n## Customizing Components With JavaScript\n\nTo add JavaScript to a component, create a JavaScript file in the same\nlocation as the template file, with the same name, and export a subclass\nof `Component` as the default value. For example, to add Javascript to the\n`PersonProfile` component which we defined above, we would create\n`app/components/person-profile.js` and export our class as the default, like\nso:\n\n```app/components/person-profile.js\nimport Component from '@glimmer/component';\n\nexport default class PersonProfileComponent extends Component {\n  get displayName() {\n    let { title, firstName, lastName } = this.args.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  })\n}\n```\n\nYou can add your own properties, methods, and lifecycle hooks to this\nsubclass to customize its behavior, and you can reference the instance of the\nclass in your template using `{{this}}`. For instance, we could access the\n`displayName` property of our `PersonProfile` component instance in the\ntemplate like this:\n\n```app/templates/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## `constructor`\n\nparams: `owner` object and `args` object\n\nConstructs a new component and assigns itself the passed properties. The\nconstructor is run whenever a new instance of the component is created, and\ncan be used to setup the initial state of the component.\n\n```javascript\nimport Component from '@glimmer/component';\n\nexport default class SomeComponent extends Component {\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.displayMode === 'list') {\n      this.items = [];\n    }\n  }\n}\n```\n\nService injections and arguments are available in the constructor.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  constructor(owner, args) {\n    super(owner, args);\n\n    if (this.args.fadeIn === true) {\n      this.myAnimations.register(this, 'fade-in');\n    }\n  }\n}\n```\n\n## `willDestroy`\n\n`willDestroy` is called after the component has been removed from the DOM, but\nbefore the component is fully destroyed. This lifecycle hook can be used to\ncleanup the component and any related state.\n\n```javascript\nimport Component from '@glimmer/component';\nimport { service } from '@ember/service';\n\nexport default class SomeComponent extends Component {\n  @service myAnimations;\n\n  willDestroy() {\n    super.willDestroy();\n\n    this.myAnimations.unregister(this);\n  }\n}\n```\n\n## `args`\n\nThe `args` property of Glimmer components is an object that contains the\n_arguments_ that are passed to the component. For instance, the\nfollowing component usage:\n\n```handlebars\n<SomeComponent @fadeIn={{true}} />\n```\n\nWould result in the following `args` object to be passed to the component:\n\n```javascript\n{ fadeIn: true }\n```\n\n`args` can be accessed at any point in the component lifecycle, including\n`constructor` and `willDestroy`. They are also automatically marked as tracked\nproperties, and they can be depended on as computed property dependencies:\n\n```javascript\nimport Component from '@glimmer/component';\nimport { computed } from '@ember/object';\n\nexport default class SomeComponent extends Component {\n\n  @computed('args.someValue')\n  get computedGetter() {\n    // updates whenever args.someValue updates\n    return this.args.someValue;\n  }\n\n  get standardGetter() {\n    // updates whenever args.anotherValue updates (Ember 3.13+)\n    return this.args.anotherValue;\n  }\n}\n```\n\n## `isDestroying`\n\nA boolean flag to tell if the component is in the process of destroying. This is set to\ntrue before `willDestroy` is called.\n\n## `isDestroyed`\nA boolean to tell if the component has been fully destroyed. This is set to true\nafter `willDestroy` is called.",
       "access": "public",
       "tagname": ""
     },
@@ -3447,21 +3304,6 @@
       "access": "public",
       "tagname": ""
     },
-    "Ember.Templates.helpers": {
-      "name": "Ember.Templates.helpers",
-      "shortname": "Ember.Templates.helpers",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [],
-      "module": "ember",
-      "namespace": "",
-      "file": "packages/@ember/-internals/glimmer/index.ts",
-      "line": 104,
-      "access": "public",
-      "tagname": ""
-    },
     "@ember/component": {
       "name": "@ember/component",
       "shortname": "@ember/component",
@@ -3473,17 +3315,6 @@
       "module": "@ember/component",
       "namespace": ""
     },
-    "Ember.Templates.components": {
-      "name": "Ember.Templates.components",
-      "shortname": "Ember.Templates.components",
-      "classitems": [],
-      "plugins": [],
-      "extensions": [],
-      "plugin_for": [],
-      "extension_for": [],
-      "module": "@ember/routing",
-      "namespace": ""
-    },
     "@ember/routing": {
       "name": "@ember/routing",
       "shortname": "@ember/routing",
@@ -3495,15 +3326,15 @@
       "module": "@ember/routing",
       "namespace": ""
     },
-    "@ember/helper": {
-      "name": "@ember/helper",
-      "shortname": "@ember/helper",
+    "Keywords": {
+      "name": "Keywords",
+      "shortname": "Keywords",
       "classitems": [],
       "plugins": [],
       "extensions": [],
       "plugin_for": [],
       "extension_for": [],
-      "module": "ember",
+      "module": "@ember/helper",
       "namespace": ""
     },
     "ComponentStateBucket": {
@@ -3579,7 +3410,7 @@
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/component.ts",
       "line": 209,
-      "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript file that shares the same name as the template.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the \n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n## Defining a Classic Component\n\nIf you want to customize the component in order to handle events, transform\narguments or maintain internal state, you implement a subclass of `Component`.\n\nOne example is to add computed properties to your component:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  @computed('person.title', 'person.firstName', 'person.lastName')\n  get displayName() {\n    let { title, firstName, lastName } = this.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  }\n}\n```\n\nAnd then use it in the component's template:\n\n```app/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## Customizing a Classic Component's HTML Element in JavaScript\n\n### HTML Tag\n\nThe default HTML tag name used for a component's HTML representation is `div`.\nThis can be customized by setting the `tagName` property.\n\nConsider the following component class:\n\n```app/components/emphasized-paragraph.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'em';\n}\n```\n\nWhen invoked, this component would produce output that looks something like\nthis:\n\n```html\n<em id=\"ember1\" class=\"ember-view\"></em>\n```\n\n### HTML `class` Attribute\n\nThe HTML `class` attribute of a component's tag can be set by providing a\n`classNames` property that is set to an array of strings:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNames = ['my-class', 'my-other-class'];\n}\n```\n\nInvoking this component will produce output that looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class\"></div>\n```\n\n`class` attribute values can also be set by providing a `classNameBindings`\nproperty set to an array of properties names for the component. The return\nvalue of these properties will be added as part of the value for the\ncomponents's `class` attribute. These properties can be computed properties:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default class extends Component {\n  classNames = ['my-class', 'my-other-class'];\n  classNameBindings = ['propertyA', 'propertyB'];\n\n  propertyA = 'from-a';\n\n  get propertyB {\n    if (someLogic) { return 'from-b'; }\n  }\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nNote that `classNames` and `classNameBindings` is in addition to the `class`\nattribute passed with the angle bracket invocation syntax. Therefore, if this\ncomponent was invoked like so:\n\n```handlebars\n<MyWidget class=\"from-invocation\" />\n```\n\nThe resulting HTML will look similar to this:\n\n```html\n<div id=\"ember1\" class=\"from-invocation ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nIf the value of a class name binding returns a boolean the property name\nitself will be used as the class name if the property is true. The class name\nwill not be added if the value is `false` or `undefined`.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['hovered'];\n\n  hovered = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view hovered\"></div>\n```\n\n### Custom Class Names for Boolean Values\n\nWhen using boolean class name bindings you can supply a string value other\nthan the property name for use as the `class` HTML attribute by appending the\npreferred value after a \":\" character when defining the binding:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['awesome:so-very-cool'];\n\n  awesome = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view so-very-cool\"></div>\n```\n\nBoolean value class name bindings whose property names are in a\ncamelCase-style format will be converted to a dasherized format:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['isUrgent'];\n\n  isUrgent = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view is-urgent\"></div>\n```\n\nClass name bindings can also refer to object values that are found by\ntraversing a path relative to the component itself:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport EmberObject from '@ember/object';\n\nexport default class extends Component {\n  classNameBindings = ['messages.empty'];\n\n  messages = EmberObject.create({\n    empty: true\n  });\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view empty\"></div>\n```\n\nIf you want to add a class name for a property which evaluates to true and and\na different class name if it evaluates to false, you can pass a binding like\nthis:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['isEnabled:enabled:disabled'];\n\n  isEnabled = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view enabled\"></div>\n```\n\nWhen isEnabled is `false`, the resulting HTML representation looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nThis syntax offers the convenience to add a class if a property is `false`:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\n// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false\nexport default class extends Component {\n  classNameBindings = ['isEnabled::disabled'];\n\n  isEnabled = true;\n}\n```\n\nInvoking this component when the `isEnabled` property is true will produce\nHTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view\"></div>\n```\n\nInvoking it when the `isEnabled` property on the component is `false` will\nproduce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nUpdates to the value of a class name binding will result in automatic update\nof the  HTML `class` attribute in the component's rendered HTML\nrepresentation. If the value becomes `false` or `undefined` the class name\nwill be removed.\n\nBoth `classNames` and `classNameBindings` are concatenated properties. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n### Other HTML Attributes\n\nThe HTML attribute section of a component's tag can be set by providing an\n`attributeBindings` property set to an array of property names on the\ncomponent. The return value of these properties will be used as the value of\nthe component's HTML associated attribute:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'a';\n  attributeBindings = ['href'];\n\n  href = 'http://google.com';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nOne property can be mapped on to another by placing a \":\" between the source\nproperty and the destination property:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'a';\n  attributeBindings = ['url:href'];\n\n  url = 'http://google.com';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nHTML attributes passed with angle bracket invocations will take precedence\nover those specified in `attributeBindings`. Therefore, if this component was\ninvoked like so:\n\n```handlebars\n<MyAnchor href=\"http://bing.com\" @url=\"http://google.com\" />\n```\n\nThe resulting HTML will looks like this:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://bing.com\"></a>\n```\n\nNote that the `href` attribute is ultimately set to `http://bing.com`, despite\nit having attribute binidng to the `url` property, which was set to\n`http://google.com`.\n\nNamespaced attributes (e.g. `xlink:href`) are supported, but have to be\nmapped, since `:` is not a valid character for properties in Javascript:\n\n```app/components/my-use.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'use';\n  attributeBindings = ['xlinkHref:xlink:href'];\n\n  xlinkHref = '#triangle';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<use xlink:href=\"#triangle\"></use>\n```\n\nIf the value of a property monitored by `attributeBindings` is a boolean, the\nattribute will be present or absent depending on the value:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'input';\n  attributeBindings = ['disabled'];\n\n  disabled = false;\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<input id=\"ember1\" class=\"ember-view\" />\n```\n\n`attributeBindings` can refer to computed properties:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default class extends Component {\n  tagName = 'input';\n  attributeBindings = ['disabled'];\n\n  get disabled() {\n    if (someLogic) {\n      return true;\n    } else {\n      return false;\n    }\n  }\n};\n```\n\nTo prevent setting an attribute altogether, use `null` or `undefined` as the\nvalue of the property used in `attributeBindings`:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'form';\n  attributeBindings = ['novalidate'];\n  novalidate = null;\n};\n```\n\nUpdates to the property of an attribute binding will result in automatic\nupdate of the  HTML attribute in the component's HTML output.\n\n`attributeBindings` is a concatenated property. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n## Layouts\n\nThe `layout` property can be used to dynamically specify a template associated\nwith a component class, instead of relying on Ember to link together a\ncomponent class and a template based on file names.\n\nIn general, applications should not use this feature, but it's commonly used\nin addons for historical reasons.\n\nThe `layout` property should be set to the default export of a template\nmodule, which is the name of a template file without the `.hbs` extension.\n\n```app/components/person-profile.hbs\n<h1>Person's Title</h1>\n<div class='details'>{{yield}}</div>\n```\n\n```app/components/person-profile.js\n  import Component from '@ember/component';\n  import layout from '../templates/components/person-profile';\n\n  export default class extends Component {\n    layout = layout;\n  }\n```\n\nIf you invoke the component:\n\n```handlebars\n<PersonProfile>\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</PersonProfile>\n```\n\nor\n\n```handlebars\n{{#person-profile}}\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n{{/person-profile}}\n```\n\nIt will result in the following HTML output:\n\n```html\n<h1>Person's Title</h1>\n  <div class=\"details\">\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</div>\n```\n\n## Handling Browser Events\n\nThere are two ways to handle user-initiated events:\n\n### Using the `on` modifier to capture browser events\n\nIn a component's template, you can attach an event handler to any element with the `on` modifier:\n\n```handlebars\n<button {{on 'click' this.doSomething}} />\n```\n\nThis will call the function on your component:\n\n```js\nimport Component from '@ember/component';\n\nexport default class ExampleComponent extends Component {\n  doSomething = (event) => {\n    // `event` is the native click Event\n    console.log('clicked on the button');\n  };\n}\n```\n\nSee the [Guide on Component event\nhandlers](https://guides.emberjs.com/release/components/component-state-and-actions/#toc_html-modifiers-and-actions)\nand the [API docs for `on`](../Ember.Templates.helpers/methods/on?anchor=on)\nfor more details.\n\n### Event Handler Methods\n\nComponents can also respond to user-initiated events by implementing a method\nthat matches the event name. This approach is appropriate when the same event\nshould be handled by all instances of the same component.\n\nAn event object will be passed as the argument to the event handler method.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  click(event) {\n    // `event.target` is either the component's element or one of its children\n    let tag = event.target.tagName.toLowerCase();\n    console.log('clicked on a `<${tag}>` HTML element!');\n  }\n}\n```\n\nIn this example, whenever the user clicked anywhere inside the component, it\nwill log a message to the console.\n\nIt is possible to handle event types other than `click` by implementing the\nfollowing event handler methods. In addition, custom events can be registered\nby using `Application.customEvents`.\n\nTouch events:\n\n* `touchStart`\n* `touchMove`\n* `touchEnd`\n* `touchCancel`\n\nKeyboard events:\n\n* `keyDown`\n* `keyUp`\n* `keyPress`\n\nMouse events:\n\n* `mouseDown`\n* `mouseUp`\n* `contextMenu`\n* `click`\n* `doubleClick`\n* `focusIn`\n* `focusOut`\n\nForm events:\n\n* `submit`\n* `change`\n* `focusIn`\n* `focusOut`\n* `input`\n\nDrag and drop events:\n\n* `dragStart`\n* `drag`\n* `dragEnter`\n* `dragLeave`\n* `dragOver`\n* `dragEnd`\n* `drop`",
+      "description": "A component is a reusable UI element that consists of a `.hbs` template and an\noptional JavaScript class that defines its behavior. For example, someone\nmight make a `button` in the template and handle the click behavior in the\nJavaScript.\n\nComponents are broken down into two categories:\n\n- Components _without_ JavaScript, that are based only on a template. These\n  are called Template-only or TO components.\n- Components _with_ JavaScript, which consist of a template and a backing\n  class.\n\nEmber ships with two types of JavaScript classes for components:\n\n1. Glimmer components, imported from `@glimmer/component`, which are the\n   default component's for Ember Octane (3.15) and more recent editions.\n2. Classic components, imported from `@ember/component`, which were the\n   default for older editions of Ember (pre 3.15).\n\nBelow is the documentation for Classic components. If you are looking for the\nAPI documentation for Template-only or Glimmer components, it is [available\nhere](/ember/release/modules/@glimmer%2Fcomponent).\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\".\nThe documentation for `@ember/component` still refers to the older authoring format. To read about\nthe new authoring format, see the \n[Glimmer Component API documentation](/ember/release/modules/@glimmer%2Fcomponent).\n  \n## Defining a Classic Component\n\nIf you want to customize the component in order to handle events, transform\narguments or maintain internal state, you implement a subclass of `Component`.\n\nOne example is to add computed properties to your component:\n\n```app/components/person-profile.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  @computed('person.title', 'person.firstName', 'person.lastName')\n  get displayName() {\n    let { title, firstName, lastName } = this.person;\n\n    if (title) {\n      return `${title} ${lastName}`;\n    } else {\n      return `${firstName} ${lastName}`;\n    }\n  }\n}\n```\n\nAnd then use it in the component's template:\n\n```app/components/person-profile.hbs\n<h1>{{this.displayName}}</h1>\n{{yield}}\n```\n\n## Customizing a Classic Component's HTML Element in JavaScript\n\n### HTML Tag\n\nThe default HTML tag name used for a component's HTML representation is `div`.\nThis can be customized by setting the `tagName` property.\n\nConsider the following component class:\n\n```app/components/emphasized-paragraph.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'em';\n}\n```\n\nWhen invoked, this component would produce output that looks something like\nthis:\n\n```html\n<em id=\"ember1\" class=\"ember-view\"></em>\n```\n\n### HTML `class` Attribute\n\nThe HTML `class` attribute of a component's tag can be set by providing a\n`classNames` property that is set to an array of strings:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNames = ['my-class', 'my-other-class'];\n}\n```\n\nInvoking this component will produce output that looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class\"></div>\n```\n\n`class` attribute values can also be set by providing a `classNameBindings`\nproperty set to an array of properties names for the component. The return\nvalue of these properties will be added as part of the value for the\ncomponents's `class` attribute. These properties can be computed properties:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default class extends Component {\n  classNames = ['my-class', 'my-other-class'];\n  classNameBindings = ['propertyA', 'propertyB'];\n\n  propertyA = 'from-a';\n\n  get propertyB {\n    if (someLogic) { return 'from-b'; }\n  }\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nNote that `classNames` and `classNameBindings` is in addition to the `class`\nattribute passed with the angle bracket invocation syntax. Therefore, if this\ncomponent was invoked like so:\n\n```handlebars\n<MyWidget class=\"from-invocation\" />\n```\n\nThe resulting HTML will look similar to this:\n\n```html\n<div id=\"ember1\" class=\"from-invocation ember-view my-class my-other-class from-a from-b\"></div>\n```\n\nIf the value of a class name binding returns a boolean the property name\nitself will be used as the class name if the property is true. The class name\nwill not be added if the value is `false` or `undefined`.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['hovered'];\n\n  hovered = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view hovered\"></div>\n```\n\n### Custom Class Names for Boolean Values\n\nWhen using boolean class name bindings you can supply a string value other\nthan the property name for use as the `class` HTML attribute by appending the\npreferred value after a \":\" character when defining the binding:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['awesome:so-very-cool'];\n\n  awesome = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view so-very-cool\"></div>\n```\n\nBoolean value class name bindings whose property names are in a\ncamelCase-style format will be converted to a dasherized format:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['isUrgent'];\n\n  isUrgent = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view is-urgent\"></div>\n```\n\nClass name bindings can also refer to object values that are found by\ntraversing a path relative to the component itself:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\nimport EmberObject from '@ember/object';\n\nexport default class extends Component {\n  classNameBindings = ['messages.empty'];\n\n  messages = EmberObject.create({\n    empty: true\n  });\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view empty\"></div>\n```\n\nIf you want to add a class name for a property which evaluates to true and and\na different class name if it evaluates to false, you can pass a binding like\nthis:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  classNameBindings = ['isEnabled:enabled:disabled'];\n\n  isEnabled = true;\n}\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view enabled\"></div>\n```\n\nWhen isEnabled is `false`, the resulting HTML representation looks like this:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nThis syntax offers the convenience to add a class if a property is `false`:\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\n// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false\nexport default class extends Component {\n  classNameBindings = ['isEnabled::disabled'];\n\n  isEnabled = true;\n}\n```\n\nInvoking this component when the `isEnabled` property is true will produce\nHTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view\"></div>\n```\n\nInvoking it when the `isEnabled` property on the component is `false` will\nproduce HTML that looks like:\n\n```html\n<div id=\"ember1\" class=\"ember-view disabled\"></div>\n```\n\nUpdates to the value of a class name binding will result in automatic update\nof the  HTML `class` attribute in the component's rendered HTML\nrepresentation. If the value becomes `false` or `undefined` the class name\nwill be removed.\n\nBoth `classNames` and `classNameBindings` are concatenated properties. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n### Other HTML Attributes\n\nThe HTML attribute section of a component's tag can be set by providing an\n`attributeBindings` property set to an array of property names on the\ncomponent. The return value of these properties will be used as the value of\nthe component's HTML associated attribute:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'a';\n  attributeBindings = ['href'];\n\n  href = 'http://google.com';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nOne property can be mapped on to another by placing a \":\" between the source\nproperty and the destination property:\n\n```app/components/my-anchor.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'a';\n  attributeBindings = ['url:href'];\n\n  url = 'http://google.com';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://google.com\"></a>\n```\n\nHTML attributes passed with angle bracket invocations will take precedence\nover those specified in `attributeBindings`. Therefore, if this component was\ninvoked like so:\n\n```handlebars\n<MyAnchor href=\"http://bing.com\" @url=\"http://google.com\" />\n```\n\nThe resulting HTML will looks like this:\n\n```html\n<a id=\"ember1\" class=\"ember-view\" href=\"http://bing.com\"></a>\n```\n\nNote that the `href` attribute is ultimately set to `http://bing.com`, despite\nit having attribute binidng to the `url` property, which was set to\n`http://google.com`.\n\nNamespaced attributes (e.g. `xlink:href`) are supported, but have to be\nmapped, since `:` is not a valid character for properties in Javascript:\n\n```app/components/my-use.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'use';\n  attributeBindings = ['xlinkHref:xlink:href'];\n\n  xlinkHref = '#triangle';\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<use xlink:href=\"#triangle\"></use>\n```\n\nIf the value of a property monitored by `attributeBindings` is a boolean, the\nattribute will be present or absent depending on the value:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'input';\n  attributeBindings = ['disabled'];\n\n  disabled = false;\n};\n```\n\nInvoking this component will produce HTML that looks like:\n\n```html\n<input id=\"ember1\" class=\"ember-view\" />\n```\n\n`attributeBindings` can refer to computed properties:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\nimport { computed } from '@ember/object';\n\nexport default class extends Component {\n  tagName = 'input';\n  attributeBindings = ['disabled'];\n\n  get disabled() {\n    if (someLogic) {\n      return true;\n    } else {\n      return false;\n    }\n  }\n};\n```\n\nTo prevent setting an attribute altogether, use `null` or `undefined` as the\nvalue of the property used in `attributeBindings`:\n\n```app/components/my-text-input.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  tagName = 'form';\n  attributeBindings = ['novalidate'];\n  novalidate = null;\n};\n```\n\nUpdates to the property of an attribute binding will result in automatic\nupdate of the  HTML attribute in the component's HTML output.\n\n`attributeBindings` is a concatenated property. See\n[EmberObject](/ember/release/classes/EmberObject) documentation for more\ninformation about concatenated properties.\n\n## Layouts\n\nThe `layout` property can be used to dynamically specify a template associated\nwith a component class, instead of relying on Ember to link together a\ncomponent class and a template based on file names.\n\nIn general, applications should not use this feature, but it's commonly used\nin addons for historical reasons.\n\nThe `layout` property should be set to the default export of a template\nmodule, which is the name of a template file without the `.hbs` extension.\n\n```app/components/person-profile.hbs\n<h1>Person's Title</h1>\n<div class='details'>{{yield}}</div>\n```\n\n```app/components/person-profile.js\n  import Component from '@ember/component';\n  import layout from '../templates/components/person-profile';\n\n  export default class extends Component {\n    layout = layout;\n  }\n```\n\nIf you invoke the component:\n\n```handlebars\n<PersonProfile>\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</PersonProfile>\n```\n\nor\n\n```handlebars\n{{#person-profile}}\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n{{/person-profile}}\n```\n\nIt will result in the following HTML output:\n\n```html\n<h1>Person's Title</h1>\n  <div class=\"details\">\n  <h2>Chief Basket Weaver</h2>\n  <h3>Fisherman Industries</h3>\n</div>\n```\n\n## Handling Browser Events\n\nThere are two ways to handle user-initiated events:\n\n### Using the `on` modifier to capture browser events\n\nIn a component's template, you can attach an event handler to any element with the `on` modifier:\n\n```handlebars\n<button {{on 'click' this.doSomething}} />\n```\n\nThis will call the function on your component:\n\n```js\nimport Component from '@ember/component';\n\nexport default class ExampleComponent extends Component {\n  doSomething = (event) => {\n    // `event` is the native click Event\n    console.log('clicked on the button');\n  };\n}\n```\n\nSee the [Guide on Component event\nhandlers](https://guides.emberjs.com/release/components/component-state-and-actions/#toc_html-modifiers-and-actions)\nand the [API docs for `on`](../functions/Keywords/on)\nfor more details.\n\n### Event Handler Methods\n\nComponents can also respond to user-initiated events by implementing a method\nthat matches the event name. This approach is appropriate when the same event\nshould be handled by all instances of the same component.\n\nAn event object will be passed as the argument to the event handler method.\n\n```app/components/my-widget.js\nimport Component from '@ember/component';\n\nexport default class extends Component {\n  click(event) {\n    // `event.target` is either the component's element or one of its children\n    let tag = event.target.tagName.toLowerCase();\n    console.log('clicked on a `<${tag}>` HTML element!');\n  }\n}\n```\n\nIn this example, whenever the user clicked anywhere inside the component, it\nwill log a message to the console.\n\nIt is possible to handle event types other than `click` by implementing the\nfollowing event handler methods. In addition, custom events can be registered\nby using `Application.customEvents`.\n\nTouch events:\n\n* `touchStart`\n* `touchMove`\n* `touchEnd`\n* `touchCancel`\n\nKeyboard events:\n\n* `keyDown`\n* `keyUp`\n* `keyPress`\n\nMouse events:\n\n* `mouseDown`\n* `mouseUp`\n* `contextMenu`\n* `click`\n* `doubleClick`\n* `focusIn`\n* `focusOut`\n\nForm events:\n\n* `submit`\n* `change`\n* `focusIn`\n* `focusOut`\n* `input`\n\nDrag and drop events:\n\n* `dragStart`\n* `drag`\n* `dragEnter`\n* `dragLeave`\n* `dragOver`\n* `dragEnd`\n* `drop`",
       "extends": "Ember.CoreView",
       "uses": [
         "Ember.TargetActionSupport",
@@ -3611,7 +3442,7 @@
       "namespace": "",
       "file": "packages/@ember/-internals/glimmer/lib/helper.ts",
       "line": 57,
-      "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```app/templates/application.gjs\nimport Cost from '../components/cost';\n  \n<template>\n  <Cost @cents={{230}} />\n</template>\n```\n\n```app/components/cost.gjs\nimport formatCurrency from '../helpers/format-currency';\n  \n<template>\n  <div>{{formatCurrency @cents currency=\"$\"}}</div>\n</template>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```gjs\nimport formatCurrency from '../helpers/format-currency';\n\n<template>\n  {{if @showMoney (formatCurrency @cents currency=\"$\")}}\n</template>\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```app/helpers/format-currency.js\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
+      "description": "Ember Helpers are functions that can compute values, and are used in templates.\nFor example, this code calls a helper named `format-currency`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Cost from '../components/cost';\n  \n<template>\n  <Cost @cents={{230}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/cost.gjs\"}\nimport formatCurrency from '../helpers/format-currency';\n  \n<template>\n  <div>{{formatCurrency @cents currency=\"$\"}}</div>\n</template>\n```\n\nAdditionally a helper can be called as a nested helper.\nIn this example, we show the formatted currency value if the `showMoney`\nnamed argument is truthy.\n\n```gjs\nimport formatCurrency from '../helpers/format-currency';\n\n<template>\n  {{if @showMoney (formatCurrency @cents currency=\"$\")}}\n</template>\n```\n\nHelpers defined using a class must provide a `compute` function. For example:\n\n```app/helpers/format-currency.js\nimport Helper from '@ember/component/helper';\n\nexport default class extends Helper {\n  compute([cents], { currency }) {\n    return `${currency}${cents * 0.01}`;\n  }\n}\n```\n\nEach time the input to a helper changes, the `compute` function will be\ncalled again.\n\nAs instances, these helpers also have access to the container and will accept\ninjected dependencies.\n\nAdditionally, class helpers can call `recompute` to force a new computation.",
       "extends": "CoreObject",
       "access": "public",
       "tagname": "",
@@ -3639,6 +3470,22 @@
       "module": "@ember/renderer",
       "namespace": ""
     },
+    "Ember.Templates.helpers": {
+      "name": "Ember.Templates.helpers",
+      "shortname": "Ember.Templates.helpers",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "ember",
+      "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).",
+      "access": "public",
+      "tagname": ""
+    },
     "Ember": {
       "name": "Ember",
       "shortname": "Ember",
@@ -4579,9 +4426,31 @@
       "access": "private",
       "tagname": ""
     },
-    "Instrumentation": {
-      "name": "Instrumentation",
-      "shortname": "Instrumentation",
+    "@ember/helper": {
+      "name": "@ember/helper",
+      "shortname": "@ember/helper",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "@ember/helper",
+      "namespace": ""
+    },
+    "External": {
+      "name": "External",
+      "shortname": "External",
+      "classitems": [],
+      "plugins": [],
+      "extensions": [],
+      "plugin_for": [],
+      "extension_for": [],
+      "module": "@ember/helper",
+      "namespace": ""
+    },
+    "Instrumentation": {
+      "name": "Instrumentation",
+      "shortname": "Instrumentation",
       "classitems": [],
       "plugins": [],
       "extensions": [],
@@ -4960,7 +4829,7 @@
       "namespace": "",
       "file": "packages/@ember/routing/router-service.ts",
       "line": 28,
-      "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```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.",
+      "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": "",
       "extends": "Service"
@@ -6417,61 +6286,30 @@
       "file": "packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts",
       "line": 113,
       "description": "This \"upgrades\" a route template into a invocable component. Conceptually\nit can be 1:1 for each unique `Template`, but it's also cheap to construct,\nso unless the stability is desirable for other reasons, it's probably not\nworth caching this.",
-      "class": "Ember.Templates.helpers",
+      "class": "@ember/component",
       "module": "rsvp"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/component-managers/unwrap-template.ts",
       "line": 3,
       "deprecated": true,
-      "class": "Ember.Templates.helpers",
+      "class": "@ember/component",
       "module": "rsvp"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/abstract-input.ts",
       "line": 132,
       "description": "The `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
-      "class": "Ember.Templates.helpers",
+      "class": "@ember/component",
       "module": "rsvp"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
       "line": 46,
-      "description": "See [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
-      "itemtype": "method",
-      "name": "input",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Hash"
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 55,
-      "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Input>.\n\nSee [Ember.Templates.components.Input](/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input).",
-      "itemtype": "method",
-      "name": "Input",
-      "see": [
-        "{Ember.Templates.components.Input}"
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "@ember/component",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 67,
       "description": "The `Input` component lets you create an HTML `<input>` element.\n\n```gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <Input @value=\"987\" />\n</template>\n```\n\ncreates an `<input>` element with `type=\"text\"` and value set to 987.\n\n### Text field\n\nIf no `type` argument is specified, a default of type 'text' is used.\n\n```handlebars\nSearch:\n<Input @value={{this.searchWord}} />\n```\n\nIn this example, the initial value in the `<input>` will be set to the value of\n`this.searchWord`. If the user changes the text, the value of `this.searchWord` will also be\nupdated.\n\n### Actions\n\nThe `Input` component takes a number of arguments with callbacks that are invoked in response to\nuser events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-down`\n* `key-press`\n* `key-up`\n\nThese callbacks are passed to `Input` like this:\n\n```handlebars\n<Input @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nStarting with Ember Octane, we recommend using the `{{on}}` modifier to call actions\non specific events, such as the input event.\n\n```handlebars\n<label for=\"input-name\">Name:</label>\n<Input\n  @id=\"input-name\"\n  @value={{this.name}}\n  {{on \"input\" this.validateName}}\n/>\n```\n\nThe event name (e.g. `focusout`, `input`, `keydown`) always follows the casing\nthat the HTML standard uses.\n\n### `<input>` HTML Attributes to Avoid\n\nIn most cases, if you want to pass an attribute to the underlying HTML `<input>` element, you\ncan pass the attribute directly, just like any other Ember component.\n\n```handlebars\n<Input @type=\"text\" size=\"10\" />\n```\n\nIn this example, the `size` attribute will be applied to the underlying `<input>` element in the\noutputted HTML.\n\nHowever, there are a few attributes where you **must** use the `@` version.\n\n* `@type`: This argument is used to control which Ember component is used under the hood\n* `@value`: The `@value` argument installs a two-way binding onto the element. If you wanted a\n  one-way binding, use `<input>` with the `value` property and the `input` event instead.\n* `@checked` (for checkboxes): like `@value`, the `@checked` argument installs a two-way binding\n  onto the element. If you wanted a one-way binding, use `<input type=\"checkbox\">` with\n  `checked` and the `input` event instead.\n\n### Checkbox\n\nTo create an `<input type=\"checkbox\">`:\n\n```handlebars\nEmberize Everything:\n<Input @type=\"checkbox\" @checked={{this.isEmberized}} name=\"isEmberized\" />\n```\n\nThis will bind the checked state of this checkbox to the value of `isEmberized` -- if either one\nchanges, it will be reflected in the other.",
       "itemtype": "method",
       "name": "Input",
+      "static": 1,
       "params": [
         {
           "name": "options",
@@ -6481,71 +6319,44 @@
       ],
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.components",
+      "class": "@ember/component",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 171,
+      "line": 151,
       "description": "The HTML class attribute.",
-      "class": "Ember.Templates.components",
+      "class": "@ember/component",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/input.ts",
-      "line": 182,
+      "line": 162,
       "description": "The HTML type attribute.",
-      "class": "Ember.Templates.components",
+      "class": "@ember/component",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
       "line": 40,
       "description": "The default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
-      "class": "Ember.Templates.components",
+      "class": "@ember/routing",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/internal.ts",
       "line": 53,
       "description": "The default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
-      "class": "Ember.Templates.components",
+      "class": "@ember/routing",
       "module": "@ember/component"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 48,
+      "line": 52,
       "description": "The `LinkTo` component renders a link to the supplied `routeName` passing an optionally\nsupplied model to the route as its `model` context of the route. The block for `LinkTo`\nbecomes the contents of the rendered element:\n\n```gjs\nimport { LinkTo } from '@ember/routing';\n  \n<template>\n  <LinkTo @route='photoGallery'>\n    Great Hamster Photos\n  </LinkTo>\n</template>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos\">\n  Great Hamster Photos\n</a>\n```\n\n### Disabling the `LinkTo` component\n\nThe `LinkTo` component can be disabled by using the `disabled` argument. A disabled link\ndoesn't result in a transition when activated, and adds the `disabled` class to the `<a>`\nelement.\n\n(The class name to apply to the element can be overridden by using the `disabledClass`\nargument)\n\n```handlebars\n<LinkTo @route='photoGallery' @disabled={{true}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\n### Handling `href`\n\n`<LinkTo>` will use your application's Router to fill the element's `href` property with a URL\nthat matches the path to the supplied `routeName`.\n\n### Handling current route\n\nThe `LinkTo` component will apply a CSS class name of 'active' when the application's current\nroute matches the supplied routeName. For example, if the application's current route is\n'photoGallery.recent', then the following invocation of `LinkTo`:\n\n```handlebars\n<LinkTo @route='photoGallery.recent'>\n  Great Hamster Photos\n</LinkTo>\n```\n\nwill result in\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"active\">\n  Great Hamster Photos\n</a>\n```\n\nThe CSS class used for active classes can be customized by passing an `activeClass` argument:\n\n```handlebars\n<LinkTo @route='photoGallery.recent' @activeClass=\"current-url\">\n  Great Hamster Photos\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/this-week\" class=\"current-url\">\n  Great Hamster Photos\n</a>\n```\n\n### Keeping a link active for other routes\n\nIf you need a link to be 'active' even when it doesn't match the current route, you can use the\n`current-when` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @current-when='photos'>\n  Photo Gallery\n</LinkTo>\n```\n\nThis may be helpful for keeping links active for:\n\n* non-nested routes that are logically related\n* some secondary menu approaches\n* 'top navigation' with 'sub navigation' scenarios\n\nA link will be active if `current-when` is `true` or the current\nroute is the route this link would transition to.\n\nTo match multiple routes 'space-separate' the routes:\n\n```handlebars\n<LinkTo @route='gallery' @current-when='photos drawings paintings'>\n  Art Gallery\n</LinkTo>\n```\n\n### Supplying a model\n\nAn optional `model` argument can be used for routes whose\npaths contain dynamic segments. This argument will become\nthe model context of the linked route:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", {path: \"hamster-photos/:photo_id\"});\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{this.aPhoto}}>\n  {{aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\n### Supplying multiple models\n\nFor deep-linking to route paths that contain multiple\ndynamic segments, the `models` argument can be used.\n\nAs the router transitions through the route path, each\nsupplied model argument will become the context for the\nroute with the dynamic segments:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" }, function() {\n    this.route(\"comment\", {path: \"comments/:comment_id\"});\n  });\n});\n```\n\nThis argument will become the model context of the linked route:\n\n```handlebars\n<LinkTo @route='photoGallery.comment' @models={{array this.aPhoto this.comment}}>\n  {{comment.body}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42/comments/718\">\n  A+++ would snuggle again.\n</a>\n```\n\n### Supplying an explicit dynamic segment value\n\nIf you don't have a model object available to pass to `LinkTo`,\nan optional string or integer argument can be passed for routes whose\npaths contain dynamic segments. This argument will become the value\nof the dynamic segment:\n\n```javascript\nRouter.map(function() {\n  this.route(\"photoGallery\", { path: \"hamster-photos/:photo_id\" });\n});\n```\n\n```handlebars\n<LinkTo @route='photoGallery' @model={{aPhotoId}}>\n  {{this.aPhoto.title}}\n</LinkTo>\n```\n\n```html\n<a href=\"/hamster-photos/42\">\n  Tomster\n</a>\n```\n\nWhen transitioning into the linked route, the `model` hook will\nbe triggered with parameters including this passed identifier.\n\n### Supplying query parameters\n\nIf you need to add optional key-value pairs that appear to the right of the ? in a URL,\nyou can use the `query` argument.\n\n```handlebars\n<LinkTo @route='photoGallery' @query={{hash page=1 per_page=20}}>\n  Great Hamster Photos\n</LinkTo>\n```\n\nThis will result in:\n\n```html\n<a href=\"/hamster-photos?page=1&per_page=20\">\n  Great Hamster Photos\n</a>\n```",
       "itemtype": "method",
       "name": "LinkTo",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.components",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 264,
-      "description": "See [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
-      "itemtype": "method",
-      "name": "link-to",
-      "see": [
-        "{Ember.Templates.components.LinkTo}"
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "@ember/routing"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/link-to.ts",
-      "line": 273,
-      "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <LinkTo>.\n\nSee [Ember.Templates.components.LinkTo](/ember/release/classes/Ember.Templates.components/methods/input?anchor=LinkTo).",
-      "itemtype": "method",
-      "name": "LinkTo",
-      "see": [
-        "{Ember.Templates.components.LinkTo}"
-      ],
+      "static": 1,
       "access": "public",
       "tagname": "",
       "class": "@ember/routing",
@@ -6554,37 +6365,10 @@
     {
       "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
       "line": 10,
-      "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```app/components/word-editor.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
-      "itemtype": "method",
-      "name": "Textarea",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.components",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-      "line": 127,
-      "description": "See [Ember.Templates.components.Textarea](/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Textarea)",
-      "itemtype": "method",
-      "name": "textarea",
-      "see": [
-        "{Ember.Templates.components.Textarea}"
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "@ember/component"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/components/textarea.ts",
-      "line": 136,
-      "description": "An opaque interface which can be imported and used in strict-mode\ntemplates to call <Textarea>.\n\nSee [Ember.Templates.components.Textarea](/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Textarea).",
+      "description": "The `Textarea` component inserts a new instance of `<textarea>` tag into the template.\n\nThe `@value` argument provides the content of the `<textarea>`.\n\nThis template:\n\n```handlebars\nimport { Textarea } from '@ember/component';\n\n<template>\n  <Textarea @value=\"A bunch of text\" />\n</template>\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  A bunch of text\n</textarea>\n```\n\nThe `@value` argument is two-way bound. If the user types text into the textarea, the `@value`\nargument is updated. If the `@value` argument is updated, the text in the textarea is updated.\n\nIn the following example, the `writtenWords` property on the component will be updated as the user\ntypes 'Lots of text' into the text area of their browser's window.\n\n```gjs {data-filename=\"app/components/word-editor.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class WordEditorComponent extends Component {\n  @tracked writtenWords = \"Lots of text that IS bound\";\n  \n  <template>\n    <Textarea @value={{writtenWords}} />\n  </template>\n}\n```\n\nWould result in the following HTML:\n\n```html\n<textarea class=\"ember-text-area\">\n  Lots of text that IS bound\n</textarea>\n```\n\nIf you wanted a one way binding, you could use the `<textarea>` element directly, and use the\n`value` DOM property and the `input` event.\n\n### Actions\n\nThe `Textarea` component takes a number of arguments with callbacks that are invoked in\nresponse to user events.\n\n* `enter`\n* `insert-newline`\n* `escape-press`\n* `focus-in`\n* `focus-out`\n* `key-press`\n\nThese callbacks are passed to `Textarea` like this:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\n## Classic Invocation Syntax\n\nThe `Textarea` component can also be invoked using curly braces, just like any other Ember\ncomponent.\n\nFor example, this is an invocation using angle-bracket notation:\n\n```handlebars\n<Textarea @value={{this.searchWord}} @enter={{this.query}} />\n```\n\nYou could accomplish the same thing using classic invocation:\n\n```handlebars\n{{textarea value=this.searchWord enter=this.query}}\n```\n\nThe main difference is that angle-bracket invocation supports any HTML attribute using HTML\nattribute syntax, because attributes and arguments have different syntax when using angle-bracket\ninvocation. Curly brace invocation, on the other hand, only has a single syntax for arguments,\nand components must manually map attributes onto component arguments.\n\nWhen using classic invocation with `{{textarea}}`, only the following attributes are mapped onto\narguments:\n\n* rows\n* cols\n* name\n* selectionEnd\n* selectionStart\n* autocomplete\n* wrap\n* lang\n* dir\n* value\n\n## Classic `layout` and `layoutName` properties\n\nBecause HTML `textarea` elements do not contain inner HTML the `layout` and\n`layoutName` properties will not be applied.",
       "itemtype": "method",
       "name": "Textarea",
-      "see": [
-        "{Ember.Templates.components.Textarea}"
-      ],
+      "static": 1,
       "access": "public",
       "tagname": "",
       "class": "@ember/component",
@@ -6594,353 +6378,133 @@
       "file": "packages/@ember/-internals/glimmer/lib/helpers/-track-array.ts",
       "line": 12,
       "description": "This reference is used to get the `[]` tag of iterables, so we can trigger\nupdates to `{{each}}` when it changes. It is put into place by a template\ntransform at build time, similar to the (-each-in) helper",
-      "class": "@ember/helper",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/array.ts",
-      "line": 5,
-      "description": "Use the `{{array}}` helper to create an array to pass as an option to your\ncomponents.\n\n```handlebars\n<MyComponent @people={{array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson}}\n/>\n```\n or\n```handlebars\n{{yield people=(array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson)\n}}\n```\n\nWould result in an object such as:\n\n```js\n['Tom Dale', 'Yehuda Katz', this.get('myOtherPerson')]\n```\n\nWhere the 3rd item in the array is bound to updates of the `myOtherPerson` property.\n \nThe `array` helper is built-in keyword and does not need to be imported as of v7.1.0.",
-      "itemtype": "method",
-      "name": "array",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Array"
-        }
-      ],
-      "return": {
-        "description": "Array",
-        "type": "Array"
-      },
-      "since": "3.8.0",
-      "access": "public",
-      "tagname": "",
-      "class": "@ember/helper",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/component.ts",
-      "line": 5,
-      "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```app/components/full-name.gjs\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```app/components/person-form.gjs\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```app/components/person-form.gjs\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```app/templates/application.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
-      "itemtype": "method",
-      "name": "component",
-      "since": "1.11.0",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/concat.ts",
-      "line": 5,
-      "description": "Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\nimport { concat } from '@ember/helper';\n  \n<template>\n  {{yield (concat firstName \" \" lastName)}}\n\n  {{! would yield name=\"<first name value> <last name value>\" to the component}}\n</template>\n```\n\nFor invocation of components, you don't need concat at all.\n\n```handlebars\n<SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n```",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "concat",
-      "since": "1.13.0",
-      "class": "@ember/helper",
+      "class": "Keywords",
       "module": "ember"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
       "line": 13,
-      "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\nAssuming the `@developers` argument contains this array:\n\n```javascript\n[{ name: 'Yehuda' },{ name: 'Tom' }, { name: 'Paul' }];\n```\n\n```handlebars\n<ul>\n  {{#each @developers as |person|}}\n    <li>Hello, {{person.name}}!</li>\n  {{/each}}\n</ul>\n```\n\nThe same rules apply to arrays of primitives.\n\n```javascript\n['Yehuda', 'Tom', 'Paul']\n```\n\n```handlebars\n<ul>\n  {{#each @developerNames as |name|}}\n    <li>Hello, {{name}}!</li>\n  {{/each}}\n</ul>\n```\n\nDuring iteration, the index of each item in the array is provided as a second block\nparameter.\n\n```handlebars\n<ul>\n  {{#each @developers as |person index|}}\n    <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n  {{/each}}\n</ul>\n```\n  \n`#each` is a keyword and does not need to be imported. \n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example:\n\n```javascript\npeople.map(person => {\n  return { ...person, type: 'developer' };\n});\n```\n\nIn this case, each time the `people` array is `map`-ed over, it will produce\nan new array with completely different objects between renders. In these cases,\nyou can help Ember determine how these objects related to each other with the\n`key` option:\n\n```handlebars\n<ul>\n  {{#each @developers key=\"name\" as |person|}}\n    <li>Hello, {{person.name}}!</li>\n  {{/each}}\n</ul>\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `@developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```handlebars\n<ul>\n  {{#each @developers as |person|}}\n    <li>{{person.name}} is available!</li>\n  {{else}}\n    <li>Sorry, nobody is available for this task.</li>\n  {{/each}}\n</ul>\n```",
+      "description": "The `{{#each}}` keyword loops over elements in a collection. It is an extension\nof the base Handlebars `{{#each}}` helper.\n\nThe default behavior of `{{#each}}` is to yield its inner block once for every\nitem in an array passing the item as the first block parameter.\n\n```gjs {data-filename=\"app/components/developer-list.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperList extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nThe same rules apply to arrays of primitives:\n\n```gjs {data-filename=\"app/components/developer-names.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperNames extends Component {\n  developerNames = ['Yehuda', 'Tom', 'Paul'];\n\n  <template>\n    <ul>\n      {{#each this.developerNames as |name|}}\n        <li>Hello, {{name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`{{#each}}` also supports native JavaScript [`Set`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)\nvalues and other iterables:\n\n```gjs {data-filename=\"app/components/developer-set.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperSet extends Component {\n  developers = new Set([\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ]);\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nDuring iteration, the index of each item in the array is provided as a second\nblock parameter:\n\n```gjs {data-filename=\"app/components/developer-list-with-index.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperListWithIndex extends Component {\n  developers = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person index|}}\n        <li>Hello, {{person.name}}! You're number {{index}} in line</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\n`#each` is a keyword and does not need to be imported.\n\n### Specifying Keys\n\nIn order to improve rendering speed, Ember will try to reuse the DOM elements\nwhere possible. Specifically, if the same item is present in the array both\nbefore and after the change, its DOM output will be reused.\n\nThe `key` option is used to tell Ember how to determine if the items in the\narray being iterated over with `{{#each}}` has changed between renders. By\ndefault the item's object identity is used.\n\nThis is usually sufficient, so in most cases, the `key` option is simply not\nneeded. However, in some rare cases, the objects' identities may change even\nthough they represent the same underlying data.\n\nFor example, mapping over `people` produces a new array of new objects on each\nrender. Use `key` so Ember can match items across those renders:\n\n```gjs {data-filename=\"app/components/mapped-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class MappedDevelopers extends Component {\n  people = [\n    { name: 'Yehuda' },\n    { name: 'Tom' },\n    { name: 'Paul' },\n  ];\n\n  get developers() {\n    return this.people.map((person) => {\n      return { ...person, type: 'developer' };\n    });\n  }\n\n  <template>\n    <ul>\n      {{#each this.developers key=\"name\" as |person|}}\n        <li>Hello, {{person.name}}!</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```\n\nBy doing so, Ember will use the value of the property specified (`person.name`\nin the example) to find a \"match\" from the previous render. That is, if Ember\nhas previously seen an object from the `developers` array with a matching\nname, its DOM elements will be re-used.\n\nThere are two special values for `key`:\n\n  * `@index` - The index of the item in the array.\n  * `@identity` - The item in the array itself.\n\n### {{else}} condition\n\n`{{#each}}` can have a matching `{{else}}`. The contents of this block will render\nif the collection is empty.\n\n```gjs {data-filename=\"app/components/available-developers.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class AvailableDevelopers extends Component {\n  developers = [];\n\n  <template>\n    <ul>\n      {{#each this.developers as |person|}}\n        <li>{{person.name}} is available!</li>\n      {{else}}\n        <li>Sorry, nobody is available for this task.</li>\n      {{/each}}\n    </ul>\n  </template>\n}\n```",
       "itemtype": "method",
       "name": "each",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/-internals/glimmer/lib/helpers/each-in.ts",
-      "line": 126,
-      "description": "The `{{#each-in}}` keyword loops over properties on an object.\n\nFor example, given this component definition:\n\n```app/components/developer-details.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class extends Component {\n  @tracked developer = {\n    \"name\": \"Shelly Sails\",\n    \"age\": 42\n  };\n  \n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n \n`#each-in` is a keyword and does not need to be imported.",
+      "line": 189,
+      "description": "The `{{#each-in}}` keyword loops over properties on an object, or entries in a\nnative JavaScript [`Map`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map).\n\nFor example, given this component definition:\n\n```gjs {data-filename=\"app/components/developer-details.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nexport default class DeveloperDetails extends Component {\n  @tracked developer = {\n    name: 'Shelly Sails',\n    age: 42,\n  };\n\n  <template>\n    <ul>\n      {{#each-in this.developer as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nThis template would display all properties on the `developer`\nobject in a list, outputting their name and age:\n\n```html\n<ul>\n  <li>name: Shelly Sails</li>\n  <li>age: 42</li>\n</ul>\n```\n\nThe same pattern works with a `Map`:\n\n```gjs {data-filename=\"app/components/developer-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class DeveloperMap extends Component {\n  map = new Map([\n    ['name', 'Shelly Sails'],\n    ['age', 42],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map as |key value|}}\n        <li>{{key}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\nWhen a `Map` uses object keys, you can pass `key=\"@identity\"` to explicitly\ntrack entries across re-renders using the JavaScript identity of each key:\n\n```gjs {data-filename=\"app/components/object-keyed-map.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class ObjectKeyedMap extends Component {\n  map = new Map([\n    [{ name: 'one' }, 'foo'],\n    [{ name: 'two' }, 'bar'],\n  ]);\n\n  <template>\n    <ul>\n      {{#each-in this.map key=\"@identity\" as |key value|}}\n        <li>{{key.name}}: {{value}}</li>\n      {{/each-in}}\n    </ul>\n  </template>\n}\n```\n\n`#each-in` is a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "each-in",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
       "since": "2.1.0",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/element.ts",
-      "line": 84,
-      "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```handlebars\n{{#let (element @tagName) as |Tag|}}\n  <Tag class=\"my-element\">Hello</Tag>\n{{/let}}\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\n\nWhen `@tagName` is an empty string `\"\"`, the block content is rendered without\na wrapping element.\n\nPassing `null`, `undefined`, or non-string values will throw an assertion error.\n\nChanging the tag name will tear down and recreate the element and its contents.\n \nThe `element` helper is built-in and does not need to be imported.",
+      "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
+      "line": 9,
+      "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```gjs {data-filename=\"app/components/my-child.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
       "itemtype": "method",
-      "name": "element",
+      "name": "mut",
+      "params": [
+        {
+          "name": "attr",
+          "description": "the \"two-way\" attribute that can be modified.",
+          "type": "Object",
+          "optional": true
+        }
+      ],
+      "static": 1,
       "access": "public",
       "tagname": "",
-      "class": "Ember.Templates.helpers",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/fn.ts",
-      "line": 5,
-      "description": "The `fn` helper allows you to ensure a function that you are passing off\nto another component, helper, or modifier has access to arguments that are\navailable in the template.\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```app/components/items-listing.gjs\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\n  receive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\n  will receive the `item` from the loop as its first argument and the\n  string `'foo'` as its second argument.\n\nIn the example above, we used `@action` to ensure that `handleSelected` is\nproperly bound to the `items-list`, but let's explore what happens if we\nleft out `@action`:\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\n\nexport default class ItemsList extends Component {\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when `handleSelected` is invoked inside the `display-item`\ncomponent, it will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `fn`!\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n \n`fn` is built-in and does not need to be imported.",
+      "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
+      "line": 9,
+      "description": "The `readonly` helper let's you specify that a binding is one-way only,\ninstead of two-way.\n\nThis is a vestigial helper from the days of `@ember/component` and does not apply to\ncomponents extending from `@glimmer/component`.\n  \nWhen you pass a `readonly` binding from an outer context (e.g. parent component),\nto to an inner context (e.g. child component), you are saying that changing that\nproperty in the inner context does not change the value in the outer context.\n\nTo specify that a binding is read-only, when invoking the child `Component`:\n\n```app/components/my-parent.js\nexport default class MyParent extends Component {\n  totalClicks = 3;\n}\n```\n\nNow, when you update `childClickCount`:\n\n```app/components/my-child.js\nexport default class MyChild extends Component {\n  click() {\n    this.incrementProperty('childClickCount');\n  }\n}\n```\n\nThe value updates in the child component, but not the parent component:\n\n```app/templates/components/my-child.hbs\n{{log childClickCount}} //-> 4\n```\n\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n<MyChild @childClickCount={{readonly totalClicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n{{my-child childClickCount=(readonly totalClicks)}}\n```\n\n### Objects and Arrays\n\nWhen passing a property that is a complex object (e.g. object, array) instead of a primitive object (e.g. number, string),\nonly the reference to the object is protected using the readonly helper.\nThis means that you can change properties of the object both on the parent component, as well as the child component.\nThe `readonly` binding behaves similar to the `const` keyword in JavaScript.\n\nLet's look at an example:\n\nFirst let's set up the parent component:\n\n```app/components/my-parent.js\nimport Component from '@ember/component';\n\nexport default class MyParent extends Component {\n  clicks: null,\n\n  init() {\n    this._super(...arguments);\n    this.set('clicks', { total: 3 });\n  }\n}\n```\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n<MyChild @childClicks={{readonly clicks}} />\n```\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n{{my-child childClicks=(readonly clicks)}}\n```\n\nNow, if you update the `total` property of `childClicks`:\n\n```app/components/my-child.js\nimport Component from '@ember/component';\n\nexport default class MyChild extends Component {\n  click() {\n    this.get('clicks').incrementProperty('total');\n  }\n}\n```\n\nYou will see the following happen:\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n<MyChild @childClicks={{readonly clicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n{{my-child childClicks=(readonly clicks)}}\n```\n\n```app/templates/components/my-child.hbs\n{{log childClicks.total}} //-> 4\n```",
       "itemtype": "method",
-      "name": "fn",
-      "access": "public",
+      "name": "readonly",
+      "params": [
+        {
+          "name": "attr",
+          "description": "the read-only attribute.",
+          "type": "Object",
+          "optional": true
+        }
+      ],
+      "noimport": "",
+      "static": 1,
+      "access": "private",
       "tagname": "",
-      "since": "3.11.0",
-      "class": "@ember/helper",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/get.ts",
-      "line": 5,
-      "description": "Dynamically look up a property on an object or an element in an array.\nThe second argument to `{{get}}` should have a string or number value,\nalthough it can be bound.\n\nFor example, these two usages are equivalent:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n  \n  <template>\n    {{this.developer.name}}\n    {{get this.developer \"name\"}}\n  </template>\n}\n```\n  \nIf there were several facts about a person, the `{{get}}` helper can dynamically\npick one:\n\n```app/templates/application.gjs\nimport DeveloperDetail from '../components/developer-detail';\n\n<template>\n  <DeveloperDetail @factName=\"language\" />\n</template\n```\n\n```handlebars\n{{get this.developer @factName}}\n```\n\nFor a more complex example, this template would allow the user to switch\nbetween showing the user's name and preferred coding language with a click:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n\n  @tracked currentFact = 'name'\n\n  @action\n  showFact(fact) {\n    this.currentFact = fact;\n  }\n  \n  <template>\n    {{get this.developer this.currentFact}}\n\n    <button {{on 'click' (fn this.showFact \"name\")}}>Show name</button>\n    <button {{on 'click' (fn this.showFact \"language\")}}>Show language</button>\n  </template>\n}\n```\n\nThe `{{get}}` helper can also be used for array element access via index.\nThis would display the value of the first element in the array `this.names`:\n\n```handlebars\n{{get this.names 0}}\n```\n\nArray element access also works with a dynamic second argument:\n\n```handlebars\n{{get this.names @index}}\n```",
+      "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
+      "line": 10,
+      "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.\n \n `unbound` is a template keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "unbound",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "itemtype": "method",
-      "name": "get",
-      "since": "2.1.0",
-      "class": "@ember/helper",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/hash.ts",
-      "line": 5,
-      "description": "Use the `{{hash}}` helper to create a hash to pass as an option to your\ncomponents. This is especially useful for contextual components where you can\njust yield a hash:\n\n```handlebars\n{{yield (hash\n   name='Sarah'\n   title=office\n)}}\n```\n\nWould result in an object such as:\n\n```js\n{ name: 'Sarah', title: this.get('office') }\n```\n\nWhere the `title` is bound to updates of the `office` property.\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\n \nThe `hash` helper is a built-in keyword and does not need to be imported as of v7.1.0.",
+      "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
+      "line": 17,
+      "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```hbs\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
       "itemtype": "method",
-      "name": "hash",
+      "name": "mount",
       "params": [
         {
-          "name": "options",
-          "description": "",
-          "type": "Object"
+          "name": "name",
+          "description": "Name of the engine to mount.",
+          "type": "String"
+        },
+        {
+          "name": "model",
+          "description": "Object that will be set as\n                        the model of the engine.",
+          "type": "Object",
+          "optional": true
         }
       ],
-      "return": {
-        "description": "Hash",
-        "type": "Object"
-      },
-      "since": "2.3.0",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "class": "@ember/helper",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/helper.ts",
-      "line": 5,
-      "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
+      "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
+      "line": 32,
+      "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
       "itemtype": "method",
-      "name": "helper",
+      "name": "outlet",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "since": "3.27.0",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts",
-      "line": 5,
-      "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```app/templates/application.gjs\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```app/components/weather.gjs\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```app/components/weather.gjs\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```app/components/weather.gjs\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```app/templates/application.gjs\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "if",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/if-unless.ts",
-      "line": 119,
-      "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```app/templates/application.gjs\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```app/components/greeting.gjs\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```app/components/logged-in.gjs\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```app/templates/application.gjs\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```app/templates/application.gjs\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "unless",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/log.ts",
-      "line": 5,
-      "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```",
-      "itemtype": "method",
-      "name": "log",
-      "params": [
-        {
-          "name": "params",
-          "description": "",
-          "type": "Array"
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/modifier.ts",
-      "line": 5,
-      "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.",
-      "itemtype": "method",
-      "name": "modifier",
-      "access": "public",
-      "tagname": "",
-      "since": "3.27.0",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/mut.ts",
-      "line": 9,
-      "description": "The `mut` helper is a shortcut for updating for args.\n  \nHowever, defining update functions on your backing class is preferable to using `mut`.\n  \nMore directly: Don't use `mut`. \n\nThe `mut` helper, when used with `fn`, will return a function that\nsets the value passed to `mut` to its first argument. As an example, we can create a\nbutton that increments a value passing the value directly to the `fn`:\n\n```handlebars\n<MyChild @childClickCount={{this.totalClicks}} @clickCountChange={{fn (mut this.totalClicks)}} />\n```\n\nThe child `Component` would invoke the function with the new click count:\n\n```app/components/my-child.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n  \nexport default class MyChild extends Component {\n  @action\n  update() {\n    this.args.clickCountChange(this.args.childClickCount + 1);\n  }\n  \n  <template>\n    <button {{on \"click\" this.update}}>\n      Click me!\n    </button>\n  </template>\n}\n```\n\nThe `mut` helper changes the `totalClicks` value to what was provided as the `fn` argument.",
-      "itemtype": "method",
-      "name": "mut",
-      "params": [
-        {
-          "name": "attr",
-          "description": "the \"two-way\" attribute that can be modified.",
-          "type": "Object",
-          "optional": true
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/page-title.ts",
-      "line": 5,
-      "description": "`page-title` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport pageTitle from 'ember-page-title/helpers/page-title';\n\n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
-      "itemtype": "method",
-      "name": "page-title",
-      "params": [
-        {
-          "name": "param",
-          "description": "",
-          "type": "String"
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/readonly.ts",
-      "line": 9,
-      "description": "The `readonly` helper let's you specify that a binding is one-way only,\ninstead of two-way.\n\nThis is a vestigial helper from the days of `@ember/component` and does not apply to\ncomponents extending from `@glimmer/component`.\n  \nWhen you pass a `readonly` binding from an outer context (e.g. parent component),\nto to an inner context (e.g. child component), you are saying that changing that\nproperty in the inner context does not change the value in the outer context.\n\nTo specify that a binding is read-only, when invoking the child `Component`:\n\n```app/components/my-parent.js\nexport default class MyParent extends Component {\n  totalClicks = 3;\n}\n```\n\nNow, when you update `childClickCount`:\n\n```app/components/my-child.js\nexport default class MyChild extends Component {\n  click() {\n    this.incrementProperty('childClickCount');\n  }\n}\n```\n\nThe value updates in the child component, but not the parent component:\n\n```app/templates/components/my-child.hbs\n{{log childClickCount}} //-> 4\n```\n\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n<MyChild @childClickCount={{readonly totalClicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log totalClicks}} //-> 3\n{{my-child childClickCount=(readonly totalClicks)}}\n```\n\n### Objects and Arrays\n\nWhen passing a property that is a complex object (e.g. object, array) instead of a primitive object (e.g. number, string),\nonly the reference to the object is protected using the readonly helper.\nThis means that you can change properties of the object both on the parent component, as well as the child component.\nThe `readonly` binding behaves similar to the `const` keyword in JavaScript.\n\nLet's look at an example:\n\nFirst let's set up the parent component:\n\n```app/components/my-parent.js\nimport Component from '@ember/component';\n\nexport default class MyParent extends Component {\n  clicks: null,\n\n  init() {\n    this._super(...arguments);\n    this.set('clicks', { total: 3 });\n  }\n}\n```\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n<MyChild @childClicks={{readonly clicks}} />\n```\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 3\n{{my-child childClicks=(readonly clicks)}}\n```\n\nNow, if you update the `total` property of `childClicks`:\n\n```app/components/my-child.js\nimport Component from '@ember/component';\n\nexport default class MyChild extends Component {\n  click() {\n    this.get('clicks').incrementProperty('total');\n  }\n}\n```\n\nYou will see the following happen:\n\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n<MyChild @childClicks={{readonly clicks}} />\n```\nor\n```app/templates/components/my-parent.hbs\n{{log clicks.total}} //-> 4\n{{my-child childClicks=(readonly clicks)}}\n```\n\n```app/templates/components/my-child.hbs\n{{log childClicks.total}} //-> 4\n```",
-      "itemtype": "method",
-      "name": "readonly",
-      "params": [
-        {
-          "name": "attr",
-          "description": "the read-only attribute.",
-          "type": "Object",
-          "optional": true
-        }
-      ],
-      "access": "private",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/unbound.ts",
-      "line": 10,
-      "description": "The `{{unbound}}` helper disconnects the one-way binding of a property,\nessentially freezing its value at the moment of rendering. For example,\nin this example the display of the variable `name` will not change even\nif it is set with a new value:\n\n```handlebars\n{{unbound this.name}}\n```\n\nLike any helper, the `unbound` helper can accept a nested helper expression.\nThis allows for custom helpers to be rendered unbound:\n\n```handlebars\n{{unbound (some-custom-helper)}}\n{{unbound (capitalize this.name)}}\n{{! You can use any helper, including unbound, in a nested expression }}\n{{capitalize (unbound this.name)}}\n```\n\nThe `unbound` helper only accepts a single argument, and it return an\nunbound value.",
-      "itemtype": "method",
-      "name": "unbound",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/helpers/unique-id.ts",
-      "line": 5,
-      "description": "Use the {{unique-id}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\n```handlebars\n<input id={{unique-id}} type=\"email\" />\n```\nEach invocation of {{unique-id}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```handlebars\n{{#let (unique-id) as |emailId|}}\n  <label for={{emailId}}>Email address</label>\n  <input id={{emailId}} type=\"email\" />\n{{/let}}\n```",
-      "itemtype": "method",
-      "name": "unique-id",
-      "since": "4.4.0",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/modifiers/on.ts",
-      "line": 5,
-      "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```hbs\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!",
-      "itemtype": "method",
-      "name": "on",
-      "access": "public",
-      "tagname": "",
-      "since": "3.11.0",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/syntax/in-element.ts",
-      "line": 5,
-      "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "in-element",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/syntax/let.ts",
-      "line": 5,
-      "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "let",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/syntax/mount.ts",
-      "line": 17,
-      "description": "The `{{mount}}` helper lets you embed a routeless engine in a template.\nMounting an engine will cause an instance to be booted and its `application`\ntemplate to be rendered.\n\nFor example, the following template mounts the `ember-chat` engine:\n\n```app/templates/application.gjs\n{{mount \"ember-chat\"}}\n```\n\nAdditionally, you can also pass in a `model` argument that will be\nset as the engines model. This can be an existing object:\n\n```hbs\n<div>\n  {{mount 'admin' model=userSettings}}\n</div>\n```\n\nOr an inline `hash`, and you can even pass components:\n\n```gjs\nimport SignInButton from '../components/sign-in-button';\n<template>\n  <div>\n    <h1>Application template!</h1>\n    {{mount 'admin' model=(hash\n        title='Secret Admin'\n        signInButton=SignInButton\n    )}}\n  </div>\n</template>\n```\n \n `mount` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "mount",
-      "params": [
-        {
-          "name": "name",
-          "description": "Name of the engine to mount.",
-          "type": "String"
-        },
-        {
-          "name": "model",
-          "description": "Object that will be set as\n                        the model of the engine.",
-          "type": "Object",
-          "optional": true
-        }
-      ],
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/syntax/outlet.ts",
-      "line": 28,
-      "description": "The `{{outlet}}` helper lets you specify where a child route will render in\nyour template. An important use of the `{{outlet}}` helper is in your\napplication's `application.gjs` file:\n\n```app/templates/application.gjs\nimport MyHeader from '../components/my-header';\nimport MyFooter from '../components/my-footer';\n  \n<template>\n  <MyHeader />\n\n  <div class=\"my-dynamic-content\">\n    <!-- this content will change based on the current route, which depends on the current URL -->\n    {{outlet}}\n  </div>\n\n  <MyFooter />\n</template>\n```\n\nSee the [routing guide](https://guides.emberjs.com/release/routing/rendering-a-template/) for more\ninformation on how your `route` interacts with the `{{outlet}}` helper.\nNote: Your content __will not render__ if there isn't an `{{outlet}}` for it.\n\n`outlet` is built-in and does not need to be imported.",
-      "itemtype": "method",
-      "name": "outlet",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/lib/utils/managers.ts",
-      "line": 7,
-      "description": "Associate a class with a component manager (an object that is responsible for\ncoordinating the lifecycle events that occurs when invoking, rendering and\nre-rendering a component).",
+      "file": "packages/@ember/-internals/glimmer/lib/utils/managers.ts",
+      "line": 7,
+      "description": "Associate a class with a component manager (an object that is responsible for\ncoordinating the lifecycle events that occurs when invoking, rendering and\nre-rendering a component).",
       "itemtype": "method",
       "name": "setComponentManager",
       "params": [
@@ -7960,83 +7524,6 @@
       "class": "Ember.Templates.helpers",
       "module": "@ember/renderer"
     },
-    {
-      "file": "packages/@ember/-internals/glimmer/index.ts",
-      "line": 109,
-      "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```app/templates/application.gjs\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```app/components/labeled-textfield.gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally you can `yield` properties into the context for use by the consumer:\n\n```app/templates/application.gjs\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```app/components/labeled-textfield.gjs\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```app/templates/application.gjs\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```app/components/date-ranges.gjs\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```app/templates/application.gjs\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```app/components/banner.gjs\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```app/components/banner.gjs\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```app/templates/application.gjs\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```app/components/banner/subtitle.gjs\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```app/components/banner/title.gjs\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```",
-      "itemtype": "method",
-      "name": "yield",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Hash"
-        }
-      ],
-      "return": {
-        "description": "HTML string",
-        "type": "String"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/index.ts",
-      "line": 370,
-      "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```app/components/my-component.gjs\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```",
-      "itemtype": "method",
-      "name": "has-block",
-      "params": [
-        {
-          "name": "the",
-          "description": "name of the block. The name (at the moment) is either \"main\" or \"inverse\" (though only curly components support inverse)",
-          "type": "String"
-        }
-      ],
-      "return": {
-        "description": "`true` if the component was invoked with a block",
-        "type": "Boolean"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/index.ts",
-      "line": 407,
-      "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\nHi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\nHi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```app/components/my-component.gjs\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
-      "itemtype": "method",
-      "name": "has-block-params",
-      "params": [
-        {
-          "name": "the",
-          "description": "name of the block. The name (at the moment) is either \"main\" or \"inverse\" (though only curly components support inverse)",
-          "type": "String"
-        }
-      ],
-      "return": {
-        "description": "`true` if the component was invoked with block params",
-        "type": "Boolean"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
-    {
-      "file": "packages/@ember/-internals/glimmer/index.ts",
-      "line": 448,
-      "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
-      "itemtype": "method",
-      "name": "debugger",
-      "access": "public",
-      "tagname": "",
-      "class": "Ember.Templates.helpers",
-      "module": "ember"
-    },
     {
       "file": "packages/@ember/-internals/meta/lib/meta.ts",
       "line": 91,
@@ -13941,6 +13428,7 @@
         "description": "The capabilities object instance",
         "type": "Capabilities"
       },
+      "since": "3.23.0",
       "access": "public",
       "tagname": "",
       "class": "@ember/helper",
@@ -13948,7 +13436,7 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 80,
+      "line": 81,
       "description": "Sets the helper manager for an object or function.\n\n```js\nsetHelperManager((owner) => new ClassHelperManager(owner), Helper)\n```\n\nWhen a value is used as a helper in a template, the helper manager is looked up\non the object by walking up its prototype chain and finding the first helper\nmanager. This manager then receives the value and can create and manage an\ninstance of a helper from it. This provides a layer of indirection that allows\nusers to design high-level helper APIs, without Ember needing to worry about the\ndetails. High-level APIs can be experimented with and iterated on while the\ncore of Ember helpers remains stable, and new APIs can be introduced gradually\nover time to existing code bases.\n\n`setHelperManager` receives two arguments:\n\n1. A factory function, which receives the `owner` and returns an instance of a\n  helper manager.\n2. A helper definition, which is the object or function to associate the factory function with.\n\nThe first time the object is looked up, the factory function will be called to\ncreate the helper manager. It will be cached, and in subsequent lookups the\ncached helper manager will be used instead.\n\nOnly one helper manager is guaranteed to exist per `owner` and per usage of\n`setHelperManager`, so many helpers will end up using the same instance of the\nhelper manager. As such, you should only store state that is related to the\nmanager itself. If you want to store state specific to a particular helper\ndefinition, you should assign a unique helper manager to that helper. In\ngeneral, most managers should either be stateless, or only have the `owner` they\nwere created with as state.\n\nHelper managers must fulfill the following interface (This example uses\n[TypeScript interfaces](https://www.typescriptlang.org/docs/handbook/interfaces.html)\nfor precision, you do not need to write helper managers using TypeScript):\n\n```ts\ninterface HelperManager<HelperStateBucket> {\n  capabilities: HelperCapabilities;\n\n  createHelper(definition: HelperDefinition, args: TemplateArgs): HelperStateBucket;\n\n  getValue?(bucket: HelperStateBucket): unknown;\n\n  runEffect?(bucket: HelperStateBucket): void;\n\n  getDestroyable?(bucket: HelperStateBucket): object;\n}\n```\n\nThe capabilities property _must_ be provided using the `capabilities()` function\nimported from the same module as `setHelperManager`:\n\n```js\nimport { capabilities } from '@ember/helper';\n\nclass MyHelperManager {\n  capabilities = capabilities('3.21.0', { hasValue: true });\n\n  // ...snip...\n}\n```\n\nBelow is a description of each of the methods on the interface and their\nfunctions.\n\n#### `createHelper`\n\n`createHelper` is a required hook on the HelperManager interface. The hook is\npassed the definition of the helper that is currently being created, and is\nexpected to return a _state bucket_. This state bucket is what represents the\ncurrent state of the helper, and will be passed to the other lifecycle hooks at\nappropriate times. It is not necessarily related to the definition of the\nhelper itself - for instance, you could return an object _containing_ an\ninstance of the helper:\n\n```js\nclass MyManager {\n  createHelper(Definition, args) {\n    return {\n      instance: new Definition(args);\n    };\n  }\n}\n```\n\nThis allows the manager to store metadata that it doesn't want to expose to the\nuser.\n\nThis hook is _not_ autotracked - changes to tracked values used within this hook\nwill _not_ result in a call to any of the other lifecycle hooks. This is because\nit is unclear what should happen if it invalidates, and rather than make a\ndecision at this point, the initial API is aiming to allow as much expressivity\nas possible. This could change in the future with changes to capabilities and\ntheir behaviors.\n\nIf users do want to autotrack some values used during construction, they can\neither create the instance of the helper in `runEffect` or `getValue`, or they\ncan use the `cache` API to autotrack the `createHelper` hook themselves. This\nprovides maximum flexibility and expressiveness to manager authors.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called as discovered during DOM construction\n- called in definition order in the template\n\n#### `getValue`\n\n`getValue` is an optional hook that should return the value of the helper. This\nis the value that is returned from the helper and passed into the template.\n\nThis hook is called when the value is requested from the helper (e.g. when the\ntemplate is rendering and the helper value is needed). The hook is autotracked,\nand will rerun whenever any tracked values used inside of it are updated.\nOtherwise it does not rerun.\n\n> Note: This means that arguments which are not _consumed_ within the hook will\n> not trigger updates.\n\nThis hook is only called for helpers with the `hasValue` capability enabled.\nThis hook has the following timing semantics:\n\n**Always**\n- called the first time the helper value is requested\n- called after autotracked state has changed\n\n**Never**\n- called if the `hasValue` capability is disabled\n\n#### `runEffect`\n\n`runEffect` is an optional hook that should run the effect that the helper is\napplying, setting it up or updating it.\n\nThis hook is scheduled to be called some time after render and prior to paint.\nThere is not a guaranteed, 1-to-1 relationship between a render pass and this\nhook firing. For instance, multiple render passes could occur, and the hook may\nonly trigger once. It may also never trigger if it was dirtied in one render\npass and then destroyed in the next.\n\nThe hook is autotracked, and will rerun whenever any tracked values used inside\nof it are updated. Otherwise it does not rerun.\n\nThe hook is also run during a time period where state mutations are _disabled_\nin Ember. Any tracked state mutation will throw an error during this time,\nincluding changes to tracked properties, changes made using `set`, updates\nto computed properties, etc. This is meant to prevent infinite rerenders and\nother antipatterns.\n\nThis hook is only called for helpers with the `hasScheduledEffect` capability\nenabled. This hook is also not called in SSR currently, though this could be\nadded as a capability in the future. It has the following timing semantics:\n\n**Always**\n- called after the helper was first created, if the helper has not been\n  destroyed since creation\n- called after autotracked state has changed, if the helper has not been\n  destroyed during render\n\n**Never**\n- called if the `hasScheduledEffect` capability is disabled\n- called in SSR\n\n#### `getDestroyable`\n\n`getDestroyable` is an optional hook that users can use to register a\ndestroyable object for the helper. This destroyable will be registered to the\ncontaining block or template parent, and will be destroyed when it is destroyed.\nSee the [Destroyables RFC](https://github.com/emberjs/rfcs/blob/master/text/0580-destroyables.md)\nfor more details.\n\n`getDestroyable` is only called if the `hasDestroyable` capability is enabled.\n\nThis hook has the following timing semantics:\n\n**Always**\n- called immediately after the `createHelper` hook is called\n\n**Never**\n- called if the `hasDestroyable` capability is disabled",
       "itemtype": "method",
       "name": "setHelperManager",
@@ -13969,6 +13457,7 @@
         "description": "The definition passed into setHelperManager",
         "type": "Object"
       },
+      "since": "3.23.0",
       "access": "public",
       "tagname": "",
       "class": "@ember/helper",
@@ -13976,8 +13465,8 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 274,
-      "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```js\n// app/components/data-loader.js\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n```\n```js\n{{this.value}}\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
+      "line": 276,
+      "description": "The `invokeHelper` function can be used to create a helper instance in\nJavaScript.\n\nTo access a helper's value you have to use `getValue` from\n`@glimmer/tracking/primitives/cache`.\n\n```gjs {data-filename=\"app/components/data-loader.js\"}\nimport Component from '@glimmer/component';\nimport { getValue } from '@glimmer/tracking/primitives/cache';\nimport Helper from '@ember/component/helper';\nimport { invokeHelper } from '@ember/helper';\n\nclass PlusOne extends Helper {\n  compute([number]) {\n    return number + 1;\n  }\n}\n\nexport default class PlusOneComponent extends Component {\n  plusOne = invokeHelper(this, PlusOne, () => {\n    return {\n      positional: [this.args.number],\n    };\n  });\n\n  get value() {\n    return getValue(this.plusOne);\n  }\n}\n\n<template>\n  {{this.value}}\n</template>\n```\n\nIt receives three arguments:\n\n* `context`: The parent context of the helper. When the parent is torn down and\n  removed, the helper will be as well.\n* `definition`: The definition of the helper.\n* `computeArgs`: An optional function that produces the arguments to the helper.\n  The function receives the parent context as an argument, and must return an\n  object with a `positional` property that is an array and/or a `named`\n  property that is an object.\n\nAnd it returns a Cache instance that contains the most recent value of the\nhelper. You can access the helper using `getValue()` like any other cache. The\ncache is also destroyable, and using the `destroy()` function on it will cause\nthe helper to be torn down.\n\nNote that using `getValue()` on helpers that have scheduled effects will not\ntrigger the effect early. Effects will continue to run at their scheduled time.",
       "itemtype": "method",
       "name": "invokeHelper",
       "static": 1,
@@ -14001,6 +13490,7 @@
       "return": {
         "description": ""
       },
+      "since": "3.23.0",
       "access": "public",
       "tagname": "",
       "class": "@ember/helper",
@@ -14008,43 +13498,100 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 346,
-      "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```",
-      "class": "@ember/helper",
-      "module": "@ember/helper"
-    },
-    {
-      "file": "packages/@ember/helper/index.ts",
-      "line": 361,
-      "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```js\n\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```",
-      "class": "@ember/helper",
+      "line": 349,
+      "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```\n\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```\nThe `hash` helper is available as a keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "hash",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "noimport": "",
+      "params": [
+        {
+          "name": "options",
+          "description": "",
+          "type": "Object"
+        }
+      ],
+      "return": {
+        "description": "Hash",
+        "type": "Object"
+      },
+      "since": "2.3.0",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 379,
-      "description": "The `{{concat}}` helper makes it easy to dynamically send a number of\nparameters to a component or helper as a single parameter in the format of a\nconcatenated string.\n\nFor example:\n\n```js\nimport { concat } from '@ember/helper';\n\n<template>\n  {{get @foo (concat \"item\" @index)}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
-      "class": "@ember/helper",
+      "line": 386,
+      "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```gjs\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```\n\nThe `array` helper is available as a keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "array",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "noimport": "",
+      "params": [
+        {
+          "name": "options",
+          "description": "",
+          "type": "Array"
+        }
+      ],
+      "return": {
+        "description": "Array",
+        "type": "Array"
+      },
+      "since": "3.8.0",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 400,
-      "description": "The `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
+      "line": 414,
+      "description": "The `{{concat}}` helper Concatenates the given arguments into a string.\n\nExample:\n\n```gjs\n import { concat } from '@ember/helper';\n\n <template>\n   {{yield (concat firstName \" \" lastName)}}\n\n   {{! would yield name=\"<first name value> <last name value>\" to the component}}\n </template>\n ```\n\n or for angle bracket invocation, you actually don't need concat at all:\n\n ```handlebars\n <SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n ```",
+      "itemtype": "method",
+      "name": "concat",
+      "exampleimport": "import { concat } from '@ember/helper';",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "since": "1.13.0",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 441,
-      "description": "`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```js\nimport { fn } from '@ember/helper';\n\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```",
+      "line": 445,
+      "description": "The `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```gjs\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
+      "itemtype": "method",
+      "name": "get",
+      "since": "2.1.0",
+      "exampleimport": "import { get } from '@ember/helper';",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 463,
-      "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```js\nimport { gt } from '@ember/helper';\n\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `gt` is available as a keyword and\ndoes not need to be imported.",
+      "line": 493,
+      "description": "`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```gjs\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```gjs {data-filename=\"app/components/items-listing.gjs\"}\n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```gjs {data-filename=\"app/components/items-list.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  @action\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take a look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\nreceive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\nwill receive the `item` from the loop as its first argument and the\nstring `'foo'` as its second argument.\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\nThe `fn` helper is available as a keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "fn",
+      "noimport": "",
+      "access": "public",
+      "tagname": "",
+      "since": "3.11.0",
+      "static": 1,
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 562,
+      "description": "The `{{gt}}` helper returns `true` if the first argument is greater than\nthe second argument.\n\n```gjs\n<template>\n  {{if (gt @score 100) \"High score!\" \"Keep trying\"}}\n</template>\n```\n\nThe `gt` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "gt",
       "params": [
@@ -14063,13 +13610,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "since": "7.1.0",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 486,
-      "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```js\nimport { gte } from '@ember/helper';\n\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `gte` is available as a keyword and\ndoes not need to be imported.",
+      "line": 587,
+      "description": "The `{{gte}}` helper returns `true` if the first argument is greater than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (gte @age 18) \"Adult\" \"Minor\"}}\n</template>\n```\n\nThe `gte` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "gte",
       "params": [
@@ -14088,13 +13640,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "since": "7.1.0",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 509,
-      "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```js\nimport { lt } from '@ember/helper';\n\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `lt` is available as a keyword and\ndoes not need to be imported.",
+      "line": 612,
+      "description": "The `{{lt}}` helper returns `true` if the first argument is less than\nthe second argument.\n\n```gjs\n<template>\n  {{if (lt @temperature 0) \"Freezing\" \"Above zero\"}}\n</template>\n```\n\nThe `lt` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "lt",
       "params": [
@@ -14113,13 +13670,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "since": "7.1.0",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 532,
-      "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```js\nimport { lte } from '@ember/helper';\n\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `lte` is available as a keyword and\ndoes not need to be imported.",
+      "line": 637,
+      "description": "The `{{lte}}` helper returns `true` if the first argument is less than\nor equal to the second argument.\n\n```gjs\n<template>\n  {{if (lte @count 0) \"Empty\" \"Has items\"}}\n</template>\n```\n\nThe `lte` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "lte",
       "params": [
@@ -14138,13 +13700,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "since": "7.1.0",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 555,
-      "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```js\nimport { element } from '@ember/helper';\n\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.",
+      "line": 662,
+      "description": "The `element` helper lets you dynamically set the tag name of an element.\n\n```gjs\n<template>\n  {{#let (element @tagName) as |Tag|}}\n    <Tag class=\"my-element\">Hello</Tag>\n  {{/let}}\n</template>\n```\n\nWhen `@tagName` is `\"h1\"`, this renders `<h1 class=\"my-element\">Hello</h1>`.\nWhen `@tagName` is an empty string, the block content is rendered without a\nwrapping element. When `@tagName` is `null` or `undefined`, nothing is rendered.\n\nThe `element` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "element",
       "params": [
@@ -14154,20 +13721,32 @@
           "type": "String"
         }
       ],
-      "class": "@ember/helper",
+      "noimport": "",
+      "since": "7.1.0",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 578,
-      "description": "Use the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```js\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
+      "line": 690,
+      "description": "Use the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```gjs\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
+      "itemtype": "method",
+      "name": "uniqueId",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "exampleimport": "import { uniqueId } from '@ember/helper';",
+      "since": "4.4.0",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 599,
-      "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```js\nimport { eq } from '@ember/helper';\n\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `eq` is available as a keyword and\ndoes not need to be imported.",
+      "line": 718,
+      "description": "The `{{eq}}` helper returns `true` if its two arguments are strictly equal\n(`===`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (eq @status \"active\") \"Active\" \"Inactive\"}}\n</template>\n```\n\nThe `eq` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "eq",
       "params": [
@@ -14186,13 +13765,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "static": 1,
+      "since": "7.1.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 622,
-      "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```js\nimport { neq } from '@ember/helper';\n\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `neq` is available as a keyword and\ndoes not need to be imported.",
+      "line": 743,
+      "description": "The `{{neq}}` helper returns `true` if its two arguments are strictly\nnot equal (`!==`). Takes exactly two arguments.\n\n```gjs\n<template>\n  {{if (neq @status \"active\") \"Not active\" \"Active\"}}\n</template>\n```\n\nThe `neq` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "neq",
       "params": [
@@ -14211,13 +13795,18 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "static": 1,
+      "since": "7.1.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 645,
-      "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```js\nimport { and } from '@ember/helper';\n\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `and` is available as a keyword and\ndoes not need to be imported.",
+      "line": 768,
+      "description": "The `{{and}}` helper evaluates arguments left to right, returning the first\nfalsy value (using Handlebars truthiness) or the right-most value if all\nare truthy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (and @isAdmin @isLoggedIn) \"Welcome, admin!\" \"Access denied\"}}\n</template>\n```\n\nThe `and` helper is available as a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "and",
       "params": [
@@ -14231,13 +13820,18 @@
         "description": "The first falsy value or the last value",
         "type": "Unknown"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "static": 1,
+      "since": "7.1.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 668,
-      "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```js\nimport { or } from '@ember/helper';\n\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
+      "line": 793,
+      "description": "The `{{or}}` helper evaluates arguments left to right, returning the first\ntruthy value (using Handlebars truthiness) or the right-most value if all\nare falsy. Requires at least two arguments.\n\n```gjs\n<template>\n  {{if (or @hasAccess @isAdmin) \"Welcome!\" \"No access\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `or` is available as a keyword and\ndoes not need to be imported.",
       "itemtype": "method",
       "name": "or",
       "params": [
@@ -14251,13 +13845,18 @@
         "description": "The first truthy value or the last value",
         "type": "Unknown"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "static": 1,
+      "since": "7.1.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 691,
-      "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```js\nimport { not } from '@ember/helper';\n\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
+      "line": 819,
+      "description": "The `{{not}}` helper returns the logical negation of its argument using\nHandlebars truthiness. Takes exactly one argument.\n\n```gjs\n<template>\n  {{if (not @isDisabled) \"Enabled\" \"Disabled\"}}\n</template>\n```\n\nIn strict-mode (gjs/gts) templates, `not` is available as a keyword and\ndoes not need to be imported.",
       "itemtype": "method",
       "name": "not",
       "params": [
@@ -14271,155 +13870,389 @@
         "description": "",
         "type": "Boolean"
       },
-      "class": "@ember/helper",
+      "noimport": "",
+      "static": 1,
+      "since": "7.1.0",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
       "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/instrumentation/index.ts",
-      "line": 107,
-      "description": "Notifies event's subscribers, calls `before` and `after` hooks.",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 844,
+      "description": "`{{yield}}` denotes an area of a template that will be rendered inside\nof another template.\n\n### Use with `Component`\n\nWhen designing components, `{{yield}}` is used to denote where, inside the component's\ntemplate, an optional block passed to the component should render:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LabeledTextField from '../components/labeled-textfield';\n  \n<template>\n  <LabeledTextField @value={{@model.name}}>\n    First name:\n  </LabeledTextField>\n</template>\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  First name: <input type=\"text\" />\n</label>\n```\n\nAdditionally, you can `yield` properties into the context for use by the consumer:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport LabeledTextField from '../components/labeled-textfield';\n  \nexport default class Application extends Component {\n  firstNameValidator = (value) => {\n    // validates\n  }\n  \n  <template>\n    <LabeledTextField @value={{@model.validation}} @validator={{this.firstNameValidator}} as |validationError|>\n      {{#if validationError}}\n        <p class=\"error\">{{validationError}}</p>\n      {{/if}}\n      First name:\n    </LabeledTextField>\n  </template>\n}\n```\n\n```gjs {data-filename=\"app/components/labeled-textfield.gjs\"}\nimport { Input } from '@ember/component';\n  \n<template>\n  <label>\n    {{yield this.validationError}} <Input @value={{@value}} />\n  </label>\n</template>\n```\n\nResult:\n\n```html\n<label>\n  <p class=\"error\">First Name must be at least 3 characters long.</p>\n  First name: <input type=\"text\" />\n</label>\n```\n\n`yield` can also be used with the `hash` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport DateRanges from '../components/date-ranges';\n  \n<template>\n  <DateRanges @value={{@model.date}} as |range|>\n    Start date: {{range.start}}\n    End date: {{range.end}}\n  </DateRanges>\n</template>\n```\n\n```gjs {data-filename=\"app/components/date-ranges.gjs\"}\n<template>\n  <div>\n    {{yield (hash start=@value.start end=@value.end)}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  Start date: July 1st\n  End date: July 30th\n</div>\n```\n\nMultiple values can be yielded as block params:\n  \n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n  \n<template>\n  <Banner @value={{@model}} as |title subtitle body|>\n    <h1>{{title}}</h1>\n    <h2>{{subtitle}}</h2>\n    {{body}}\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\n<template>\n  <div>\n    {{yield \"Hello title\" \"hello subtitle\" \"body text\"}}\n  </div>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h1>Hello title</h1>\n  <h2>hello subtitle</h2>\n  body text\n</div>\n```\n\nHowever, it is preferred to use the hash helper, as this can prevent breaking changes to your component and also simplify the api for the component.\n\nMultiple components can be yielded with the `hash` and `component` helper:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner.gjs\"}\nimport Title from './banner/title';\nimport Subtitle from './banner/subtitle';\nimport Body from './banner/body';\n\nexport default class Banner extends Component {\n  Title = Title;\n  Subtitle = Subtitle;\n  Body = Body;\n  \n  <template>\n    <div>\n      {{yield (hash\n        Title=this.Title\n        Subtitle=this.Subtitle\n        Body=(component this.Body defaultArg=\"some value\")\n      )}}\n    </div>\n  </template>\n}\n```\n\nResult:\n\n```html\n<div>\n  <h1>Banner title</h1>\n  <h2>Banner subtitle</h2>\n  A load of body text\n</div>\n```\n\nA benefit of using this pattern is that the user of the component can change the order the components are displayed.\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle>Banner subtitle</banner.Subtitle>\n    <banner.Title>Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2>Banner subtitle</h2>\n  <h1>Banner title</h1>\n  A load of body text\n</div>\n```\n\nAnother benefit to using `yield` with the `hash` and `component` helper\nis you can pass attributes and arguments to these components:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Banner from '../components/banner';\n\n<template>\n  <Banner @value={{@model}} as |banner|>\n    <banner.Subtitle class=\"mb-1\">Banner subtitle</banner.Subtitle>\n    <banner.Title @variant=\"loud\">Banner title</banner.Title>\n    <banner.Body>A load of body text</banner.Body>\n  </Banner>\n</template>\n```\n\n```gjs {data-filename=\"app/components/banner/subtitle.gjs\"}\n{{!-- note the use of ..attributes --}}\n<h2 ...attributes>\n  {{yield}}\n</h2>\n```\n\n```gjs {data-filename=\"app/components/banner/title.gjs\"}\n<template>\n  {{#if (eq @variant \"loud\")}}\n    <h1 class=\"loud\">{{yield}}</h1>\n  {{else}}\n    <h1 class=\"quiet\">{{yield}}</h1>\n  {{/if}}\n</template>\n```\n\nResult:\n\n```html\n<div>\n  <h2 class=\"mb-1\">Banner subtitle</h2>\n  <h1 class=\"loud\">Banner title</h1>\n  A load of body text\n</div>\n```\n\n`yield` is available as a keyword and does not need to be imported.",
       "itemtype": "method",
-      "name": "instrument",
-      "static": 1,
+      "name": "yield",
       "params": [
         {
-          "name": "name",
-          "description": "Namespaced event name.",
-          "type": "String",
-          "optional": true
-        },
-        {
-          "name": "payload",
+          "name": "options",
           "description": "",
-          "type": "Object"
-        },
-        {
-          "name": "callback",
-          "description": "Function that you're instrumenting.",
-          "type": "Function"
-        },
-        {
-          "name": "binding",
-          "description": "Context that instrument function is called with.",
-          "type": "Object"
+          "type": "Hash"
         }
       ],
-      "access": "private",
+      "return": {
+        "description": "HTML string",
+        "type": "String"
+      },
+      "static": 1,
+      "noimport": "",
+      "access": "public",
       "tagname": "",
-      "class": "@ember/instrumentation",
-      "module": "@ember/instrumentation"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/instrumentation/index.ts",
-      "line": 260,
-      "description": "Subscribes to a particular event or instrumented block of code.",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1109,
+      "description": "`{{(has-block)}}` indicates if the component was invoked with a block.\n\nThis component is invoked with a block:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis component is invoked without a block:\n\n```handlebars\n<MyComponent />\n```\n\nThis is useful when you want to create a component that can optionally take a block\nand then render a default template when it is not invoked with a block.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block)}}\n    Welcome {{yield}}, we are happy you're here!\n  {{else}}\n    Hey you! You're great!\n  {{/if}}\n</template>\n```\n\n`has-block` is available as a keyword and does not need to be imported.",
       "itemtype": "method",
-      "name": "subscribe",
-      "static": 1,
+      "name": "has-block",
       "params": [
         {
-          "name": "pattern",
-          "description": "Namespaced event name.",
-          "type": "String",
-          "optional": true
-        },
-        {
-          "name": "object",
-          "description": "Before and After hooks.",
-          "type": "Object",
-          "optional": true
+          "name": "blockName",
+          "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+          "type": "String"
         }
       ],
       "return": {
-        "description": "",
-        "type": "Subscriber"
+        "description": "`true` if the component was invoked with a block",
+        "type": "Boolean"
       },
-      "access": "private",
+      "static": 1,
+      "noimport": "",
+      "access": "public",
       "tagname": "",
-      "class": "@ember/instrumentation",
-      "module": "@ember/instrumentation"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/instrumentation/index.ts",
-      "line": 300,
-      "description": "Unsubscribes from a particular event or instrumented block of code.",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1150,
+      "description": "`{{(has-block-params)}}` indicates if the component was invoked with block params.\n\nThis component is invoked with block params:\n  \n```handlebars\n<MyComponent as |favoriteFlavor|>\n  Hi Jen!\n</MyComponent>\n```\n\nAnd without block params:\n\n```handlebars\n<MyComponent>\n  Hi Jen!\n</MyComponent>\n```\n\nThis is useful when you want to create a component that can render itself\ndifferently when it is not invoked with block params.\n\n```gjs {data-filename=\"app/components/my-component.gjs\"}\n<template>\n  {{#if (has-block-params)}}\n    Welcome {{yield this.favoriteFlavor}}, we're happy you're here and hope you\n    enjoy your favorite ice cream flavor.\n  {{else}}\n    Welcome {{yield}}, we're happy you're here, but we're unsure what\n    flavor ice cream you would enjoy.\n  {{/if}}\n</template>\n```",
       "itemtype": "method",
-      "name": "unsubscribe",
+      "name": "has-block-params",
       "static": 1,
+      "noimport": "",
       "params": [
         {
-          "name": "subscriber",
-          "description": "",
-          "type": "Object",
-          "optional": true
+          "name": "blockName",
+          "description": "the name of the block. The name is either \"main\" or \"inverse\" (though only curly components support inverse) or the name given to a named block.",
+          "type": "String"
         }
       ],
-      "access": "private",
+      "return": {
+        "description": "`true` if the component was invoked with block params",
+        "type": "Boolean"
+      },
+      "access": "public",
       "tagname": "",
-      "class": "@ember/instrumentation",
-      "module": "@ember/instrumentation"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/instrumentation/index.ts",
-      "line": 323,
-      "description": "Resets `Instrumentation` by flushing list of subscribers.",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1193,
+      "description": "Execute the `debugger` statement in the current template's context.\n\n```handlebars\n{{debugger}}\n```\n\nWhen using the debugger helper you will have access to a `get` function. This\nfunction retrieves values available in the context of the template.\nFor example, if you're wondering why a value `{{foo}}` isn't rendering as\nexpected within a template, you could place a `{{debugger}}` statement and,\nwhen the `debugger;` breakpoint is hit, you can attempt to retrieve this value:\n\n```\n> get('foo')\n```\n\n`get` is also aware of keywords. So in this situation\n\n```handlebars\n{{#each this.items as |item|}}\n  {{debugger}}\n{{/each}}\n```\n\nYou'll be able to get values from the current item:\n\n```\n> get('item.name')\n```\n\nYou can also access the context of the view to make sure it is the object that\nyou expect:\n\n```\n> context\n```",
       "itemtype": "method",
-      "name": "reset",
+      "name": "debugger",
       "static": 1,
-      "access": "private",
+      "noimport": "",
+      "access": "public",
       "tagname": "",
-      "class": "@ember/instrumentation",
-      "module": "@ember/instrumentation"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
-      "line": 65,
-      "description": "A computed property macro that returns true if the value of the dependent\nproperty is null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { empty } from '@ember/object/computed';\n\nclass ToDoList {\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  @empty('todos') isDone;\n}\n\nlet todoList = new ToDoList(\n  ['Unit Test', 'Documentation', 'Release']\n);\n\ntodoList.isDone; // false\nset(todoList, 'todos', []);\ntodoList.isDone; // true\n```",
-      "since": "1.6.0",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1238,
+      "description": "The `component` helper is used to package a Component with initial arguments.\nThe included arguments can then be merged during the final invocation.\n\nSee [Component](/ember/release/modules/@glimmer%2Fcomponent/) for\nadditional information on how a `Component` functions.\n\nThis is similar to the concept of Partial Application.\n  \nFor example, given a `FullName` component:\n\n```gjs {data-filename=\"app/components/full-name.gjs\"}\nimport MyInputComponent from './my-input-component';\n\n<template>\n  {{yield (component MyInputComponent value=@model.name placeholder=\"Username\")}}\n</template>\n```\n\nThe yielded component can be invoked by the calling component.\nSee the following snippet:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n  \n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field />\n  </FullName>\n</template>\n```\n\nWhich will output an input whose value is already bound to `@model.name` and `placeholder`\nis \"Username\".\n  \nAny arguments passed at the invocation site of the component will override those applied via\nthe `component` helper. For example, if the invocation site of the component is:\n\n```gjs {data-filename=\"app/components/person-form.gjs\"}\nimport FullName from './full-name';\n\n<template>\n  <FullName @model={{@model}} as |Field|>\n    <Field @placeholder=\"Your name\" />\n  </FullName>\n</template>\n```\n\nThe output will be an input whose value is bound to `@model.name` and `placeholder`\nis \"Your name\".\n  \nThe `component` helper is built-in and does not need to be imported. \n  \nPrior to Strict Mode aka \"Template Tag\" or gjs, the component helper was also used to invoke\ncomponents dynamically. This is no longer necessary, and they can be directly invoked, as above.\n\n### Dynamic Component Invocation\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { component } from '@ember/helper';\nimport LiveUpdatingChart from '../components/live-updating-chart';\nimport MarketCloseSummary from '../components/market-close-summary';\n\nexport default class Application extends Component {\n  @tracked isMarketOpen = false;\n\n  get infographicComponent() {\n    return this.isMarketOpen ? LiveUpdatingChart : MarketCloseSummary;\n  }\n\n  <template>\n    {{!-- The component can be invoked directly --}}\n    <this.infographicComponent />\n  \n    {{!-- The component helper here is no longer necessary --}}\n    {{component this.infographicComponentName}}\n  </template>\n}\n```",
       "itemtype": "method",
-      "name": "empty",
+      "name": "component",
+      "since": "1.11.0",
       "static": 1,
-      "params": [
-        {
-          "name": "dependentKey",
-          "description": "",
-          "type": "String"
-        }
-      ],
-      "return": {
-        "description": "computed property which returns true if the value\nof the dependent property is null, an empty string, empty array, or empty\nfunction and false if the underlying value is not empty.",
-        "type": "ComputedProperty"
-      },
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "class": "@ember/object/computed",
-      "module": "@ember/object"
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
-      "line": 114,
-      "description": "A computed property that returns true if the value of the dependent property\nis NOT null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { notEmpty } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(backpack) {\n    set(this, 'backpack', backpack);\n  }\n\n  @notEmpty('backpack') hasStuff\n}\n\nlet hamster = new Hamster(\n  ['Food', 'Sleeping Bag', 'Tent']\n);\n\nhamster.hasStuff; // true\nset(hamster, 'backpack', []);\nhamster.hasStuff; // false\n```",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1328,
+      "description": "Use the `{{helper}}` helper to create contextual helper so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (helper \"join-words\" \"foo\" \"bar\" separator=\" \") as |foo-bar|}}\n\n  {{!-- this is equivalent to invoking `{{join-words \"foo\" \"bar\" separator=\" \"}}` --}}\n  {{foo-bar}}\n\n  {{!-- this will pass the helper itself into the component, instead of invoking it now --}}\n  <MyComponent @helper={{helper foo-bar \"baz\"}} />\n\n  {{!-- this will yield the helper itself (\"contextual helper\"), instead of invoking it now --}}\n  {{yield foo-bar}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{helper}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{modifier}}`](./modifier?anchor=modifier) helper:\n\n* When passed a string (e.g. `(helper \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"helper definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced helper.",
       "itemtype": "method",
-      "name": "notEmpty",
+      "name": "helper",
       "static": 1,
-      "params": [
-        {
-          "name": "dependentKey",
-          "description": "",
-          "type": "String"
-        }
-      ],
-      "return": {
-        "description": "computed property which returns true if original\nvalue for property is not empty.",
-        "type": "ComputedProperty"
-      },
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "class": "@ember/object/computed",
-      "module": "@ember/object"
+      "since": "3.27.0",
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1368,
+      "description": "The `if` helper allows you to conditionally render one of two branches,\ndepending on the \"truthiness\" of a property.\nFor example the following values are all falsey: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\nThis helper has two forms, block and inline.\n\n## Block form\n\nYou can use the block form of `if` to conditionally render a section of the template.\n\nTo use it, pass the conditional value to the `if` helper,\nusing the block form to wrap the section of template you want to conditionally render.\nLike so:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather />\n</template>\n```\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{! will not render because greeting is undefined}}\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{/if}}\n</template>\n```\n\nYou can also define what to show if the property is falsey by using\nthe `else` helper.\n\n```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>\n```\n\nYou are also able to combine `else` and `if` helpers to create more complex\nconditional logic.\n\nFor the following template:\n\n ```gjs {data-filename=\"app/components/weather.gjs\"}\n<template>\n  {{#if @isRaining}}\n    Yes, grab an umbrella!\n  {{else if @isCold}}\n    Grab a coat, it's chilly!\n  {{else}}\n    No, it's lovely outside!\n  {{/if}}\n</template>  \n```\n\nIf you call it by saying `isCold` is true:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Weather from '../components/weather';\n  \n<template>\n  <Weather @isCold={{true}} />\n</template>\n```\n\nThen `Grab a coat, it's chilly!` will be rendered.\n\n## Inline form\n\nThe inline `if` helper conditionally renders a single property or string.\n\nIn this form, the `if` helper receives three arguments, the conditional value,\nthe value to render when truthy, and the value to render when falsey.\n\nFor example, if `useLongGreeting` is truthy, the following:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n\n<template>\n  <Greeting @useLongGreeting={{true}} />\n<template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{if @useLongGreeting \"Hello\" \"Hi\"}} Alex\n<template>\n```\n\nWill render:\n\n```html\nHello Alex\n```\n\nOne detail to keep in mind is that both branches of the `if` helper will be evaluated,\nso if you have `{{if condition \"foo\" (expensive-operation \"bar\")`,\n`expensive-operation` will always calculate.\n \n`if` is built-in and does not need to be imported.",
+      "itemtype": "method",
+      "name": "if",
+      "static": 1,
+      "noimport": "",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1484,
+      "description": "The `unless` helper is the inverse of the `if` helper. It displays if a value\nis falsey (\"not true\" or \"is false\"). Example values that will display with\n`unless`: `false`, `undefined`, `null`, `\"\"`, `0`, `NaN` or an empty array.\n\n## Inline form\n\nThe inline `unless` helper conditionally renders a single property or string.\nThis helper acts like a ternary operator. If the first property is falsy,\nthe second argument will be displayed, otherwise, the third argument will be\ndisplayed\n\nFor example, if you pass a falsey `useLongGreeting` to the `Greeting` component:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting @useLongGreeting={{false}} />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{unless @useLongGreeting \"Hi\" \"Hello\"}} Ben\n</template>\n```\n\nThen it will display:\n\n```html\nHi Ben\n```\n\n## Block form\n\nLike the `if` helper, the `unless` helper also has a block form.\n\nThe following will not render anything:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport Greeting from '../components/greeting';\n  \n<template>\n  <Greeting />\n</template>\n```\n\n```gjs {data-filename=\"app/components/greeting.gjs\"}\n<template>\n  {{#unless @greeting}}\n    No greeting was found. Why not set one?\n  {{/unless}}\n</template>\n```\n\nYou can also use an `else` helper with the `unless` block. The\n`else` will display if the value is truthy.\n\nIf you have the following component:\n\n```gjs {data-filename=\"app/components/logged-in.gjs\"}\n<template>\n  {{#unless @userData}}\n    Please login.\n  {{else}}\n    Welcome back!\n  {{/unless}}\n</template>\n```\n\nCalling it with a truthy `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n  \n<template>\n  <LoggedIn @userData={{hash username=\"Zoey\"}} />\n</template>\n```\n\nWill render:\n\n```html\nWelcome back!\n```\n\nand calling it with a falsey `userData`:\n\n```gjs {data-filename=\"app/templates/application.gjs\"}\nimport LoggedIn from '../components/logged-in';\n\n<template>\n  <LoggedIn @userData={{false}} />\n</template>\n```\n\nWill render:\n\n```html\nPlease login.\n```\n \n`unless` is built-in and does not need to be imported.",
+      "itemtype": "method",
+      "name": "unless",
+      "noimport": "",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1596,
+      "description": "`log` allows you to output the value of variables in the current rendering\ncontext. `log` also accepts primitive types such as strings or numbers.\n\n```handlebars\n{{log \"myVariable:\" myVariable }}\n```\n \n`log` is built-in as a template keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "log",
+      "noimport": "",
+      "static": 1,
+      "params": [
+        {
+          "name": "params",
+          "description": "",
+          "type": "Array"
+        }
+      ],
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1614,
+      "description": "Use the `{{modifier}}` helper to create contextual modifier so\nthat it can be passed around as first-class values in templates.\n\n```handlebars\n{{#let (modifier \"click-outside\" click=this.submit) as |on-click-outside|}}\n\n  {{!-- this is equivalent to `<MyComponent {{click-outside click=this.submit}} />` --}}\n  <MyComponent {{on-click-outside}} />\n\n  {{!-- this will pass the modifier itself into the component, instead of invoking it now --}}\n  <MyComponent @modifier={{modifier on-click-outside \"extra\" \"args\"}} />\n\n  {{!-- this will yield the modifier itself (\"contextual modifier\"), instead of invoking it now --}}\n  {{yield on-click-outside}}\n{{/let}}\n```\n\n### Arguments\n\nThe `{{modifier}}` helper works similarly to the [`{{component}}`](./component?anchor=component) and\n[`{{helper}}`](./helper?anchor=helper) helper:\n\n* When passed a string (e.g. `(modifier \"foo\")`) as the first argument,\n  it will produce an opaque, internal \"modifier definition\" object\n  that can be passed around and invoked elsewhere.\n\n* Any additional positional and/or named arguments (a.k.a. params and hash)\n  will be stored (\"curried\") inside the definition object, such that, when invoked,\n  these arguments will be passed along to the referenced modifier.\n\n`modifier` is built-in as a template keyword and does not need to be imported.",
+      "itemtype": "method",
+      "name": "modifier",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "since": "3.27.0",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1654,
+      "description": "`pageTitle` allows you to set the title of any page in your application and\nappend additional titles for each route. For complete documentation, see\nhttps://github.com/ember-cli/ember-page-title.\n\n```gjs\nimport { pageTitle } from 'ember-page-title';\n  \n<template>\n  {{pageTitle \"My Page Title\" }}\n</template>\n```",
+      "itemtype": "method",
+      "name": "pageTitle",
+      "params": [
+        {
+          "name": "param",
+          "description": "",
+          "type": "String"
+        }
+      ],
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "External",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1674,
+      "description": "The `let` helper receives one or more positional arguments and yields\nthem out as block params.\n\nThis allows the developer to introduce shorter names for certain computations\nin the template.\n\nThis is especially useful if you are passing properties to a component\nthat receives a lot of options and you want to clean up the invocation.\n\nFor the following example, the template receives a `post` object with\n`content` and `title` properties.\n\nWe are going to call the `my-post` component, passing a title which is\nthe title of the post suffixed with the name of the blog, the content\nof the post, and a series of options defined in-place.\n\n```handlebars\n{{#let\n    (concat post.title ' | The Ember.js Blog')\n    post.content\n    (hash\n      theme=\"high-contrast\"\n      enableComments=true\n    )\n    as |title content options|\n}}\n  <MyPost @title={{title}} @content={{content}} @options={{options}} />\n{{/let}}\n  ```\n\n `let` is built-in and does not need to be imported.",
+      "itemtype": "method",
+      "name": "let",
+      "static": 1,
+      "noimport": "",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 1714,
+      "description": "The `in-element` helper renders its block content outside of the regular flow,\ninto a DOM element given by its `destinationElement` positional argument.\n\nCommon use cases - often referred to as \"portals\" or \"wormholes\" - are rendering\ndropdowns, modals or tooltips close to the root of the page to bypass CSS overflow\nrules, or to render content to parts of the page that are outside of the control\nof the Ember app itself (e.g. embedded into a static or server rendered HTML page).\n\n```handlebars\n{{#in-element this.destinationElement}}\n  <div>Some content</div>\n{{/in-element}}\n```\n\n### Arguments\n\n`{{in-element}}` requires a single positional argument:\n\n- `destinationElement` -- the DOM element to render into. It must exist at the time\nof rendering.\n\nIt also supports an optional named argument:\n\n- `insertBefore` -- by default the DOM element's content is replaced when used as\n`destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\nappend the block content to the end of any existing content. Any other value than\n`null` is currently not supported.\n\n    For example:\n\n    ```handlebars\n    {{#in-element this.destinationElement insertBefore=null}}\n      <div>Some content</div>\n    {{/in-element}}\n    ```\n\n`in-element` is built-in and does not need to be imported.",
+      "itemtype": "method",
+      "name": "in-element",
+      "params": [
+        {
+          "name": "destinationElement",
+          "description": "the DOM element to render into. It must exist at the time\n of rendering.",
+          "type": "Element"
+        },
+        {
+          "name": "insertBefore",
+          "description": "named argument, by default the DOM element's content is replaced when used as\n `destinationElement`. Passing `null` to `insertBefore` changes the behaviour to\n append the block content to the end of any existing content. Any other value than\n `null` is currently not supported.",
+          "type": "Boolean"
+        }
+      ],
+      "static": 1,
+      "noimport": "",
+      "access": "public",
+      "tagname": "",
+      "class": "Keywords",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/instrumentation/index.ts",
+      "line": 107,
+      "description": "Notifies event's subscribers, calls `before` and `after` hooks.",
+      "itemtype": "method",
+      "name": "instrument",
+      "static": 1,
+      "params": [
+        {
+          "name": "name",
+          "description": "Namespaced event name.",
+          "type": "String",
+          "optional": true
+        },
+        {
+          "name": "payload",
+          "description": "",
+          "type": "Object"
+        },
+        {
+          "name": "callback",
+          "description": "Function that you're instrumenting.",
+          "type": "Function"
+        },
+        {
+          "name": "binding",
+          "description": "Context that instrument function is called with.",
+          "type": "Object"
+        }
+      ],
+      "access": "private",
+      "tagname": "",
+      "class": "@ember/instrumentation",
+      "module": "@ember/instrumentation"
+    },
+    {
+      "file": "packages/@ember/instrumentation/index.ts",
+      "line": 260,
+      "description": "Subscribes to a particular event or instrumented block of code.",
+      "itemtype": "method",
+      "name": "subscribe",
+      "static": 1,
+      "params": [
+        {
+          "name": "pattern",
+          "description": "Namespaced event name.",
+          "type": "String",
+          "optional": true
+        },
+        {
+          "name": "object",
+          "description": "Before and After hooks.",
+          "type": "Object",
+          "optional": true
+        }
+      ],
+      "return": {
+        "description": "",
+        "type": "Subscriber"
+      },
+      "access": "private",
+      "tagname": "",
+      "class": "@ember/instrumentation",
+      "module": "@ember/instrumentation"
+    },
+    {
+      "file": "packages/@ember/instrumentation/index.ts",
+      "line": 300,
+      "description": "Unsubscribes from a particular event or instrumented block of code.",
+      "itemtype": "method",
+      "name": "unsubscribe",
+      "static": 1,
+      "params": [
+        {
+          "name": "subscriber",
+          "description": "",
+          "type": "Object",
+          "optional": true
+        }
+      ],
+      "access": "private",
+      "tagname": "",
+      "class": "@ember/instrumentation",
+      "module": "@ember/instrumentation"
+    },
+    {
+      "file": "packages/@ember/instrumentation/index.ts",
+      "line": 323,
+      "description": "Resets `Instrumentation` by flushing list of subscribers.",
+      "itemtype": "method",
+      "name": "reset",
+      "static": 1,
+      "access": "private",
+      "tagname": "",
+      "class": "@ember/instrumentation",
+      "module": "@ember/instrumentation"
+    },
+    {
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 65,
+      "description": "A computed property macro that returns true if the value of the dependent\nproperty is null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { empty } from '@ember/object/computed';\n\nclass ToDoList {\n  constructor(todos) {\n    set(this, 'todos', todos);\n  }\n\n  @empty('todos') isDone;\n}\n\nlet todoList = new ToDoList(\n  ['Unit Test', 'Documentation', 'Release']\n);\n\ntodoList.isDone; // false\nset(todoList, 'todos', []);\ntodoList.isDone; // true\n```",
+      "since": "1.6.0",
+      "itemtype": "method",
+      "name": "empty",
+      "static": 1,
+      "params": [
+        {
+          "name": "dependentKey",
+          "description": "",
+          "type": "String"
+        }
+      ],
+      "return": {
+        "description": "computed property which returns true if the value\nof the dependent property is null, an empty string, empty array, or empty\nfunction and false if the underlying value is not empty.",
+        "type": "ComputedProperty"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "@ember/object/computed",
+      "module": "@ember/object"
+    },
+    {
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
+      "line": 114,
+      "description": "A computed property that returns true if the value of the dependent property\nis NOT null, an empty string, empty array, or empty function.\n\nExample:\n\n```javascript\nimport { set } from '@ember/object';\nimport { notEmpty } from '@ember/object/computed';\n\nclass Hamster {\n  constructor(backpack) {\n    set(this, 'backpack', backpack);\n  }\n\n  @notEmpty('backpack') hasStuff\n}\n\nlet hamster = new Hamster(\n  ['Food', 'Sleeping Bag', 'Tent']\n);\n\nhamster.hasStuff; // true\nset(hamster, 'backpack', []);\nhamster.hasStuff; // false\n```",
+      "itemtype": "method",
+      "name": "notEmpty",
+      "static": 1,
+      "params": [
+        {
+          "name": "dependentKey",
+          "description": "",
+          "type": "String"
+        }
+      ],
+      "return": {
+        "description": "computed property which returns true if original\nvalue for property is not empty.",
+        "type": "ComputedProperty"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "@ember/object/computed",
+      "module": "@ember/object"
+    },
+    {
+      "file": "packages/@ember/object/lib/computed/computed_macros.ts",
       "line": 160,
       "description": "A computed property that returns true if the value of the dependent property\nis null or undefined. This avoids errors from JSLint complaining about use of\n==, which can be technically confusing.\n\n```javascript\nimport { set } from '@ember/object';\nimport { none } from '@ember/object/computed';\n\nclass Hamster {\n  @none('food') isHungry;\n}\n\nlet hamster = new Hamster();\n\nhamster.isHungry; // true\n\nset(hamster, 'food', 'Banana');\nhamster.isHungry; // false\n\nset(hamster, 'food', null);\nhamster.isHungry; // true\n```",
       "itemtype": "method",
@@ -15244,7 +15077,7 @@
     {
       "file": "packages/@ember/object/compat.ts",
       "line": 45,
-      "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nClassic Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport EmberObject, { computed, observer, set } from '@ember/object';\n\nconst Person = EmberObject.extend({\n  firstName: tracked(),\n  lastName: tracked(),\n\n  fullName: dependentKeyCompat(function() {\n    return `${this.firstName} ${this.lastName}`;\n  }),\n});\n\nconst Profile = EmberObject.extend({\n  person: null,\n\n  helloMessage: computed('person.fullName', function() {\n    return `Hello, ${this.person.fullName}!`;\n  }),\n\n  onNameUpdated: observer('person.fullName', function() {\n    console.log('person name updated!');\n  }),\n});\n```\n\n`dependentKeyCompat()` can receive a getter function or an object containing\n`get`/`set` methods when used in classic classes, like computed properties.\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
+      "description": "`@dependentKeyCompat` is decorator that can be used on _native getters_ that\nuse tracked properties. It exposes the getter to Ember's classic computed\nproperty and observer systems, so they can watch it for changes. It can be\nused in both native and classic classes.\n\nNative Example:\n\n```js\nimport { tracked } from '@glimmer/tracking';\nimport { dependentKeyCompat } from '@ember/object/compat';\nimport { computed, set } from '@ember/object';\n\nclass Person {\n  @tracked firstName;\n  @tracked lastName;\n\n  @dependentKeyCompat\n  get fullName() {\n    return `${this.firstName} ${this.lastName}`;\n  }\n}\n\nclass Profile {\n  constructor(person) {\n    set(this, 'person', person);\n  }\n\n  @computed('person.fullName')\n  get helloMessage() {\n    return `Hello, ${this.person.fullName}!`;\n  }\n}\n```\n\nIn general, only properties which you _expect_ to be watched by older,\nuntracked clases should be marked as dependency compatible. The decorator is\nmeant as an interop layer for parts of Ember's older classic APIs, and should\nnot be applied to every possible getter/setter in classes. The number of\ndependency compatible getters should be _minimized_ wherever possible. New\napplication code should not need to use `@dependentKeyCompat`, since it is\nonly for interoperation with older code.",
       "access": "public",
       "tagname": "",
       "itemtype": "method",
@@ -18301,7 +18134,7 @@
     {
       "file": "packages/@ember/routing/router-service.ts",
       "line": 90,
-      "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```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```",
+      "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",
       "params": [
@@ -18369,7 +18202,7 @@
     {
       "file": "packages/@ember/routing/router-service.ts",
       "line": 190,
-      "description": "Generate a URL based on the supplied route name and optionally a model. The\nURL is returned as a string that can be used for any purpose.\n\nIn this example, the URL for the `author.books` route for a given author\nis copied to the clipboard.\n\n```app/templates/application.gjs\nimport CopyLink from '../components/copy-link';\n  \n<template>\n  <CopyLink @author={{hash id=\"tomster\" name=\"Tomster\"}} />\n</template>\n```\n\n```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```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```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```",
+      "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",
       "params": [
@@ -18402,7 +18235,7 @@
     {
       "file": "packages/@ember/routing/router-service.ts",
       "line": 274,
-      "description": "Returns `true` if `routeName/models/queryParams` is the active route, where `models` and `queryParams` are optional.\nSee [model](api/ember/release/classes/Route/methods/model?anchor=model) and\n[queryParams](/api/ember/3.7/classes/Route/properties/queryParams?anchor=queryParams) for more information about these arguments.\n\nIn the following example, `isActive` will return `true` if the current route is `/posts`.\n\n```app/components/posts.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```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.",
+      "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",
       "params": [
@@ -18634,7 +18467,7 @@
     {
       "file": "packages/@ember/routing/router-service.ts",
       "line": 732,
-      "description": "The `currentRoute` property contains metadata about the current leaf route.\nIt returns a `RouteInfo` object that has information like the route name,\nparams, query params and more.\n\nSee [RouteInfo](/ember/release/classes/RouteInfo) for more info.\n\nThis property is guaranteed to change whenever a route transition\nhappens (even when that transition only changes parameters\nand doesn't change the active route).\n\nUsage example:\n```app/components/header.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```",
+      "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",
       "type": "RouteInfo",
@@ -20303,84 +20136,228 @@
       "file": "packages/@glimmer/compiler/lib/builder/builder-interface.ts",
       "line": 70,
       "description": "Differences:\n\n- strict mode variables always refer to in-scope variables\n- loose mode variables use this algorithm:\n  1. otherwise, fall back to `this.<name>`",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/builder/builder-interface.ts",
       "line": 588,
       "description": "The special value 'splat' is used to indicate that the attribute is a splat",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts",
       "line": 108,
       "description": "A \"generic\" keyword is something like `has-block`, which makes sense in the context\nof sub-expression or append",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts",
       "line": 227,
       "description": "This function builds keyword definitions for a particular type of AST node (`KeywordType`).\n\nYou can build keyword definitions for:\n\n- `Expr`: A `SubExpression` or `PathExpression`\n- `Block`: A `BlockStatement`\n  - A `BlockStatement` is a keyword candidate if its head is a\n    `PathExpression`\n- `Append`: An `AppendStatement`\n\nA node is a keyword candidate if:\n\n- A `PathExpression` is a keyword candidate if it has no tail, and its\n  head expression is a `LocalVarHead` or `FreeVarHead` whose name is\n  the keyword's name.\n- A `SubExpression`, `AppendStatement`, or `BlockStatement` is a keyword\n  candidate if its head is a keyword candidate.\n\nThe keyword infrastructure guarantees that:\n\n- If a node is not a keyword candidate, it is never passed to any keyword's\n  `assert` method.\n- If a node is not the `KeywordType` for a particular keyword, it will not\n  be passed to the keyword's `assert` method.\n\n`Expr` keywords are used in expression positions and should return HIR\nexpressions. `Block` and `Append` keywords are used in statement\npositions and should return HIR statements.\n\nA keyword definition has two parts:\n\n- `match`, which determines whether an AST node matches the keyword, and can\n  optionally return some information extracted from the AST node.\n- `translate`, which takes a matching AST node as well as the extracted\n  information and returns an appropriate HIR instruction.\n\n# Example\n\nThis keyword:\n\n- turns `(hello)` into `\"hello\"`\n  - as long as `hello` is not in scope\n- makes it an error to pass any arguments (such as `(hello world)`)\n\n```ts\nkeywords('SubExpr').kw('hello', {\n  assert(node: ExprKeywordNode): Result<void> | false {\n    // we don't want to transform `hello` as a `PathExpression`\n    if (node.type !== 'SubExpression') {\n      return false;\n    }\n\n    // node.head would be `LocalVarHead` if `hello` was in scope\n    if (node.head.type !== 'FreeVarHead') {\n      return false;\n    }\n\n    if (node.params.length || node.hash) {\n      return Err(generateSyntaxError(`(hello) does not take any arguments`), node.loc);\n    } else {\n      return Ok();\n    }\n  },\n\n  translate(node: ASTv2.SubExpression): hir.Expression {\n    return ASTv2.builders.literal(\"hello\", node.loc)\n  }\n})\n```\n\nThe keyword infrastructure checks to make sure that the node is the right\ntype before calling `assert`, so you only need to consider `SubExpression`\nand `PathExpression` here. It also checks to make sure that the node passed\nto `assert` has the keyword name in the right place.\n\nNote the important difference between returning `false` from `assert`,\nwhich just means that the node didn't match, and returning `Err`, which\nmeans that the node matched, but there was a keyword-specific syntax\nerror.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/passes/1-normalization/visitors/expressions.ts",
       "line": 51,
       "description": "Normalize paths into `hir.Path` or a `hir.Expr` that corresponds to the ref.\n\nTODO since keywords don't support tails anyway, distinguish PathExpression from\nVariableReference in ASTv2.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/passes/1-normalization/context.ts",
       "line": 10,
       "description": "This is the mutable state for this compiler pass.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
       "file": "packages/@glimmer/compiler/lib/passes/1-normalization/index.ts",
       "line": 17,
       "description": "Normalize the AST from @glimmer/syntax into the HIR. The HIR has special\ninstructions for keywords like `{{yield}}`, `(has-block)` and\n`{{#in-element}}`.\n\nMost importantly, it also classifies HTML element syntax into:\n\n1. simple HTML element (with optional splattributes)\n2. component invocation\n\nBecause the @glimmer/syntax AST gives us a string for an element's tag,\nthis pass also normalizes that string into an expression.\n\n```\n// normalized into a path expression whose head is `this` and tail is\n// `[\"x\"]`\n<this.x />\n\n{{#let expr as |t|}}\n  // `\"t\"` is normalized into a variable lookup.\n  <t />\n\n  // normalized into a path expression whose head is the variable lookup\n  // `t` and tail is `[\"input\"]`.\n  <t.input />\n{{/let}}\n\n// normalized into a free variable lookup for `SomeComponent` (with the\n// context `ComponentHead`).\n<SomeComponent />\n\n// normalized into a path expression whose head is the free variable\n// `notInScope` (with the context `Expression`), and whose tail is\n// `[\"SomeComponent\"]`. In resolver mode, this path will be rejected later,\n// since it cannot serve as an input to the resolver.\n<notInScope.SomeComponent />\n```",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 36,
-      "class": "@glimmer/tracking",
+      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "line": 10,
+      "class": "Keywords",
       "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.\n  @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***.\n",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 56,
-      "class": "@glimmer/tracking",
+      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "line": 30,
+      "class": "Keywords",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 79,
-      "class": "@glimmer/tracking",
+      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "line": 62,
+      "class": "Keywords",
       "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.\n  @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***.\n",
       "module": "@ember/utils"
     },
     {
-      "file": "packages/@glimmer/component/src/-private/component.ts",
-      "line": 97,
+      "file": "packages/@glimmer/component/dist/-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": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@ember/utils"
     },
+    {
+      "file": "packages/@glimmer/component/dist/-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,
+      "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": "@ember/utils"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/-private/component.d.ts",
+      "line": 212,
+      "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,
+      "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",
+      "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,
+      "class": "Keywords",
+      "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.\n  @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***.\n",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/index.js",
+      "line": 47,
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/index.js",
+      "line": 49,
+      "class": "Keywords",
+      "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.\n  @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***.\n",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/dist/index.js",
+      "line": 66,
+      "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,
+      "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,
+      "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/index.js",
+      "line": 212,
+      "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,
+      "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,
+      "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,
+      "class": "Keywords",
+      "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.\n  @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***.\n",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/src/-private/component.ts",
+      "line": 56,
+      "class": "Keywords",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/src/-private/component.ts",
+      "line": 79,
+      "class": "Keywords",
+      "description": "Given any allowed shorthand form of a signature, desugars it to its full\nexpanded type.\n  @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***.\n",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/component/src/-private/component.ts",
+      "line": 97,
+      "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,
       "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": "@glimmer/tracking",
-      "module": "@ember/utils"
+      "class": "Keywords",
+      "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
@@ -20396,252 +20373,252 @@
           "description": ""
         }
       ],
-      "class": "@glimmer/tracking",
-      "module": "@ember/utils"
+      "class": "Keywords",
+      "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
       "line": 248,
       "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": "@glimmer/tracking",
-      "module": "@ember/utils"
+      "class": "Keywords",
+      "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/component.ts",
       "line": 282,
       "description": "Called before the component has been removed from the DOM.",
-      "class": "@glimmer/tracking",
-      "module": "@ember/utils"
+      "class": "Keywords",
+      "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/component/src/-private/ember-component-manager.ts",
       "line": 24,
       "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": "@glimmer/tracking",
-      "module": "@ember/utils"
+      "class": "Keywords",
+      "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/dism/dism.ts",
       "line": 43,
       "description": "A dynamic operand has a value that can't be easily represented as an embedded string.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/dism/dism.ts",
       "line": 63,
       "description": "A variable is a numeric offset into the stack (relative to the $fp register).",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 6,
       "description": "The `LogFragmentBuffer` is responsible for collecting the fragments that are logged to the\n`DebugLogger` so that they can be accumulated during a group and flushed together.\n\nThis queuing serves two purposes:\n\n1. To allow the individual fragments that make up a single line to append their values to\n   the current line. To accomplish this, each fragment can append static content and its\n   formatting specifier (e.g. `%o`) to the accumulated {@link #template} *and* append the\n   value to format to the {@link #substitutions} array.\n2. To allow logs that refer to objects to be represented as footnotes in the current line,\n   with the footnote to be printed in a later line.\n\nThis allows a list of fragments, each of which represent formattable values, to be flattened\ninto a single template string and an array of values to format.\n\n## Footnotes\n\nAn opcode slice containing constant references will be logged like this:\n\n```\n...\n362. (PushArgs names=[] block-names=[] flags=16)\n366. (Helper helper=[0])\n[0] glimmerHelper()\n368. (PopFrame)\n369. (Fetch register=$v0)\n371. (Primitive constant=\"/index.html\")\n...\n```\n\nThe fragment for line `366` includes an `ObjectFragment` for the helper value. When logged,\nthe object will be represented as a footnote and the value will be printed in a later\nline.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 42,
       "description": "The first parameter to the `console.log` family of APIs is a *template* that can use\nformat specifiers (e.g. `%c`, `%o`, and `%O`) to refer to subsequent parameters.\n\nWhen a fragment is appended to a line,",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 50,
       "description": "Each format specified in the {@link #template} corresponds to a value in the\n`#substitutions` array.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 56,
       "description": "The logging options for the buffer, which currently only contains `showSubtle`.\n\nWhen fragments call the buffer's {@linkcode append} method, they specify whether the\ncontent to append is subtle or not. If the buffer is not configured to show subtle\ncontent, the content is not appended.\n\nThis allows fragments to append content to the buffer without having to know how the\nbuffer is configured.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 68,
       "description": "A single line can produce multiple queued log entries. This happens when fragments\nappend *footnotes* to the buffer. A *reference* to the footnote is appended to the\nprimary line, and a line containing the *value* of the footnote is appended to the\n`#queued` array.\n\nBoth the primary line and any queued footnotes are flushed together when the buffer\nis flushed.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 85,
       "description": "Add a footnoted value to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.\n\nThis method takes two callbacks: `add` and `append`.\n\nThe `append` callback behaves like {@linkcode append}, but without the `subtle` argument. If\n`addFootnoted` is called with `subtle: false`, then the callback will never be called, so\nthere is no need to pass the `subtle` argument again.\n\nThe `add` callback is responsible for appending the footnote itself to the buffer. The first\nparameter to `add` (`useNumber`) specifies whether the caller has used the footnote number\nto refer to the footnote.\n\nThis is typically true, but fragments can specify an alternative annotation that should be used\ninstead of the default footnote number. In that case, the footnote number is not used, and the\nnext footnote is free to use it.\n\nThe `add` callback also takes a template string and an optional list of substitutions, which\ndescribe the way the footnote itself should be formatted.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/buffer.ts",
       "line": 134,
       "description": "Append a fragment to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/combinators.ts",
       "line": 6,
       "description": "The prepend function returns a subtle fragment if the contents are subtle.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/combinators.ts",
       "line": 13,
       "description": "The append function returns a subtle fragment if the contents are subtle.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/combinators.ts",
       "line": 19,
       "description": "The `wrap` function returns a subtle fragment if the contents are subtle.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/combinators.ts",
       "line": 53,
       "description": "A compact array makes the wrapping `[]` subtle if there's only one element.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/entry.ts",
       "line": 1,
       "description": "A Loggable is either:\n\n1. a single log line\n2. a log line as a header followed by a group of log entries",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/entry.ts",
       "line": 11,
       "description": "LogLine represents a single line in the log. The line is logged *either* by passing the `line`\nvalues to `console.{log,info,debug,warn,error}` *or* by passing them to `console.group` to\nrepresent the header of a group.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/entry.ts",
       "line": 21,
       "description": "LogGroup represents a group of log entries. It is logged by calling *either* `console.group` or\n`console.groupCollapsed` (depending on the value of `collapsed`).",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 19,
       "description": "A leaf fragment that represents an arbitrary value.\n\nWhen the value is a primitive, the fragment is appended to the buffer as if it was an instance of\nthe appropriate leaf fragment type (e.g. strings are appended as if they were `StringFragment`).\n\nOtherwise, `ValueFragment` is appended to the current line as a footnote reference and the value\nitself is appended to a later line that *defines* the footnote using the `%O` format specifier.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 32,
       "description": "The `ValueFragment` is appended to the current line as a footnote reference (e.g. `[1]`) and\nthe value itself is appended to a later line that *defines* the footnote (e.g. `[1]\nObjectHere`).\n\nBy default, the footnote reference is an incrementing number per log line, and the footnote\nvalue is formatted using the `%O` format specifier.\n\nThe `display` property can be provided to override these defaults.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 48,
       "description": "A leaf fragment that represents a string value.\n\nCorresponds to the `%s` format specifier.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 58,
       "description": "A leaf fragment that represents an integer value.\n\nCorresponds to the `%d` format specifier.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 68,
       "description": "A leaf fragment that represents a float value.\n\nCorresponds to the `%f` format specifier.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 78,
       "description": "A leaf fragment that represents a DOM node.\n\nCorresponds to the `%o` format specifier.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment-type.ts",
       "line": 88,
       "description": "The list of leaf fragment types correspond exactly to the list of console.log\nformat specifiers.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 21,
       "import": "{ StyleName } from './styles';",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 25,
       "description": "Fragment is the most fundamental building block of the debug logger.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 68,
       "description": "A subtle fragment is only printed if the `showSubtle` option is set.\n\nReturns true if this fragment is a subtle leaf or is a multi fragment\nwith all subtle leaves.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 78,
       "description": "If the current fragment is not empty, apply `ifPresent` to the current\nfragment. Otherwise, do nothing.\n\nIf the current fragment is subtle, the result is also subtle.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 90,
       "description": "A fragment is empty if it should not be printed with the provided display options.\n\nThis means that if a fragment is subtle and `showSubtle` is false, the fragment is empty.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 99,
       "description": "Returns an array of {@linkcode LeafFragment}s that make up the current\nfragment.\n\nThis effectively flattens any number of nested multi-fragments into a flat array of leaf\nfragments.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 116,
       "description": "Returns a fragment with the specified subtle status without mutating the current fragment.\n\nIf `isSubtle` is true, the fragment will also be styled with the `subtle` style.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 144,
       "description": "Apply the specified styles to the current fragment (if it's a leaf) or all\nof its children (if it's a multi-fragment).\n\nKeep in mind that merging styles might be very difficult to undo, so treat\nthis as a low-level operation, and prefer to use higher-level concepts like\n`subtle` if you can instead.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 168,
       "description": "Convert the current fragment into a string with no additional formatting.\nThe primary purpose for this method is to support converting a fragment\ninto a string for inclusion in thrown Errors. If you're going to *log*\na fragment, log it using `DebugLogger` and don't convert it to\na string first.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20651,95 +20628,95 @@
       "see": [
         "isEmpty"
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 213,
       "description": "Convert this fragment into a Loggable for logging through the `DebugLogger`.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/render/fragment.ts",
       "line": 226,
       "description": "Append this fragment to the low-level `LogFragmentBuffer`.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/debug.ts",
       "line": 235,
       "description": "A dynamic operand has a value that can't be easily represented as an embedded string.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/debug.ts",
       "line": 255,
       "description": "A variable is a numeric offset into the stack (relative to the $fp register).",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/metadata.ts",
       "line": 34,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug/lib/metadata.ts",
       "line": 36,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug-util/lib/assert.ts",
       "line": 19,
       "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\nFF\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug-util/lib/assert.ts",
       "line": 29,
       "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug-util/lib/debug-brand.ts",
       "line": 15,
       "description": "An object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function does nothing (and is removed\nby the minifier in builder).",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug-util/lib/debug-brand.ts",
       "line": 38,
       "description": "An object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function always returns undefined. However,\nthis function should only be called by the trace logger, which should only\nrun in trace `LOCAL_DEBUG` + `LOCAL_TRACE_LOGGING` mode.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/debug-util/lib/platform-utils.ts",
       "line": 13,
       "description": "This 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.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 4,
       "description": "This 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",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 21,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "description": "Interfaces\n\nTODO: Move these into @glimmer/interfaces, move @glimmer/interfaces to\n  @glimmer /internal-interfaces.\n",
       "module": "@glimmer/component"
     },
@@ -20747,7 +20724,7 @@
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 37,
       "description": "Schedules a VM revalidation.\n\nNote: this has a default value so that tags can warm themselves when first loaded.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20764,7 +20741,7 @@
           "description": "The destructor being scheduled"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20777,7 +20754,7 @@
           "description": "finalizer function"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20790,7 +20767,7 @@
           "description": "The value to create an iterator for"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20803,7 +20780,7 @@
           "description": "The value to convert to a boolean"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20820,7 +20797,7 @@
           "description": "The path to get the value from"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20841,7 +20818,7 @@
           "description": "The value to set the value to"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20858,7 +20835,7 @@
           "description": "The path to get the value from"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20875,97 +20852,97 @@
           "description": "The path to get the value from"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 113,
       "description": "Hook to warn if a style binding string or value was not marked as trusted\n(e.g. HTMLSafe)",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 119,
       "description": "Hook to customize assertion messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/global-context/index.ts",
       "line": 135,
       "description": "Hook to customize deprecation messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 303,
       "description": "A Handlebars statement",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 344,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 362,
       "description": "A JSON object that the Block was serialized into.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 369,
       "description": "A JSON object that the compiled TemplateBlock was serialized into.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 378,
       "description": "A JSON object that the compiled Template was serialized into.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 387,
       "description": "A string of JSON containing a SerializedTemplateBlock",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 392,
       "description": "A JSON object containing the SerializedTemplateBlock as JSON and TemplateMeta.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts",
       "line": 403,
       "description": "A string of Javascript containing a SerializedTemplateWithLazyBlock to be\nconcatenated into a Javascript module.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/wire-format/resolution.d.ts",
       "line": 1,
       "description": "A VariableResolutionContext explains how a variable name should be resolved.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/encoder.d.ts",
       "line": 134,
       "description": "The Encoder receives a stream of opcodes from the syntax compiler and turns\nthem into a binary program.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -20982,7 +20959,7 @@
           "description": ""
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21000,21 +20977,21 @@
           "type": "Type: \"type\", value: value"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/encoder.d.ts",
       "line": 163,
       "description": "Start a new labels block. A labels block is a scope for labels that\ncan be referred to before they are declared. For example, when compiling\nan `if`, the `JumpUnless` opcode occurs before the target label. To\naccommodate this use-case ergonomically, the `Encoder` allows a syntax\nto create a labels block and then refer to labels that have not yet\nbeen declared. Once the block is complete, a second pass replaces the\nlabel names with offsets.\n\nThe pattern is:\n\n```ts\nencoder.reserve(Op.JumpUnless);\nencoder.target(encoder.pos, 'ELSE');\n```\n\nThe `reserve` method creates a placeholder opcode with space for a target\nin the future, and the `target` method registers the blank operand position\nto be replaced with an offset to `ELSE`, once it's known.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/compile/encoder.d.ts",
       "line": 185,
       "description": "Finish the current labels block and replace label names with offsets,\nnow that all of the offsets are known.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21031,188 +21008,188 @@
           "description": ""
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/dom/attributes.d.ts",
       "line": 15,
       "description": "`AppendingBlock` is the interface used by the `ElementBuilder` to keep track of which nodes have\nbeen appended to a block. Ultimately, an `AppendingBlock` is finalized and used as a `FixedBlock`\nor `ResettableBlock` during the updating phase.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/dom/attributes.d.ts",
       "line": 30,
       "description": "A `FixedBlock` is a block that is only rendered once, during initial render. Its *children* may\nchange during the updating phase, and this may cause its *bounds* to change, but the block itself\nremains stable.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/dom/attributes.d.ts",
       "line": 38,
       "description": "A `ResettableBlock` can be reset during the updating phase and rendered again.\n\nThis occurs for two reasons:\n\n1. The block represents an element in a list, and the element has been removed\n2. The block represents a conditional, and the condition has changed",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 16,
       "description": "Describes the capabilities of a particular component. The capabilities are\nprovided to the Glimmer compiler and VM via the ComponentDefinition, which\nincludes a ComponentCapabilities record.\n\nCertain features in the VM come with some overhead, so the compiler and\nruntime use this information to skip unnecessary work for component types\nthat don't need it.\n\nFor example, a component that is template-only (i.e., it does not have an\nassociated JavaScript class to instantiate) can skip invoking component\nmanager hooks related to lifecycle events by setting the `elementHook`\ncapability to `false`.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 31,
       "description": "Whether a component's template is static across all instances of that\ncomponent, or can vary per instance. This should usually be `false` except\nfor cases of backwards-compatibility.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 38,
       "description": "Whether a \"wrapped\" component's root element can change after being\nrendered. This flag is only used by the WrappedBuilder and should be\n`false` except for cases of backwards-compatibility.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 47,
       "description": "Setting the `prepareArgs` flag to true enables the `prepareArgs` hook on\nthe component manager, which would otherwise not be called.\n\nThe component manager's `prepareArgs` hook allows it to programmatically\nadd or remove positional and named arguments for a component before the\ncomponent is invoked. This flag should usually be `false` except for cases\nof backwards-compatibility.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 58,
       "description": "Whether a reified `Arguments` object will get passed to the component\nmanager's `create` hook. If a particular component does not access passed\narguments from JavaScript (via the `this.args` property in Glimmer.js, for\nexample), this flag can be set to `false` to avoid the work of\ninstantiating extra data structures to expose the arguments to JavaScript.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 67,
       "description": "Whether the component needs the caller component",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 72,
       "description": "Whether to call the `didSplatAttributes` hook on the component manager.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 77,
       "description": "Whether to call the `didCreateElement` hook on the component manager.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 82,
       "description": "Whether the component manager has an update hook.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 87,
       "description": "Whether the component needs an additional dynamic scope frame.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 92,
       "description": "Whether there is a component instance to create. If this is false,\nthe component is a \"template only component\"",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 98,
       "description": "Whether or not the component has a `willDestroy` hook that should fire\nprior to the component being removed from the DOM.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 104,
       "description": "Whether or not the component pushes an owner onto the owner stack. This is\nused for engines.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/managers/internal/component.d.ts",
       "line": 111,
       "description": "Enum used for bit flags version of the capabilities, used once the component\nhas been loaded for the first time",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts",
       "line": 40,
       "description": "All parts of `DebugVmState` are _snapshots_. They will not change if the piece of VM state that\nthey reference changes.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts",
       "line": 45,
       "description": "These values are the same for the entire program",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts",
       "line": 50,
       "description": "These values can change for each opcode. You can get a snapshot a specific stack by calling\n`stacks.<name>.snapshot()`.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/runtime/scope.d.ts",
       "line": 14,
       "description": "A single program can mix and match multiple owners. This can happen component is curried from a\ntemplate with one owner and then rendered in a second owner.\n\nNote: Owners can change when new root scopes are created (including when rendering a\ncomponent), but not in child scopes.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/runtime/vm-state.d.ts",
       "line": 13,
       "description": "Registers\n\nFor the most part, these follows MIPS naming conventions, however the\nregister numbers are different.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/core.d.ts",
       "line": 7,
       "description": "A special version of `Optional` that is used for values that are expected to be initialized. This\ndocuments the intent that the value will be initialized before it is used, and therefore that\nnull assertions or `?.` are not appropriate.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/core.d.ts",
       "line": 16,
       "description": "A type that has an index signature, but nothing else is know about it. Useful in generic code\nthat needs to index into an opaque, user-specified object.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/core.d.ts",
       "line": 33,
       "description": "This is needed because the normal IteratorResult in the TypeScript\nstandard library is generic over the value in each tick and not over\nthe return value. It represents a standard ECMAScript IteratorResult.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 42,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "description": "Return the number of entries in the table. A handle is legal if\nit is less than this number.\n  @debugging \n",
       "module": "@glimmer/component"
     },
@@ -21220,91 +21197,91 @@
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 51,
       "description": "The `EvaluationContext` is the context that remains the same across all of the templates and\nevaluations in a single program.\n\nNote that multiple programs can co-exist on the same page, sharing tracking logic (and the\nglobal tracking context) but having different *evaluation* contexts.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 59,
       "description": "The program's environment, which contains customized framework behavior.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 63,
       "description": "The compiled program itself: the constants and heap",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 67,
       "description": "The offsets to stdlib functions",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 71,
       "description": "A framework-specified resolver for resolving free variables in classic templates.\n\nA strict component can invoke a classic component and vice versa, but only classic components\nwill use the resolver. If no resolver is available in the `ProgramContext`, only strict components\nwill compile and run.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 83,
       "description": "Options for compiling a specific template. This carries\nalong the static information associated with the entire\ntemplate when compiling blocks nested inside of it.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 98,
       "description": "Constants are interned values that are referenced as numbers in the program.\nThe constant pool is a part of the program, and is always transmitted\ntogether with the program.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/program.d.ts",
       "line": 109,
       "description": "Resolution happens when components are first loaded, either via the resolver\nor via looking them up in template scope.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/serialize.d.ts",
       "line": 1,
       "description": "This file describes the interface between compilation time\nand runtime.\n\n# Locators\n\nCompile time and runtime must share the same Locator. A Locator is an\nobject that describes the location of a template, and is roughly a\nmodule name. The compiler and runtime may use the Locator to locally\nresolve names relative to the template the name was found in, but must\nshare resolution rules between compilation time and runtime.\n\nFor example, given this template with Locator\n`{ module: 'components/Articles/Container' }:\n\n```\n<TabBar />\n```\n\nThe compiler may resolve `<TabBar>` to `components/Articles/TabBar`. The\nimportant thing is that the compiler and runtime share resolution rules.\n\n# CompileTimeLookup\n\nWhen compiling an application, the `CompileTimeLookup` is responsible\nfor resolving helpers, modifiers, and components into \"handles\"\n(numbers) that can be embedded into the program and used at runtime.\n\n# RuntimeResolver\n\nThe `RuntimeResolver` has two responsibilities.\n\n1. To turn handles created by the `CompileTimeLookup` into live helpers,\n   modifiers, and components.\n2. To resolve dynamic components at runtime that come from\n   calls to `{{component dynamic}}`.\n\nThe `CompileTimeLookup` and `RuntimeResolver` must maintain symmetry\nbetween:\n\n* `resolver.resolve(lookup.lookupComponentDefinition(name, referrer))`; and\n* `resolver.lookupComponentDefinition(name, referrer))`\n\n# Coupling\n\nIn practice, the `CompileTimeLookup` and `RuntimeResolver` are two parts\nof one system. The goal of this system is to allow the `CompileTimeLookup`\nto do as much resolution as possible ahead of time, while still allowing\nthe `RuntimeResolver` to do dynamic resolution when necessary.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/stack.d.ts",
       "line": 13,
       "description": "For debugging",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/tags.d.ts",
       "line": 12,
       "description": "This union represents all of the possible tag types for the monomorphic tag class.\nOther custom tag classes can exist, such as CurrentTag and VolatileTag, but for\nperformance reasons, any type of tag that is meant to be used frequently should\nbe added to the monomorphic tag.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/template.d.ts",
       "line": 30,
       "description": "Environment specific template.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/interfaces/lib/template.d.ts",
       "line": 36,
       "description": "Module name associated with the template, used for debugging purposes",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21318,7 +21295,7 @@
         }
       ],
       "description": "https://astexplorer.net/#/gist/c3f41b75af73006f64476775e73f7daa/e6e3e120df8404b1bff308bec3ed89eaaf0b05f2\n\nThis plugin exists because, _even when we inline\n  @glimmer /debug_,\nwe cannot get terser to remove/inline/unwrap identity functions.\n\nRepro here: https://try.terser.org/\n\n```js\nfunction x(x) { return x; }\nfunction y(x, y, z) { return x; };\n\nfunction abc(a) { return x(a); }\nfunction abc2(a) { return y(a); }\n\nexport function example() {\nreturn `${x(2)} ${y(\"2\")} ${abc(3)} ${abc2(\"3\")}`;\n}\n```\n\nWith Options:\n\n{\nmodule: true,\ncompress: {\npasses: 6,\nmodule: true,\ninline: 3, // default\n},\nmangle: {},\noutput: {},\nparse: {},\nrename: {},\n}\n",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21336,7 +21313,7 @@
           "type": "Any"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21354,7 +21331,7 @@
           "type": "Any"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21367,7 +21344,7 @@
           "type": " template: any;"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21385,14 +21362,14 @@
           "type": " [key: symbol]: any;"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/local-debug-babel-plugin/index.js",
       "line": 82,
       "description": "Do we want to support local aliasing / re-assignment?\nif so, this would break",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21410,7 +21387,7 @@
           "type": " [x: symbol]:  names: Set<any>; nodes: any[];"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21428,49 +21405,49 @@
           "type": " [key: symbol]:  names: Set<any>; nodes: any[];"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/local-debug-flags/index.ts",
       "line": 129,
       "description": "If the specified flag is set as a boolean flag with no value, `true` is returned.\n\nOtherwise, this function returns true if the flag value is a pattern that matches `value`.\n\nThe pattern can have a `*`, which matches any number of characters.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/manager/lib/internal/api.ts",
       "line": 28,
       "description": "There is also Reflect.getPrototypeOf,\nwhich errors when non-objects are passed.\n\nSince our conditional for figuring out whether to render primitives or not\nmay contain non-object values, we don't want to throw errors when we call this.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/manager/lib/public/component.ts",
       "line": 85,
       "description": "The CustomComponentManager allows addons to provide custom component\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom component manager, which\nimplements a set of hooks that determine component behavior.\n\nTo create a custom component manager, instantiate a new CustomComponentManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomComponentManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a component, the component manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n\n* `create()` - invoked when a new instance of a component should be created\n* `update()` - invoked when the arguments passed to a component change\n* `getContext()` - returns the object that should be",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/manager/lib/public/component.ts",
       "line": 208,
       "description": "Stores internal state about a component instance after it's been created.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/manager/lib/public/modifier.ts",
       "line": 50,
       "description": "The CustomModifierManager allows addons to provide custom modifier\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom modifier manager, which\nimplements a set of hooks that determine modifier behavior.\nTo create a custom modifier manager, instantiate a new CustomModifierManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomModifierManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a modifier, the modifier manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n* `createModifier()` - invoked when a new instance of a modifier should be created\n* `installModifier()` - invoked when the modifier is installed on the element\n* `updateModifier()` - invoked when the arguments passed to a modifier change\n* `destroyModifier()` - invoked when the modifier is about to be destroyed",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/manager/lib/util/capabilities.ts",
       "line": 48,
       "description": "Converts a ComponentCapabilities object into a 32-bit integer representation.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21487,7 +21464,7 @@
           "description": "optional block parameters to yield to the block"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21500,7 +21477,7 @@
           "description": "An optional Compilable block"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21513,7 +21490,7 @@
           "description": "a Compilable block"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21530,56 +21507,56 @@
           "description": "A number of stack entries to preserve"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts",
       "line": 73,
       "description": "A convenience for pushing some arguments on the stack and\nrunning some code if the code needs to be re-executed during\nupdating execution if some of the arguments have changed.\n\n# Initial Execution\n\nThe `args` function should push zero or more arguments onto\nthe stack and return the number of arguments pushed.\n\nThe `body` function provides the instructions to execute both\nduring initial execution and during updating execution.\n\nInternally, this function starts by pushing a new frame, so\nthat the body can return and sets the return point ($ra) to\nthe ENDINITIAL label.\n\nIt then executes the `args` function, which adds instructions\nresponsible for pushing the arguments for the block to the\nstack. These arguments will be restored to the stack before\nupdating execution.\n\nNext, it adds the Enter opcode, which marks the current position\nin the DOM, and remembers the current $pc (the next instruction)\nas the first instruction to execute during updating execution.\n\nNext, it runs `body`, which adds the opcodes that should\nexecute both during initial execution and during updating execution.\nIf the `body` wishes to finish early, it should Jump to the\n`FINALLY` label.\n\nNext, it adds the FINALLY label, followed by:\n\n- the Exit opcode, which finalizes the marked DOM started by the\n  Enter opcode.\n- the Return opcode, which returns to the current return point\n  ($ra).\n\nFinally, it adds the ENDINITIAL label followed by the PopFrame\ninstruction, which restores $fp, $sp and $ra.\n\n# Updating Execution\n\nUpdating execution for this `replayable` occurs if the `body` added an\nassertion, via one of the `JumpIf`, `JumpUnless` or `AssertSame` opcodes.\n\nIf, during updating executon, the assertion fails, the initial VM is\nrestored, and the stored arguments are pushed onto the stack. The DOM\nbetween the starting and ending markers is cleared, and the VM's cursor\nis set to the area just cleared.\n\nThe return point ($ra) is set to -1, the exit instruction.\n\nFinally, the $pc is set to to the instruction saved off by the\nEnter opcode during initial execution, and execution proceeds as\nusual.\n\nThe only difference is that when a `Return` instruction is\nencountered, the program jumps to -1 rather than the END label,\nand the PopFrame opcode is not needed.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts",
       "line": 187,
       "description": "A specialized version of the `replayable` convenience that allows the\ncaller to provide different code based upon whether the item at\nthe top of the stack is true or false.\n\nAs in `replayable`, the `ifTrue` and `ifFalse` code can invoke `return`.\n\nDuring the initial execution, a `return` will continue execution\nin the cleanup code, which finalizes the current DOM block and pops\nthe current frame.\n\nDuring the updating execution, a `return` will exit the updating\nroutine, as it can reuse the DOM block and is always only a single\nframe deep.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
       "line": 78,
       "description": "<Foo/>\n<Foo></Foo>\n<Foo @arg={{true}} />",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
       "line": 144,
       "description": "(helper)\n(helper arg)",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
       "line": 191,
       "description": "<div {{modifier}}/>\n<div {{modifier arg}}/>\n<Foo {{modifier}}/>",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
       "line": 254,
       "description": "{{component-or-helper arg}}",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
       "line": 344,
       "description": "{{maybeHelperOrComponent}}",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21604,7 +21581,7 @@
           "description": ""
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21617,7 +21594,7 @@
           "description": "an optional list of positional arguments"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21630,7 +21607,7 @@
           "description": "whether to interpolate a string as raw HTML (corresponds to\ntriple curlies)"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21643,7 +21620,7 @@
           "description": "A JavaScript primitive (undefined, null, boolean, number or string)"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21656,7 +21633,7 @@
           "description": "A JavaScript primitive (undefined, null, boolean, number or string)"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21681,7 +21658,7 @@
           "description": "An optional list of named arguments (name + expression) to compile"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21702,7 +21679,7 @@
           "description": "An optional list of named arguments (name + expression) to compile"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21719,69 +21696,69 @@
           "description": "a function that returns a list of statements to evaluate"
         }
       ],
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/template.ts",
       "line": 39,
       "description": "Wraps a template js in a template module to change it into a factory\nthat handles lazy parsing the template and to create per env singletons\nof the template.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/owner/index.ts",
       "line": 8,
       "description": "Framework objects in a Glimmer application may receive an owner object.\nGlimmer is unopinionated about this owner, but will forward it through its\ninternal resolution system, and through its managers if it is provided.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/owner/index.ts",
       "line": 17,
       "description": "`setOwner` set's an object's owner",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/program/lib/util/default-template.ts",
       "line": 4,
       "description": "Default component template, which is a plain yield",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/program/lib/program.ts",
       "line": 20,
       "description": "The Program Heap is responsible for dynamically allocating\nmemory in which we read/write the VM's instructions\nfrom/to. When we malloc we pass out a VMHandle, which\nis used as an indirect way of accessing the memory during\nexecution of the VM. Internally we track the different\nregions of the memory in an int array known as the table.\n\nThe table 32-bit aligned and has the following layout:\n\n| ... | hp (u32) |       info (u32)   | size (u32) |\n| ... |  Handle  | Scope Size | State | Size       |\n| ... | 32bits   | 30bits     | 2bits | 32bit      |\n\nWith this information we effectively have the ability to\ncontrol when we want to free memory. That being said you\ncan not free during execution as raw address are only\nvalid during the execution. This means you cannot close\nover them as you will have a bad memory access exception.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/program/lib/program.ts",
       "line": 122,
       "description": "The heap uses the [Mark-Compact Algorithm](https://en.wikipedia.org/wiki/Mark-compact_algorithm) to shift\nreachable memory to the bottom of the heap and freeable\nmemory to the top of the heap. When we have shifted all\nthe reachable memory to the top of the heap, we move the\noffset to the next free position.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/reference/lib/iterable.ts",
       "line": 135,
       "description": "When iterating over a list, it's possible that an item with the same unique\nkey could be encountered twice:\n\n```js\nlet arr = ['same', 'different', 'same', 'same'];\n```\n\nIn general, we want to treat these items as _unique within the list_. To do\nthis, we track the occurences of every item as we iterate the list, and when\nan item occurs more than once, we generate a new unique key just for that\nitem, and that occurence within the list. The next time we iterate the list,\nand encounter an item for the nth time, we can get the _same_ key, and let\nGlimmer know that it should reuse the DOM for the previous nth occurence.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/compiled/opcodes/component.ts",
       "line": 107,
       "description": "The VM creates a new ComponentInstance data structure for every component\ninvocation it encounters.\n\nSimilar to how a ComponentDefinition contains state about all components of a\nparticular type, a ComponentInstance contains state specific to a particular\ninstance of a component type. It also contains a pointer back to its\ncomponent type's ComponentDefinition.",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/component/interfaces.ts",
       "line": 8,
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
@@ -21805,3537 +21782,4877 @@
       "category": [
         "EMBER_GLIMMER_SET_COMPONENT_TEMPLATE"
       ],
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
-    },
-    {
-      "file": "packages/@glimmer/runtime/lib/helpers/array.ts",
-      "line": 8,
-      "description": "Use the `{{array}}` helper to create an array to pass as an option to your\ncomponents.\n\n```handlebars\n<MyComponent @people={{array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson}}\n/>\n```\n or\n```handlebars\n{{yield people=(array\n  'Tom Dale'\n  'Yehuda Katz'\n  this.myOtherPerson)\n}}\n```\n\nWould result in an object such as:\n\n```js\n['Tom Dale', 'Yehuda Katz', this.get('myOtherPerson')]\n```\n\nWhere the 3rd item in the array is bound to updates of the `myOtherPerson` property.",
-      "itemtype": "method",
-      "name": "array",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Array"
-        }
-      ],
-      "return": {
-        "description": "Array",
-        "type": "Array"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
-    },
-    {
-      "file": "packages/@glimmer/runtime/lib/helpers/concat.ts",
-      "line": 18,
-      "description": "Concatenates the given arguments into a string.\n\nExample:\n\n\n```gjs\nimport { concat } from '@ember/helper';\n\n<template>\n{{yield (concat firstName \" \" lastName)}}\n\n{{! would yield name=\"<first name value> <last name value>\" to the component}}\n</template>\n```\n\nor for angle bracket invocation, you actually don't need concat at all.\n\n```handlebars\n<SomeComponent @name=\"{{firstName}} {{lastName}}\" />\n```",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "concat",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/eq.ts",
       "line": 3,
       "description": "Performs a strict equality comparison.\n\nleft === right",
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
-    },
-    {
-      "file": "packages/@glimmer/runtime/lib/helpers/fn.ts",
-      "line": 18,
-      "description": "The `fn` helper allows you to ensure a function that you are passing off\nto another component, helper, or modifier has access to arguments that are\navailable in the template.\n\nFor example, if you have an `each` helper looping over a number of items, you\nmay need to pass a function that expects to receive the item as an argument\nto a component invoked within the loop. Here's how you could use the `fn`\nhelper to pass both the function and its arguments together:\n\n```app/components/items-listing.gjs\nimport DisplayItem from './display-item';\n  \n<template>\n  {{#each @items as |item|}}\n    <DisplayItem @item=item @select={{fn this.handleSelected item}} />\n  {{/each}}\n</template>\n```\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class ItemsList extends Component {\n  handleSelected = (item) => {\n    // ...snip...\n  }\n}\n```\n\nIn this case the `DisplayItem` component will receive a normal function\nthat it can invoke. When it invokes the function, the `handleSelected`\nfunction will receive the `item` and any arguments passed, thanks to the\n`fn` helper.\n\nLet's take look at what that means in a couple circumstances:\n\n- When invoked as `this.args.select()` the `handleSelected` function will\n  receive the `item` from the loop as its first and only argument.\n- When invoked as `this.args.select('foo')` the `handleSelected` function\n  will receive the `item` from the loop as its first argument and the\n  string `'foo'` as its second argument.\n\nIn the example above, we used an arrow function to ensure that\n`handleSelected` is properly bound to the `items-list`, but let's explore what\nhappens if we left out the arrow function:\n\n```app/components/items-list.gjs\nimport Component from '@glimmer/component';\n\nexport default class ItemsList extends Component {\n  handleSelected(item) {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when `handleSelected` is invoked inside the `display-item`\ncomponent, it will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via an arrow function or other means) before passing into `fn`!\n\nSee also [partial application](https://en.wikipedia.org/wiki/Partial_application).\n\n`fn` is built-in and does not require any additional imports.",
-      "itemtype": "method",
-      "name": "fn",
-      "access": "public",
-      "tagname": "",
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
-    },
-    {
-      "file": "packages/@glimmer/runtime/lib/helpers/get.ts",
-      "line": 12,
-      "description": "Dynamically look up a property on an object. The second argument to `{{get}}`\nshould have a string value, although it can be bound.\n\nFor example, these two usages are equivalent:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n\nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n  \n  <template>\n    {{this.developer.name}}\n    {{get this.developer \"name\"}}\n  </template>\n}\n```\n\nIf there were several facts about a person, the `{{get}}` helper can dynamically\npick one:\n\n```app/templates/application.gjs\n<template>\n  <DeveloperDetail @factName=\"language\" />\n</template>\n```\n\n```handlebars\n{{get this.developer @factName}}\n```\n\nFor a more complex example, this template would allow the user to switch\nbetween showing the user's height and weight with a click:\n\n```app/components/developer-detail.gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { get } from '@ember/object';\n  \nexport default class extends Component {\n  @tracked developer = {\n    name: \"Sandi Metz\",\n    language: \"Ruby\"\n  }\n\n  @tracked currentFact = 'name'\n\n  showFact = (fact) => {\n    this.currentFact = fact;\n  }\n  \n  <template>\n    {{get this.developer this.currentFact}}\n\n    <button {{on 'click' (fn this.showFact \"name\")}}>Show name</button>\n    <button {{on 'click' (fn this.showFact \"language\")}}>Show language</button>\n  </template>\n}\n```",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "get",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/gt.ts",
       "line": 3,
       "description": "Performs a greater than comparison.\n\nleft > right",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/gte.ts",
       "line": 3,
       "description": "Performs a greater than or equal comparison.\n\nleft >= right",
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
-    },
-    {
-      "file": "packages/@glimmer/runtime/lib/helpers/hash.ts",
-      "line": 8,
-      "description": "Use the `{{hash}}` helper to create a hash to pass as an option to your\ncomponents. This is especially useful for contextual components where you can\njust yield a hash:\n\n```handlebars\n{{yield (hash\n   name='Sarah'\n   title=office\n)}}\n```\n\nWould result in an object such as:\n\n```js\n{ name: 'Sarah', title: this.get('office') }\n```\n\nWhere the `title` is bound to updates of the `office` property.\n\nNote that the hash is an empty object with no prototype chain, therefore\ncommon methods like `toString` are not available in the resulting hash.\nIf you need to use such a method, you can use the `call` or `apply`\napproach:\n\n```js\nfunction toString(obj) {\n  return Object.prototype.toString.apply(obj);\n}\n```",
-      "itemtype": "method",
-      "name": "hash",
-      "params": [
-        {
-          "name": "options",
-          "description": "",
-          "type": "Object"
-        }
-      ],
-      "return": {
-        "description": "Hash",
-        "type": "Object"
-      },
-      "access": "public",
-      "tagname": "",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/lt.ts",
       "line": 3,
       "description": "Performs a less than comparison.\n\nleft < right",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/lte.ts",
       "line": 3,
       "description": "Performs a less than or equal comparison.\n\nleft <= right",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/helpers/neq.ts",
       "line": 3,
       "description": "Performs a strict inequality comparison.\n\nleft !== right",
-      "class": "@glimmer/tracking",
+      "class": "Keywords",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
-      "line": 249,
-      "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePostComponent extends Component {\n  saveLike = () => {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```app/components/like-post.hbs\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used an arrow function to ensure that `likePost` is\nproperly bound to the `items-list`, but let's explore what happens if we\nleft out the arrow function:\n\n```app/components/like-post.gjs\nimport Component from '@glimmer/component';\n\nexport default class LikePostComponent extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via an arrow function or other means) before passing into `on`!",
+      "line": 253,
+      "description": "The `{{on}}` modifier lets you easily add event listeners (it uses\n[EventTarget.addEventListener](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)\ninternally).\n\nFor example, if you'd like to run a function on your component when a `<button>`\nin the components template is clicked you might do something like:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\nimport { action } from '@ember/object';\n\nexport default class LikePost extends Component {\n  @action\n  saveLike() {\n    // someone likes your post!\n    // better send a request off to your server...\n  }\n  \n  <template>\n    <button {{on 'click' this.saveLike}}>Like this post!</button>\n  </template>\n}\n```\n\n### Arguments\n\n`{{on}}` accepts two positional arguments, and a few named arguments.\n\nThe positional arguments are:\n\n- `event` -- the name to use when calling `addEventListener`\n- `callback` -- the function to be passed to `addEventListener`\n\nThe named arguments are:\n\n- capture -- a `true` value indicates that events of this type will be dispatched\n  to the registered listener before being dispatched to any EventTarget beneath it\n  in the DOM tree.\n- once -- indicates that the listener should be invoked at most once after being\n  added. If true, the listener would be automatically removed when invoked.\n- passive -- if `true`, indicates that the function specified by listener will never\n  call preventDefault(). If a passive listener does call preventDefault(), the user\n  agent will do nothing other than generate a console warning. See\n  [Improving scrolling performance with passive listeners](https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#Improving_scrolling_performance_with_passive_listeners)\n  to learn more.\n\nThe callback function passed to `{{on}}` will receive any arguments that are passed\nto the event handler. Most commonly this would be the `event` itself.\n\nIf you would like to pass additional arguments to the function you should use\nthe `{{fn}}` helper.\n\nFor example, in our example case above if you'd like to pass in the post that\nwas being liked when the button is clicked you could do something like:\n\n```hbs\n<button {{on 'click' (fn this.saveLike @post)}}>Like this post!</button>\n```\n\nIn this case, the `saveLike` function will receive two arguments: the click event\nand the value of `@post`.\n\n### Function Context\n\nIn the example above, we used `@action` to ensure that `likePost` is\nproperly bound to the `LikePost` Component, but let's explore what happens if we\nleft out `@action`:\n\n```gjs {data-filename=\"app/components/like-post.gjs\"}\nimport Component from '@glimmer/component';\n\nexport default class LikePost extends Component {\n  saveLike() {\n    // ...snip...\n  }\n}\n```\n\nIn this example, when the button is clicked `saveLike` will be invoked,\nit will **not** have access to the component instance. In other\nwords, it will have no `this` context, so please make sure your functions\nare bound (via `@action` or other means) before passing into `on`!\n\nThe `on` modifier is a keyword and does not need to be imported.",
       "itemtype": "method",
       "name": "on",
+      "static": 1,
+      "noimport": "",
       "access": "public",
       "tagname": "",
-      "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "since": "3.11.0",
+      "class": "Keywords",
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 136,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 153,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 171,
       "class": "@glimmer/tracking",
       "description": "Load a value into a syscall register.\n\n## State changes\n\n[$] $register <- `value`\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 184,
       "class": "@glimmer/tracking",
       "description": "Fetch a value from a register (machine or syscall).\n\n## State changes\n\n[ ] get $register\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 327,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 352,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 376,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 403,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 450,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 483,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 506,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 524,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 543,
       "description": "## Opcodes\n\n- Append: `RootScope`\n- Append: `VirtualRootScope`\n\n## State changes\n\n[!] push Scope Stack",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 559,
       "description": "## Opcodes\n\n- Append: `ChildScope`\n\n## State changes\n\n[!] push Scope Stack <- `child` of current Scope",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 572,
       "description": "## Opcodes\n\n- Append: `Yield`\n\n## State changes\n\n[!] push Scope Stack <- `scope`",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 585,
       "description": "## Opcodes\n\n- Append: `PopScope`\n\n## State changes\n\n[!] pop Scope Stack",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 598,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 613,
       "description": "## Opcodes\n\n- Append: `BindDynamicScope`\n\n## State changes:\n\n[!] pop Dynamic Scope Stack `names.length` times",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 630,
       "class": "@glimmer/tracking",
       "description": "## State changes\n\n- [!] push Updating Stack\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 641,
       "class": "@glimmer/tracking",
       "description": "## State changes\n\n[!] pop Updating Stack\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 652,
       "class": "@glimmer/tracking",
       "description": "## State changes\n\n[!] push Updating List\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 667,
       "class": "@glimmer/tracking",
       "description": "## State changes\n\n[-] associate destroyable `child`\n  @utility \n",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 686,
       "description": "Get Tree Builder",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 693,
       "description": "Get current Scope",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 700,
       "description": "Get current Dynamic Scope",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 811,
       "description": "The address of the compiled template. This is converted into a\npc when the VM is created.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 817,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 823,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 832,
       "description": "The program counter that subsequent evaluations should start from.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 837,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 843,
       "description": "The current value of the VM's dynamic scope",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 848,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/append.ts",
       "line": 855,
       "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": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts",
       "line": 135,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts",
       "line": 144,
       "description": "<div>   <---------------  currentCursor.element\n  <!--%+b:1%--> <-------  would have been removed during openBlock\n  <div> <---------------  currentCursor.candidate -> cursor.element\n    <!--%+b:2%--> <-----  currentCursor.candidate.firstChild -> cursor.candidate\n    Foo\n    <!--%-b:2%-->\n  </div>\n  <!--%-b:1%-->  <------  becomes currentCursor.candidate",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/curried-value.ts",
       "line": 37,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/environment.ts",
       "line": 188,
       "description": "Used to determine the the environment is interactive (e.g. SSR is not\ninteractive). Interactive environments schedule modifiers, among other things.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/environment.ts",
       "line": 194,
       "description": "Used to enable debug tooling",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/environment.ts",
       "line": 199,
       "description": "Callback to be called when an environment transaction commits",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/scope.ts",
       "line": 45,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/scope.ts",
       "line": 47,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
       "file": "packages/@glimmer/runtime/lib/scope.ts",
       "line": 86,
       "debug": "",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/generation/printer.ts",
-      "line": 33,
-      "description": "Used to override the mechanism of printing a given AST.Node.\n\nThis will generally only be useful to source -> source codemods\nwhere you would like to specialize/override the way a given node is\nprinted (e.g. you would like to preserve as much of the original\nformatting as possible).\n\nWhen the provided override returns undefined, the default built in printing\nwill be done for the AST.Node.",
-      "params": [
-        {
-          "name": "ast",
-          "description": "the ast node to be printed"
-        },
-        {
-          "name": "options",
-          "description": "the options specified during the print() invocation"
-        }
-      ],
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 74,
+      "description": "Examples when true:\n - link\n - liNK\n\nExamples when false:\n - Link (component)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/generation/printer.ts",
-      "line": 50,
-      "description": "Examples when true:\n - link\n - liNK\n\nExamples when false:\n - Link (component)",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 531,
+      "description": "This includes the full list of keywords currently in use in the template\nlanguage, and where their valid usages are.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
-      "line": 633,
-      "description": "ASTPlugins can make changes to the Glimmer template AST before\ncompilation begins.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 563,
+      "description": "An object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function does nothing (and is removed\nby the minifier in builder).",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
-      "line": 663,
-      "description": "Additional non-native keywords.\n\nLocal variables (block params or lexical scope) always takes precedence,\nbut otherwise, suitable free variable candidates (e.g. those are not part\nof a path) are matched against this list and turned into keywords.\n\nIn strict mode compilation, keywords suppresses the undefined reference\nerror and will be resolved by the runtime environment.\n\nIn loose mode, keywords are currently ignored and since all free variables\nare already resolved by the runtime environment.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 594,
+      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\n\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
-      "line": 678,
-      "description": "In loose mode, this hook allows embedding environments to customize the name of an\nangle-bracket component. In practice, this means that `<HelloWorld />` in Ember is\ncompiled by Glimmer as an invocation of a component named `hello-world`.\n\nIt's a little weird that this is needed in addition to the resolver, but it's a\nclassic-only feature and it seems fine to leave it alone for classic consumers.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 603,
+      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
-      "line": 709,
-      "description": "Useful for specifying a group of options together.\n\nWhen `'codemod'` we disable all whitespace control in handlebars\n(to preserve as much as possible) and we also avoid any\nescaping/unescaping of HTML entity codes.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 3181,
+      "description": "generated from https://raw.githubusercontent.com/w3c/html/26b5126f96f736f796b9e29718138919dd513744/entities.json\ndo not edit",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 1,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5951,
       "description": "We have already computed the character position of this offset or span.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 6,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5956,
       "description": "This offset or span was instantiated with a Handlebars SourcePosition or SourceLocation. Its\ncharacter position will be computed on demand.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 12,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5962,
       "description": "for (rare) situations where a node is created but there was no source location (e.g. the name\n\"default\" in default blocks when the word \"default\" never appeared in source). This is used\nby the internals when there is a legitimate reason for the internals to synthesize a node\nwith no location.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 21,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5971,
       "description": "For situations where a node represents zero parts of the source (for example, empty arguments).\nIn general, we attempt to assign these nodes *some* position (empty arguments can be\npositioned immediately after the callee), but it's not always possible",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 29,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5979,
       "description": "For situations where a source location was expected, but it didn't correspond to the node in\nthe source. This happens if a plugin creates broken locations.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
-      "line": 38,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5986,
       "description": "These kinds  describe spans that don't have a concrete location in the original source.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/match.ts",
-      "line": 9,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 5994,
       "description": "This file implements the DSL used by span and offset in places where they need to exhaustively\nconsider all combinations of states (Handlebars offsets, character offsets and invisible/broken\noffsets).\n\nIt's probably overkill, but it makes the code that uses it clear. It could be refactored or\nremoved.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/match.ts",
-      "line": 110,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6054,
       "description": "You didn't exhaustively match all possibilities.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 11,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6117,
+      "description": "All spans have these details in common.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6121,
+      "description": "A `SourceSpan` object represents a span of characters inside of a template source.\n\nThere are three kinds of `SourceSpan` objects:\n\n- `ConcreteSourceSpan`, which contains byte offsets\n- `LazySourceSpan`, which contains `SourceLocation`s from the Handlebars AST, which can be\n  converted to byte offsets on demand.\n- `InvisibleSourceSpan`, which represent source strings that aren't present in the source,\n  because:\n    - they were created synthetically\n    - their location is nonsensical (the span is broken)\n    - they represent nothing in the source (this currently happens only when a bug in the\n      upstream Handlebars parser fails to assign a location to empty blocks)\n\nAt a high level, all `SourceSpan` objects provide:\n\n- byte offsets\n- source in column and line format\n\nAnd you can do these operations on `SourceSpan`s:\n\n- collapse it to a `SourceSpan` representing its starting or ending position\n- slice out some characters, optionally skipping some characters at the beginning or end\n- create a new `SourceSpan` with a different starting or ending offset\n\nAll SourceSpan objects implement `SourceLocation`, for compatibility. All SourceSpan\nobjects have a `toJSON` that emits `SourceLocation`, also for compatibility.\n\nFor compatibility, subclasses of `AbstractSourceSpan` must implement `locDidUpdate`, which\nhappens when an AST plugin attempts to modify the `start` or `end` of a span directly.\n\nThe goal is to avoid creating any problems for use-cases like AST Explorer.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6214,
+      "description": "Get the starting `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6221,
+      "description": "Get the ending `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6228,
+      "description": "Support converting ASTv1 nodes into a serialized format using JSON.stringify.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6235,
+      "description": "Create a new span with the current span's end and a new beginning.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6242,
+      "description": "Create a new span with the current span's beginning and a new ending.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6252,
+      "description": "Convert this `SourceSpan` into a `SourceSlice`.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6264,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use startPosition instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6273,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use withStart instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6284,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use endPosition instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6293,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use withEnd instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6304,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use module instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6567,
       "description": "All positions have these details in common. Most notably, all three kinds of positions can\nmust be able to attempt to convert themselves into {@see CharPosition}.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 21,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6572,
       "description": "Used to indicate that an attempt to convert a `SourcePosition` to a character offset failed. It\nis separate from `null` so that `null` can be used to indicate that the computation wasn't yet\nattempted (and therefore to cache the failure)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 31,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6578,
       "description": "A `SourceOffset` represents a single position in the source.\n\nThere are three kinds of backing data for `SourceOffset` objects:\n\n- `CharPosition`, which contains a character offset into the raw source string\n- `HbsPosition`, which contains a `SourcePosition` from the Handlebars AST, which can be\n  converted to a `CharPosition` on demand.\n- `InvisiblePosition`, which represents a position not in source (@see {InvisiblePosition})",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 42,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6589,
       "description": "Create a `SourceOffset` from a Handlebars `SourcePosition`. It's stored as-is, and converted\ninto a character offset on demand, which avoids unnecessarily computing the offset of every\n`SourceLocation`, but also means that broken `SourcePosition`s are not always detected.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 51,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6598,
       "description": "Create a `SourceOffset` that corresponds to a broken `SourcePosition`. This means that the\ncalling code determined (or knows) that the `SourceLocation` doesn't correspond correctly to\nany part of the source.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 62,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6610,
       "description": "Get the character offset for this `SourceOffset`, if possible.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 70,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6618,
       "description": "Compare this offset with another one.\n\nIf both offsets are `HbsPosition`s, they're equivalent as long as their lines and columns are\nthe same. This avoids computing offsets unnecessarily.\n\nOtherwise, two `SourceOffset`s are equivalent if their successfully computed character offsets\nare the same.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 83,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6631,
       "description": "Create a span that starts from this source offset and ends with another source offset. Avoid\ncomputing character offsets if both `SourceOffset`s are still lazy.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 91,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6639,
       "description": "Create a `SourceOffset` by moving the character position represented by this source offset\nforward or backward (if `by` is negative), if possible.\n\nIf this `SourceOffset` can't compute a valid character offset, `move` returns a broken offset.\n\nIf the resulting character offset is less than 0 or greater than the size of the source, `move`\nreturns a broken offset.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 116,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6662,
       "description": "Create a new `SourceSpan` that represents a collapsed range at this source offset. Avoid\ncomputing the character offset if it has not already been computed.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 124,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6670,
       "description": "Convert this `SourceOffset` into a Handlebars {@see SourcePosition} for compatibility with\nexisting plugins.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 136,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6681,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 144,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6688,
       "description": "This is already a `CharPosition`.\n\n{@see HbsPosition} for the alternative.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 153,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6697,
       "description": "Produce a Handlebars {@see SourcePosition} for this `CharPosition`. If this `CharPosition` was\ncomputed using {@see SourceOffset#move}, this will compute the `SourcePosition` for the offset.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 166,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6709,
       "description": "A `CharPosition` always has an offset it can produce without any additional computation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 173,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6716,
       "description": "Convert the current character offset to an `HbsPosition`, if it was not already computed. Once\na `CharPosition` has computed its `HbsPosition`, it will not need to do compute it again, and\nthe same `CharPosition` is retained when used as one of the ends of a `SourceSpan`, so\ncomputing the `HbsPosition` should be a one-time operation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 209,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6744,
       "description": "Lazily compute the character offset from the {@see SourcePosition}. Once an `HbsPosition` has\ncomputed its `CharPosition`, it will not need to do compute it again, and the same\n`HbsPosition` is retained when used as one of the ends of a `SourceSpan`, so computing the\n`CharPosition` should be a one-time operation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 231,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6763,
       "description": "Return the {@see SourcePosition} that this `HbsPosition` was instantiated with. This operation\ndoes not need to compute anything.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 243,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6774,
       "description": "This is already an `HbsPosition`.\n\n{@see CharPosition} for the alternative.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 260,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6791,
       "description": "A broken position cannot be turned into a {@see CharacterPosition}.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 267,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6798,
       "description": "The serialization of an `InvisiblePosition is whatever Handlebars {@see SourcePosition} was\noriginally identified as broken, non-existent or synthetic.\n\nIf an `InvisiblePosition` never had an source offset at all, this method returns\n{@see UNKNOWN_POSITION} for compatibility.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
-      "line": 287,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6816,
       "description": "Compare two {@see AnyPosition} and determine whether they are equal.",
       "see": [
         "{SourceOffset#eql}"
       ],
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 24,
-      "description": "All spans have these details in common.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6845,
+      "description": "Validate that the character offset represents a position in the source string.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 30,
-      "description": "Convert this span into a string. If the span is broken, return `''`.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 7820,
+      "description": "The Parser Builder differentiates from the public builder API by:\n\n1. Offering fewer different ways to instantiate nodes\n2. Mandating source locations",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 35,
-      "description": "Gets the module the span was located in.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9349,
+      "description": "ASTPlugins can make changes to the Glimmer template AST before\ncompilation begins.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 40,
-      "description": "Get the starting position for this span. Try to avoid creating new position objects, as they\ncache computations.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9417,
+      "description": "Gets the correct Token from the Node based on it's type",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 46,
-      "description": "Get the ending position for this span. Try to avoid creating new position objects, as they\ncache computations.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9460,
+      "description": "Adds tokens to the tokensSet based on their node.type",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 52,
-      "description": "Compute the `SourceLocation` for this span, returned as an instance of `HbsSpan`.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9473,
+      "description": "Parses and traverses a given handlebars html template to extract all template locals\nreferenced that could possible come from the parent scope. Can exclude known keywords\noptionally.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 57,
-      "description": "For compatibility, whenever the `start` or `end` of a {@see SourceOffset} changes, spans are\nnotified of the change so they can update themselves. This shouldn't happen outside of AST\nplugins.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9536,
+      "description": "This is a convenience function for creating ASTv2 nodes, with an optional name and the node's\noptions.\n\n```ts\nexport class HtmlText extends node('HtmlText').fields<{ chars: string }>() {}\n```\n\nThis creates a new ASTv2 node with the name `'HtmlText'` and one field `chars: string` (in\naddition to a `loc: SourceOffsets` field, which all nodes have).\n\n```ts\nexport class Args extends node().fields<{\n positional: PositionalArguments;\n named: NamedArguments\n}>() {}\n```\n\nThis creates a new un-named ASTv2 node with two fields (`positional: Positional` and `named:\nNamed`, in addition to the generic `loc: SourceOffsets` field).\n\nOnce you create a node using `node`, it is instantiated with all of its fields (including `loc`):\n\n```ts\nnew HtmlText({ loc: offsets, chars: someString });\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 64,
-      "description": "Serialize into a {@see SerializedSourceSpan}, which is compact and designed for readability in\ncontext like AST Explorer. If you need a {@see SourceLocation}, use {@see toJSON}.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9596,
+      "description": "Corresponds to syntaxes with positional and named arguments:\n\n- SubExpression\n- Invoking Append\n- Invoking attributes\n- InvokeBlock\n\nIf `Args` is empty, the `SourceOffsets` for this node should be the collapsed position\nimmediately after the parent call node's `callee`.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 71,
-      "description": "A `SourceSpan` object represents a span of characters inside of a template source.\n\nThere are three kinds of `SourceSpan` objects:\n\n- `ConcreteSourceSpan`, which contains byte offsets\n- `LazySourceSpan`, which contains `SourceLocation`s from the Handlebars AST, which can be\n  converted to byte offsets on demand.\n- `InvisibleSourceSpan`, which represent source strings that aren't present in the source,\n  because:\n    - they were created synthetically\n    - their location is nonsensical (the span is broken)\n    - they represent nothing in the source (this currently happens only when a bug in the\n      upstream Handlebars parser fails to assign a location to empty blocks)\n\nAt a high level, all `SourceSpan` objects provide:\n\n- byte offsets\n- source in column and line format\n\nAnd you can do these operations on `SourceSpan`s:\n\n- collapse it to a `SourceSpan` representing its starting or ending position\n- slice out some characters, optionally skipping some characters at the beginning or end\n- create a new `SourceSpan` with a different starting or ending offset\n\nAll SourceSpan objects implement `SourceLocation`, for compatibility. All SourceSpan\nobjects have a `toJSON` that emits `SourceLocation`, also for compatibility.\n\nFor compatibility, subclasses of `AbstractSourceSpan` must implement `locDidUpdate`, which\nhappens when an AST plugin attempts to modify the `start` or `end` of a span directly.\n\nThe goal is to avoid creating any problems for use-cases like AST Explorer.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9633,
+      "description": "Corresponds to positional arguments.\n\nIf `PositionalArguments` is empty, the `SourceOffsets` for this node should be the collapsed\nposition immediately after the parent call node's `callee`.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 170,
-      "description": "Get the starting `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9657,
+      "description": "Corresponds to named arguments.\n\nIf `PositionalArguments` and `NamedArguments` are empty, the `SourceOffsets` for this node should\nbe the same as the `Args` node that contains this node.\n\nIf `PositionalArguments` is not empty but `NamedArguments` is empty, the `SourceOffsets` for this\nnode should be the collapsed position immediately after the last positional argument.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 177,
-      "description": "Get the ending `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9685,
+      "description": "Corresponds to a single named argument.\n\n```hbs\nx=<expr>\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 184,
-      "description": "Support converting ASTv1 nodes into a serialized format using JSON.stringify.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9703,
+      "description": "Attr nodes look like HTML attributes, but are classified as:\n\n1. `HtmlAttr`, which means a regular HTML attribute in Glimmer\n2. `SplatAttr`, which means `...attributes`\n3. `ComponentArg`, which means an attribute whose name begins with `@`, and it is therefore a\n   component argument.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 191,
-      "description": "Create a new span with the current span's end and a new beginning.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9712,
+      "description": "`HtmlAttr` and `SplatAttr` are grouped together because the order of the `SplatAttr` node,\nrelative to other attributes, matters.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 198,
-      "description": "Create a new span with the current span's beginning and a new ending.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9717,
+      "description": "\"Attr Block\" nodes are allowed inside an open element tag in templates. They interact with the\nelement (or component).",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 209,
-      "description": "Convert this `SourceSpan` into a `SourceSlice`.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9722,
+      "description": "`HtmlAttr` nodes are valid HTML attributes, with or without a value.\n\nExceptions:\n\n- `...attributes` is `SplatAttr`\n- `@x=<value>` is `ComponentArg`",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 227,
-      "description": "For compatibility with SourceLocation in AST plugins",
-      "deprecated": true,
-      "deprecationMessage": "use startPosition instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9733,
+      "description": "Corresponds to an argument passed by a component (`@x=<value>`)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 236,
-      "description": "For compatibility with SourceLocation in AST plugins",
-      "deprecated": true,
-      "deprecationMessage": "use withStart instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9737,
+      "description": "Convert the component argument into a named argument node",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 245,
-      "description": "For compatibility with SourceLocation in AST plugins",
-      "deprecated": true,
-      "deprecationMessage": "use endPosition instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9748,
+      "description": "An `ElementModifier` is just a normal call node in modifier position.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 254,
-      "description": "For compatibility with SourceLocation in AST plugins",
-      "deprecated": true,
-      "deprecationMessage": "use withEnd instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9753,
+      "description": "Content Nodes are allowed in content positions in templates. They correspond to behavior in the\n[Data][data] tokenization state in HTML.\n\n[data]: https://html.spec.whatwg.org/multipage/parsing.html#data-state",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
-      "line": 263,
-      "description": "For compatibility with SourceLocation in AST plugins",
-      "deprecated": true,
-      "deprecationMessage": "use module instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9780,
+      "description": "Corresponds to a component invocation. When the content of a component invocation contains no\nnamed blocks, `blocks` contains a single named block named `\"default\"`. When a component\ninvocation is self-closing, `blocks` is empty.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/location.ts",
-      "line": 12,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9794,
+      "description": "Corresponds to a simple HTML element. The AST allows component arguments and modifiers to support\nfuture extensions.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/location.ts",
-      "line": 14,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9808,
+      "description": "A Handlebars literal.\n\n{@link https://handlebarsjs.com/guide/expressions.html#literal-segments}",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/location.ts",
-      "line": 29,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9814,
+      "description": "Corresponds to a Handlebars literal.",
+      "see": [
+        "{LiteralValue}"
+      ],
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/source.ts",
-      "line": 16,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9827,
+      "description": "Returns true if an input {@see ExpressionNode} is a literal.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/source.ts",
-      "line": 27,
-      "description": "Validate that the character offset represents a position in the source string.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9844,
+      "description": "Corresponds to a path in expression position.\n\n```hbs\nthis\nthis.x\n@x\n@x.y\nx\nx.y\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/source/source.ts",
-      "line": 92,
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9858,
+      "description": "Corresponds to a known strict-mode keyword. It behaves similarly to a\nPathExpression with a FreeVarReference, but implies StrictResolution and\nis guaranteed to not have a tail, since `{{outlet.foo}}` would have been\nillegal.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/traversal/visitor.ts",
-      "line": 20,
-      "deprecated": true,
-      "deprecationMessage": "use Template or Block instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9866,
+      "description": "Corresponds to a parenthesized call expression.\n\n```hbs\n(x)\n(x.y)\n(x y)\n(x.y z)\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/traversal/visitor.ts",
-      "line": 39,
-      "deprecated": true,
-      "deprecationMessage": "use Template or Block instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9878,
+      "description": "Corresponds to an interpolation in attribute value position.\n\n```hbs\n<a href=\"{{url}}.html\"\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/handlebars-ast.ts",
-      "line": 1,
-      "description": "This file contains types for the raw AST returned from the Handlebars parser.\nThese types were originally imported from\nhttps://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/handlebars/index.d.ts.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9887,
+      "description": "Corresponds to an entire template.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/handlebars-ast.ts",
-      "line": 32,
-      "description": "`loc` is sometimes missing in the upstream Handlebars parser. This is a bug that should be\nfixed. In addition, we should use the types from the upstream parser rather than our own types,\nand if they're not accurate, we should fix them upstream.",
-      "see": [
-        "{https://github.com/handlebars-lang/handlebars-parser/blob/master/types/ast.d.ts}"
-      ],
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9892,
+      "description": "Represents a block. In principle this could be merged with `NamedBlock`, because all cases\ninvolving blocks have at least a notional name.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 22,
-      "description": "string accessor for params.name",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9898,
+      "description": "Corresponds to a collection of named blocks.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 35,
-      "deprecated": true,
-      "deprecationMessage": "use Template or Block instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9902,
+      "description": "Get the `NamedBlock` for a given name.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 63,
-      "deprecated": true,
-      "deprecationMessage": "use trusting instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9910,
+      "description": "Corresponds to a single named block. This is used for anonymous named blocks (`default` and\n`else`).",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 111,
-      "description": "span for the open tag",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9924,
+      "description": "Corresponds to `this` at the head of an expression.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 116,
-      "description": "span for the close tag, null for void or self-closing tags",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9929,
+      "description": "Corresponds to `@<ident>` at the beginning of an expression.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 121,
-      "description": "string accessor for path.original",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9934,
+      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is in the current\nblock's scope.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 126,
-      "description": "string accessor for params.name",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9940,
+      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is *not* in the\ncurrent block's scope.\n\nThe `resolution: FreeVarResolution` field describes how to resolve the free variable.\n\nNote: In strict mode, it must always be a variable that is in a concrete JavaScript scope that\nthe template will be installed into.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 179,
-      "description": "alias for name",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9957,
+      "description": "A free variable is resolved according to a resolution rule:\n\n1. Strict resolution\n2. Namespaced resolution",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 190,
-      "description": "alias for name",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9965,
+      "description": "Strict resolution is used:\n\n1. in a strict mode template\n2. in an local variable invocation with dot paths",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 209,
-      "deprecated": true,
-      "deprecationMessage": "use `head` and `tail` instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9984,
+      "description": "A `LooseModeResolution` includes one or more namespaces to resolve the variable in\n\nIn practice, there are a limited number of possible combinations of these degrees of freedom,\nand they are captured by the `Namespaces` union below.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 213,
-      "deprecated": true,
-      "deprecationMessage": "use `head.type` instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 9991,
+      "description": "Namespaced resolution is used in an unambiguous syntax position:\n\n1. `(sexp)` (namespace: `Helper`)\n2. `{{#block}}` (namespace: `Component`)\n3. `<a {{modifier}}>` (namespace: `Modifier`)\n4. `<Component />` (namespace: `Component`)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 217,
-      "deprecated": true,
-      "deprecationMessage": "use `head.type' instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10003,
+      "description": "Append resolution is used when the variable should be resolved in both the `component` and\n`helper` namespaces.\n\n```hbs\n{{x}}\n```\n\n```hbs\n{{x y}}\n```\n\n^ In either case, `x` should be resolved in the `component` and `helper` namespaces.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 234,
-      "deprecated": true,
-      "deprecationMessage": "use value instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10021,
+      "description": "Trusting append resolution is used when the variable should be resolved only in the\n`helper` namespaces.\n\n```hbs\n{{{x}}}\n```\n\n```hbs\n{{{x y}}}\n```\n\n^ In either case, `x` should be resolved in the `helper` namespace.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 244,
-      "deprecated": true,
-      "deprecationMessage": "use value instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10068,
+      "description": "A `Namespaced` must be resolved in one or more namespaces.\n\n```hbs\n<X />\n```\n\n^ `X` is resolved in the `component` namespace\n\n```hbs\n(x)\n```\n\n^ `x` is resolved in the `helper` namespace\n\n```hbs\n<a {{x}} />\n```\n\n^ `x` is resolved in the `modifier` namespace",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 254,
-      "deprecated": true,
-      "deprecationMessage": "use value instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10619,
+      "description": "This corresponds to attribute curlies (<Foo bar={{...}}>).\nIn strict mode, this also corresponds to arg curlies.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 264,
-      "deprecated": true,
-      "deprecationMessage": "use value instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10631,
+      "description": "This corresponds to append positions text curlies.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
-      "line": 274,
-      "deprecated": true,
-      "deprecationMessage": "use value instead",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10645,
+      "description": "A call node has a simple callee if its head is:\n\n- a `PathExpression`\n- the `PathExpression`'s head is a `VarHead`\n- it has no tail\n\nSimple heads:\n\n```\n{{x}}\n{{x y}}\n```\n\nNot simple heads:\n\n```\n{{x.y}}\n{{x.y z}}\n{{@x}}\n{{@x a}}\n{{this}}\n{{this a}}\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v1/parser-builders.ts",
-      "line": 14,
-      "description": "The Parser Builder differentiates from the public builder API by:\n\n1. Offering fewer different ways to instantiate nodes\n2. Mandating source locations",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10702,
+      "description": "A `BlockContext` represents the block that a particular AST node is contained inside of.\n\n`BlockContext` is aware of template-wide options (such as strict mode), as well as the bindings\nthat are in-scope within that block.\n\nConcretely, it has the `PrecompileOptions` and current `SymbolTable`, and provides\nfacilities for working with those options.\n\n`BlockContext` is stateless.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
-      "line": 7,
-      "description": "Corresponds to syntaxes with positional and named arguments:\n\n- SubExpression\n- Invoking Append\n- Invoking attributes\n- InvokeBlock\n\nIf `Args` is empty, the `SourceOffsets` for this node should be the collapsed position\nimmediately after the parent call node's `callee`.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10784,
+      "description": "An `ExpressionNormalizer` normalizes expressions within a block.\n\n`ExpressionNormalizer` is stateless.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
-      "line": 51,
-      "description": "Corresponds to positional arguments.\n\nIf `PositionalArguments` is empty, the `SourceOffsets` for this node should be the collapsed\nposition immediately after the parent call node's `callee`.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10794,
+      "description": "The `normalize` method takes an arbitrary expression and its original syntax context and\nnormalizes it to an ASTv2 expression.",
+      "see": [
+        "{SyntaxContext}"
+      ],
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
-      "line": 80,
-      "description": "Corresponds to named arguments.\n\nIf `PositionalArguments` and `NamedArguments` are empty, the `SourceOffsets` for this node should\nbe the same as the `Args` node that contains this node.\n\nIf `PositionalArguments` is not empty but `NamedArguments` is empty, the `SourceOffsets` for this\nnode should be the collapsed position immediately after the last positional argument.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10848,
+      "description": "The `callParts` method takes ASTv1.CallParts as well as a syntax context and normalizes\nit to an ASTv2 CallParts.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
-      "line": 114,
-      "description": "Corresponds to a single named argument.\n\n```hbs\nx=<expr>\n```",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10890,
+      "description": "The `ref` method normalizes an `ASTv1.PathHead` into an `ASTv2.VariableReference`.\nThis method is extremely important, because it is responsible for normalizing free\nvariables into an an ASTv2.PathHead *with appropriate context*.\n\nThe syntax context is originally determined by the syntactic position that this `PathHead`\ncame from, and is ultimately attached to the `ASTv2.VariableReference` here. In ASTv2,\nthe `VariableReference` node bears full responsibility for loose mode rules that control\nthe behavior of free variables.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 8,
-      "description": "Attr nodes look like HTML attributes, but are classified as:\n\n1. `HtmlAttr`, which means a regular HTML attribute in Glimmer\n2. `SplatAttr`, which means `...attributes`\n3. `ComponentArg`, which means an attribute whose name begins with `@`, and it is therefore a\n   component argument.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 10941,
+      "description": "`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 18,
-      "description": "`HtmlAttr` and `SplatAttr` are grouped together because the order of the `SplatAttr` node,\nrelative to other attributes, matters.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11019,
+      "description": "Normalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 24,
-      "description": "\"Attr Block\" nodes are allowed inside an open element tag in templates. They interact with the\nelement (or component).",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11059,
+      "description": "Normalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 30,
-      "description": "`HtmlAttr` nodes are valid HTML attributes, with or without a value.\n\nExceptions:\n\n- `...attributes` is `SplatAttr`\n- `@x=<value>` is `ComponentArg`",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11102,
+      "description": "Normalizes an ASTv1.ElementNode to:\n\n- ASTv2.NamedBlock if the tag name begins with `:`\n- ASTv2.Component if the tag name matches the component heuristics\n- ASTv2.SimpleElement if the tag name doesn't match the component heuristics\n\nA tag name represents a component if:\n\n- it begins with `@`\n- it is exactly `this` or begins with `this.`\n- the part before the first `.` is a reference to an in-scope variable binding\n- it begins with an uppercase character",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 42,
-      "description": "Corresponds to an argument passed by a component (`@x=<value>`)",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11177,
+      "description": "This method handles attribute values that are curlies, as well as curlies nested inside of\ninterpolations:\n\n```hbs\n<a href={{url}} />\n<a href=\"{{url}}.html\" />\n```",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 46,
-      "description": "Convert the component argument into a named argument node",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11216,
+      "description": "attrPart is the narrowed down list of valid attribute values that are also\nallowed as a concat part (you can't nest concats).",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
-      "line": 57,
-      "description": "An `ElementModifier` is just a normal call node in modifier position.",
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 11311,
+      "description": "This function classifies the head of an ASTv1.Element into an ASTv2.PathHead (if the\nelement is a component) or `'ElementHead'` (if the element is a simple element).\n\nRules:\n\n1. If the variable is an `@arg`, return an `AtHead`\n2. If the variable is `this`, return a `ThisHead`\n3. If the variable is in the current scope:\n  a. If the scope is the root scope, then return a Free `LocalVarHead`\n  b. Else, return a standard `LocalVarHead`\n4. If the tag name is a path and the variable is not in the current scope, Syntax Error\n5. If the variable is uppercase return a FreeVar(ResolveAsComponentHead)\n6. Otherwise, return `'ElementHead'`",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
-      "line": 13,
-      "description": "Content Nodes are allowed in content positions in templates. They correspond to behavior in the\n[Data][data] tokenization state in HTML.\n\n[data]: https://html.spec.whatwg.org/multipage/parsing.html#data-state",
+      "file": "packages/@glimmer/syntax/lib/generation/printer.ts",
+      "line": 33,
+      "description": "Used to override the mechanism of printing a given AST.Node.\n\nThis will generally only be useful to source -> source codemods\nwhere you would like to specialize/override the way a given node is\nprinted (e.g. you would like to preserve as much of the original\nformatting as possible).\n\nWhen the provided override returns undefined, the default built in printing\nwill be done for the AST.Node.",
+      "params": [
+        {
+          "name": "ast",
+          "description": "the ast node to be printed"
+        },
+        {
+          "name": "options",
+          "description": "the options specified during the print() invocation"
+        }
+      ],
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
-      "line": 66,
-      "description": "Corresponds to a component invocation. When the content of a component invocation contains no\nnamed blocks, `blocks` contains a single named block named `\"default\"`. When a component\ninvocation is self-closing, `blocks` is empty.",
+      "file": "packages/@glimmer/syntax/lib/generation/printer.ts",
+      "line": 50,
+      "description": "Examples when true:\n - link\n - liNK\n\nExamples when false:\n - Link (component)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
-      "line": 92,
-      "description": "Corresponds to a simple HTML element. The AST allows component arguments and modifiers to support\nfuture extensions.",
+      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
+      "line": 633,
+      "description": "ASTPlugins can make changes to the Glimmer template AST before\ncompilation begins.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 9,
-      "description": "A Handlebars literal.\n\n{@link https://handlebarsjs.com/guide/expressions.html#literal-segments}",
+      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
+      "line": 663,
+      "description": "Additional non-native keywords.\n\nLocal variables (block params or lexical scope) always takes precedence,\nbut otherwise, suitable free variable candidates (e.g. those are not part\nof a path) are matched against this list and turned into keywords.\n\nIn strict mode compilation, keywords suppresses the undefined reference\nerror and will be resolved by the runtime environment.\n\nIn loose mode, keywords are currently ignored and since all free variables\nare already resolved by the runtime environment.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 24,
-      "description": "Corresponds to a Handlebars literal.",
-      "see": [
-        "{LiteralValue}"
-      ],
+      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
+      "line": 678,
+      "description": "In loose mode, this hook allows embedding environments to customize the name of an\nangle-bracket component. In practice, this means that `<HelloWorld />` in Ember is\ncompiled by Glimmer as an invocation of a component named `hello-world`.\n\nIt's a little weird that this is needed in addition to the resolver, but it's a\nclassic-only feature and it seems fine to leave it alone for classic consumers.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 37,
-      "description": "Returns true if an input {@see ExpressionNode} is a literal.",
+      "file": "packages/@glimmer/syntax/lib/parser/tokenizer-event-handlers.ts",
+      "line": 709,
+      "description": "Useful for specifying a group of options together.\n\nWhen `'codemod'` we disable all whitespace control in handlebars\n(to preserve as much as possible) and we also avoid any\nescaping/unescaping of HTML entity codes.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 57,
-      "description": "Corresponds to a path in expression position.\n\n```hbs\nthis\nthis.x\n@x\n@x.y\nx\nx.y\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 1,
+      "description": "We have already computed the character position of this offset or span.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 74,
-      "description": "Corresponds to a known strict-mode keyword. It behaves similarly to a\nPathExpression with a FreeVarReference, but implies StrictResolution and\nis guaranteed to not have a tail, since `{{outlet.foo}}` would have been\nillegal.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 6,
+      "description": "This offset or span was instantiated with a Handlebars SourcePosition or SourceLocation. Its\ncharacter position will be computed on demand.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 85,
-      "description": "Corresponds to a parenthesized call expression.\n\n```hbs\n(x)\n(x.y)\n(x y)\n(x.y z)\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 12,
+      "description": "for (rare) situations where a node is created but there was no source location (e.g. the name\n\"default\" in default blocks when the word \"default\" never appeared in source). This is used\nby the internals when there is a legitimate reason for the internals to synthesize a node\nwith no location.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
-      "line": 97,
-      "description": "Corresponds to an interpolation in attribute value position.\n\n```hbs\n<a href=\"{{url}}.html\"\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 21,
+      "description": "For situations where a node represents zero parts of the source (for example, empty arguments).\nIn general, we attempt to assign these nodes *some* position (empty arguments can be\npositioned immediately after the callee), but it's not always possible",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
-      "line": 11,
-      "description": "Corresponds to an entire template.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 29,
+      "description": "For situations where a source location was expected, but it didn't correspond to the node in\nthe source. This happens if a plugin creates broken locations.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
-      "line": 20,
-      "description": "Represents a block. In principle this could be merged with `NamedBlock`, because all cases\ninvolving blocks have at least a notional name.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/kinds.ts",
+      "line": 38,
+      "description": "These kinds  describe spans that don't have a concrete location in the original source.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
-      "line": 28,
-      "description": "Corresponds to a collection of named blocks.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/match.ts",
+      "line": 9,
+      "description": "This file implements the DSL used by span and offset in places where they need to exhaustively\nconsider all combinations of states (Handlebars offsets, character offsets and invisible/broken\noffsets).\n\nIt's probably overkill, but it makes the code that uses it clear. It could be refactored or\nremoved.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
-      "line": 32,
-      "description": "Get the `NamedBlock` for a given name.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/match.ts",
+      "line": 110,
+      "description": "You didn't exhaustively match all possibilities.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
-      "line": 52,
-      "description": "Corresponds to a single named block. This is used for anonymous named blocks (`default` and\n`else`).",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 11,
+      "description": "All positions have these details in common. Most notably, all three kinds of positions can\nmust be able to attempt to convert themselves into {@see CharPosition}.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/node.ts",
-      "line": 10,
-      "description": "This is a convenience function for creating ASTv2 nodes, with an optional name and the node's\noptions.\n\n```ts\nexport class HtmlText extends node('HtmlText').fields<{ chars: string }>() {}\n```\n\nThis creates a new ASTv2 node with the name `'HtmlText'` and one field `chars: string` (in\naddition to a `loc: SourceOffsets` field, which all nodes have).\n\n```ts\nexport class Args extends node().fields<{\n positional: PositionalArguments;\n named: NamedArguments\n}>() {}\n```\n\nThis creates a new un-named ASTv2 node with two fields (`positional: Positional` and `named:\nNamed`, in addition to the generic `loc: SourceOffsets` field).\n\nOnce you create a node using `node`, it is instantiated with all of its fields (including `loc`):\n\n```ts\nnew HtmlText({ loc: offsets, chars: someString });\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 21,
+      "description": "Used to indicate that an attempt to convert a `SourcePosition` to a character offset failed. It\nis separate from `null` so that `null` can be used to indicate that the computation wasn't yet\nattempted (and therefore to cache the failure)",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
-      "line": 6,
-      "description": "Corresponds to `this` at the head of an expression.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 31,
+      "description": "A `SourceOffset` represents a single position in the source.\n\nThere are three kinds of backing data for `SourceOffset` objects:\n\n- `CharPosition`, which contains a character offset into the raw source string\n- `HbsPosition`, which contains a `SourcePosition` from the Handlebars AST, which can be\n  converted to a `CharPosition` on demand.\n- `InvisiblePosition`, which represents a position not in source (@see {InvisiblePosition})",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
-      "line": 11,
-      "description": "Corresponds to `@<ident>` at the beginning of an expression.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 42,
+      "description": "Create a `SourceOffset` from a Handlebars `SourcePosition`. It's stored as-is, and converted\ninto a character offset on demand, which avoids unnecessarily computing the offset of every\n`SourceLocation`, but also means that broken `SourcePosition`s are not always detected.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
-      "line": 16,
-      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is in the current\nblock's scope.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 51,
+      "description": "Create a `SourceOffset` that corresponds to a broken `SourcePosition`. This means that the\ncalling code determined (or knows) that the `SourceLocation` doesn't correspond correctly to\nany part of the source.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
-      "line": 26,
-      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is *not* in the\ncurrent block's scope.\n\nThe `resolution: FreeVarResolution` field describes how to resolve the free variable.\n\nNote: In strict mode, it must always be a variable that is in a concrete JavaScript scope that\nthe template will be installed into.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 62,
+      "description": "Get the character offset for this `SourceOffset`, if possible.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 1,
-      "description": "A free variable is resolved according to a resolution rule:\n\n1. Strict resolution\n2. Namespaced resolution",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 70,
+      "description": "Compare this offset with another one.\n\nIf both offsets are `HbsPosition`s, they're equivalent as long as their lines and columns are\nthe same. This avoids computing offsets unnecessarily.\n\nOtherwise, two `SourceOffset`s are equivalent if their successfully computed character offsets\nare the same.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 15,
-      "description": "Strict resolution is used:\n\n1. in a strict mode template\n2. in an local variable invocation with dot paths",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 83,
+      "description": "Create a span that starts from this source offset and ends with another source offset. Avoid\ncomputing character offsets if both `SourceOffset`s are still lazy.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 40,
-      "description": "A `LooseModeResolution` includes one or more namespaces to resolve the variable in\n\nIn practice, there are a limited number of possible combinations of these degrees of freedom,\nand they are captured by the `Namespaces` union below.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 91,
+      "description": "Create a `SourceOffset` by moving the character position represented by this source offset\nforward or backward (if `by` is negative), if possible.\n\nIf this `SourceOffset` can't compute a valid character offset, `move` returns a broken offset.\n\nIf the resulting character offset is less than 0 or greater than the size of the source, `move`\nreturns a broken offset.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 47,
-      "description": "Namespaced resolution is used in an unambiguous syntax position:\n\n1. `(sexp)` (namespace: `Helper`)\n2. `{{#block}}` (namespace: `Component`)\n3. `<a {{modifier}}>` (namespace: `Modifier`)\n4. `<Component />` (namespace: `Component`)",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 116,
+      "description": "Create a new `SourceSpan` that represents a collapsed range at this source offset. Avoid\ncomputing the character offset if it has not already been computed.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 59,
-      "description": "Append resolution is used when the variable should be resolved in both the `component` and\n`helper` namespaces.\n\n```hbs\n{{x}}\n```\n\n```hbs\n{{x y}}\n```\n\n^ In either case, `x` should be resolved in the `component` and `helper` namespaces.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 124,
+      "description": "Convert this `SourceOffset` into a Handlebars {@see SourcePosition} for compatibility with\nexisting plugins.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 77,
-      "description": "Trusting append resolution is used when the variable should be resolved only in the\n`helper` namespaces.\n\n```hbs\n{{{x}}}\n```\n\n```hbs\n{{{x y}}}\n```\n\n^ In either case, `x` should be resolved in the `helper` namespace.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 136,
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
-      "line": 128,
-      "description": "A `Namespaced` must be resolved in one or more namespaces.\n\n```hbs\n<X />\n```\n\n^ `X` is resolved in the `component` namespace\n\n```hbs\n(x)\n```\n\n^ `x` is resolved in the `helper` namespace\n\n```hbs\n<a {{x}} />\n```\n\n^ `x` is resolved in the `modifier` namespace",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 144,
+      "description": "This is already a `CharPosition`.\n\n{@see HbsPosition} for the alternative.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
-      "line": 49,
-      "description": "This corresponds to attribute curlies (<Foo bar={{...}}>).\nIn strict mode, this also corresponds to arg curlies.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 153,
+      "description": "Produce a Handlebars {@see SourcePosition} for this `CharPosition`. If this `CharPosition` was\ncomputed using {@see SourceOffset#move}, this will compute the `SourcePosition` for the offset.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
-      "line": 63,
-      "description": "This corresponds to append positions text curlies.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 166,
+      "description": "A `CharPosition` always has an offset it can produce without any additional computation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
-      "line": 85,
-      "description": "A call node has a simple callee if its head is:\n\n- a `PathExpression`\n- the `PathExpression`'s head is a `VarHead`\n- it has no tail\n\nSimple heads:\n\n```\n{{x}}\n{{x y}}\n```\n\nNot simple heads:\n\n```\n{{x.y}}\n{{x.y z}}\n{{@x}}\n{{@x a}}\n{{this}}\n{{this a}}\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 173,
+      "description": "Convert the current character offset to an `HbsPosition`, if it was not already computed. Once\na `CharPosition` has computed its `HbsPosition`, it will not need to do compute it again, and\nthe same `CharPosition` is retained when used as one of the ends of a `SourceSpan`, so\ncomputing the `HbsPosition` should be a one-time operation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 68,
-      "description": "A `BlockContext` represents the block that a particular AST node is contained inside of.\n\n`BlockContext` is aware of template-wide options (such as strict mode), as well as the bindings\nthat are in-scope within that block.\n\nConcretely, it has the `PrecompileOptions` and current `SymbolTable`, and provides\nfacilities for working with those options.\n\n`BlockContext` is stateless.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 209,
+      "description": "Lazily compute the character offset from the {@see SourcePosition}. Once an `HbsPosition` has\ncomputed its `CharPosition`, it will not need to do compute it again, and the same\n`HbsPosition` is retained when used as one of the ends of a `SourceSpan`, so computing the\n`CharPosition` should be a one-time operation.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 162,
-      "description": "An `ExpressionNormalizer` normalizes expressions within a block.\n\n`ExpressionNormalizer` is stateless.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 231,
+      "description": "Return the {@see SourcePosition} that this `HbsPosition` was instantiated with. This operation\ndoes not need to compute anything.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 170,
-      "description": "The `normalize` method takes an arbitrary expression and its original syntax context and\nnormalizes it to an ASTv2 expression.",
-      "see": [
-        "{SyntaxContext}"
-      ],
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 243,
+      "description": "This is already an `HbsPosition`.\n\n{@see CharPosition} for the alternative.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 258,
-      "description": "The `callParts` method takes ASTv1.CallParts as well as a syntax context and normalizes\nit to an ASTv2 CallParts.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 260,
+      "description": "A broken position cannot be turned into a {@see CharacterPosition}.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 307,
-      "description": "The `ref` method normalizes an `ASTv1.PathHead` into an `ASTv2.VariableReference`.\nThis method is extremely important, because it is responsible for normalizing free\nvariables into an an ASTv2.PathHead *with appropriate context*.\n\nThe syntax context is originally determined by the syntactic position that this `PathHead`\ncame from, and is ultimately attached to the `ASTv2.VariableReference` here. In ASTv2,\nthe `VariableReference` node bears full responsibility for loose mode rules that control\nthe behavior of free variables.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 267,
+      "description": "The serialization of an `InvisiblePosition is whatever Handlebars {@see SourcePosition} was\noriginally identified as broken, non-existent or synthetic.\n\nIf an `InvisiblePosition` never had an source offset at all, this method returns\n{@see UNKNOWN_POSITION} for compatibility.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 354,
-      "description": "`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/offset.ts",
+      "line": 287,
+      "description": "Compare two {@see AnyPosition} and determine whether they are equal.",
+      "see": [
+        "{SourceOffset#eql}"
+      ],
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 443,
-      "description": "Normalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 24,
+      "description": "All spans have these details in common.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 491,
-      "description": "Normalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 30,
+      "description": "Convert this span into a string. If the span is broken, return `''`.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 545,
-      "description": "Normalizes an ASTv1.ElementNode to:\n\n- ASTv2.NamedBlock if the tag name begins with `:`\n- ASTv2.Component if the tag name matches the component heuristics\n- ASTv2.SimpleElement if the tag name doesn't match the component heuristics\n\nA tag name represents a component if:\n\n- it begins with `@`\n- it is exactly `this` or begins with `this.`\n- the part before the first `.` is a reference to an in-scope variable binding\n- it begins with an uppercase character",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 35,
+      "description": "Gets the module the span was located in.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 630,
-      "description": "This method handles attribute values that are curlies, as well as curlies nested inside of\ninterpolations:\n\n```hbs\n<a href={{url}} />\n<a href=\"{{url}}.html\" />\n```",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 40,
+      "description": "Get the starting position for this span. Try to avoid creating new position objects, as they\ncache computations.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 673,
-      "description": "attrPart is the narrowed down list of valid attribute values that are also\nallowed as a concat part (you can't nest concats).",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 46,
+      "description": "Get the ending position for this span. Try to avoid creating new position objects, as they\ncache computations.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 781,
-      "description": "This function classifies the head of an ASTv1.Element into an ASTv2.PathHead (if the\nelement is a component) or `'ElementHead'` (if the element is a simple element).\n\nRules:\n\n1. If the variable is an `@arg`, return an `AtHead`\n2. If the variable is `this`, return a `ThisHead`\n3. If the variable is in the current scope:\n  a. If the scope is the root scope, then return a Free `LocalVarHead`\n  b. Else, return a standard `LocalVarHead`\n4. If the tag name is a path and the variable is not in the current scope, Syntax Error\n5. If the variable is uppercase return a FreeVar(ResolveAsComponentHead)\n6. Otherwise, return `'ElementHead'`",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 52,
+      "description": "Compute the `SourceLocation` for this span, returned as an instance of `HbsSpan`.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
-      "line": 12,
-      "description": "Gets the correct Token from the Node based on it's type",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 57,
+      "description": "For compatibility, whenever the `start` or `end` of a {@see SourceOffset} changes, spans are\nnotified of the change so they can update themselves. This shouldn't happen outside of AST\nplugins.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
-      "line": 65,
-      "description": "Adds tokens to the tokensSet based on their node.type",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 64,
+      "description": "Serialize into a {@see SerializedSourceSpan}, which is compact and designed for readability in\ncontext like AST Explorer. If you need a {@see SourceLocation}, use {@see toJSON}.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
-      "line": 84,
-      "description": "Parses and traverses a given template to extract all template locals\nreferenced that could possible come from the parent scope. Can exclude known keywords\noptionally.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 71,
+      "description": "A `SourceSpan` object represents a span of characters inside of a template source.\n\nThere are three kinds of `SourceSpan` objects:\n\n- `ConcreteSourceSpan`, which contains byte offsets\n- `LazySourceSpan`, which contains `SourceLocation`s from the Handlebars AST, which can be\n  converted to byte offsets on demand.\n- `InvisibleSourceSpan`, which represent source strings that aren't present in the source,\n  because:\n    - they were created synthetically\n    - their location is nonsensical (the span is broken)\n    - they represent nothing in the source (this currently happens only when a bug in the\n      upstream Handlebars parser fails to assign a location to empty blocks)\n\nAt a high level, all `SourceSpan` objects provide:\n\n- byte offsets\n- source in column and line format\n\nAnd you can do these operations on `SourceSpan`s:\n\n- collapse it to a `SourceSpan` representing its starting or ending position\n- slice out some characters, optionally skipping some characters at the beginning or end\n- create a new `SourceSpan` with a different starting or ending offset\n\nAll SourceSpan objects implement `SourceLocation`, for compatibility. All SourceSpan\nobjects have a `toJSON` that emits `SourceLocation`, also for compatibility.\n\nFor compatibility, subclasses of `AbstractSourceSpan` must implement `locDidUpdate`, which\nhappens when an AST plugin attempts to modify the `start` or `end` of a span directly.\n\nThe goal is to avoid creating any problems for use-cases like AST Explorer.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/lib/keywords.ts",
-      "line": 20,
-      "description": "This includes the full list of keywords currently in use in the template\nlanguage, and where their valid usages are.",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 170,
+      "description": "Get the starting `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/index.ts",
-      "line": 41,
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 177,
+      "description": "Get the ending `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/syntax/index.ts",
-      "line": 44,
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 184,
+      "description": "Support converting ASTv1 nodes into a serialized format using JSON.stringify.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/component"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/tracking/index.ts",
-      "line": 17,
-      "description": "Marks a property as tracked. By default, values that are rendered in Ember app\ntemplates are _static_, meaning that updates to them won't cause the\napplication to rerender. Marking a property as tracked means that when that\nproperty changes, any templates that used that property, directly or\nindirectly, will rerender. For instance, consider this component:\n\n```gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { action } from '@ember/object';\n\nexport default class CounterComponent extends Component {\n  @tracked count = 0;\n\n  get timesTen() {\n    return this.count * 10;\n  }\n\n  @action\n  plusOne() {\n    this.count += 1;\n  }\n  \n  <template>\n    <div>Count: {{this.count}}</div>\n    <div>Times Ten: {{this.timesTen}}</div>\n    <div>\n      <button {{on \"click\" this.plusOne}}>\n        Plus One\n      </button>\n    </div>\n  </template>\n}\n```\n\nBoth the `{{this.count}}` and the `{{this.timesTen}}` properties in the\ntemplate will update whenever the button is clicked. Any tracked properties\nthat are used in any way to calculate a value that is used in the template\nwill cause a rerender when updated - this includes through method calls and\nother means:\n\n```gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nclass Entry {\n  @tracked name;\n  @tracked phoneNumber;\n\n  constructor(name, phoneNumber) {\n    this.name = name;\n    this.phoneNumber = phoneNumber;\n  }\n}\n\nexport default class PhoneBookComponent extends Component {\n  entries = [\n    new Entry('Pizza Palace', 5551234),\n    new Entry('1st Street Cleaners', 5554321),\n    new Entry('Plants R Us', 5552468),\n  ];\n\n  // Any usage of this property will update whenever any of the names in the\n  // entries arrays are updated\n  get names() {\n    return this.entries.map(e => e.name);\n  }\n\n  // Any usage of this property will update whenever any of the numbers in the\n  // entries arrays are updated\n  get numbers() {\n    return this.getFormattedNumbers();\n  }\n\n  getFormattedNumbers() {\n    return this.entries\n      .map(e => e.phoneNumber)\n      .map(number => {\n        let numberString = '' + number;\n\n        return numberString.slice(0, 3) + '-' + numberString.slice(3);\n      });\n  }\n}\n```\n\nIt's important to note that setting tracked properties will always trigger an\nupdate, even if the property is set to the same value as it was before.\n\n```js\nlet entry = new Entry('Pizza Palace', 5551234);\n// if entry was used when rendering, this would cause a rerender, even though\n// the name is being set to the same value as it was before\nentry.name = entry.name;\n```\n\n`tracked` can also be used with the classic Ember object model in a similar\nmanner to classic computed properties:\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked(),\n  phoneNumber: tracked()\n});\n```\n\nOften this is unnecessary, but to ensure robust auto-tracking behavior it is\nadvisable to mark tracked state appropriately wherever possible.\nThis form of `tracked` also accepts an optional configuration object\ncontaining either an initial `value` or an `initializer` function (but not\nboth).\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked({ value: 'Zoey' }),\n  favoriteSongs: tracked({\n    initializer: () => ['Raspberry Beret', 'Time After Time']\n  })\n});\n```",
-      "itemtype": "method",
-      "name": "tracked",
-      "static": 1,
-      "access": "public",
-      "tagname": "",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 191,
+      "description": "Create a new span with the current span's end and a new beginning.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/tracking"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/tracking/index.ts",
-      "line": 151,
-      "description": "The `@cached` decorator can be used on getters in order to cache the return\nvalue of the getter. This is useful when a getter is expensive and used very\noften. For instance, in this guest list class, we have the `sortedGuests`\ngetter that sorts the guests alphabetically:\n\n```js\nimport { tracked } from '@glimmer/tracking';\n\nclass GuestList {\n  @tracked guests = ['Zoey', 'Tomster'];\n\n  get sortedGuests() {\n    return this.guests.slice().sort()\n  }\n}\n```\n\nEvery time `sortedGuests` is accessed, a new array will be created and sorted,\nbecause JavaScript getters do not cache by default. When the guest list is\nsmall, like the one in the example, this is not a problem. However, if the guest\nlist were to grow very large, it would mean that we would be doing a large\namount of work each time we accessed `sortedGetters`. With `@cached`, we can\ncache the value instead:\n\n```js\nimport { tracked, cached } from '@glimmer/tracking';\n\nclass GuestList {\n  @tracked guests = ['Zoey', 'Tomster'];\n\n  @cached\n  get sortedGuests() {\n    return this.guests.slice().sort()\n  }\n}\n```\n\nNow the `sortedGuests` getter will be cached based on _autotracking_. It will\nonly rerun and create a new sorted array when the `guests` tracked property is\nupdated.\n\nIn general, you should avoid using `@cached` unless you have confirmed that the\ngetter you are decorating is computationally expensive. `@cached` adds a small\namount of overhead to the getter, making it more expensive. While this overhead\nis small, if `@cached` is overused it can add up to a large impact overall in\nyour app. Many getters and tracked properties are only accessed once, rendered,\nand then never rerendered, so adding `@cached` when it is unnecessary can\nnegatively impact performance.",
-      "itemtype": "method",
-      "name": "cached",
-      "static": 1,
-      "access": "public",
-      "tagname": "",
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 198,
+      "description": "Create a new span with the current span's beginning and a new ending.",
       "class": "@glimmer/tracking",
-      "module": "@glimmer/tracking"
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/util/lib/array-utils.ts",
-      "line": 10,
-      "description": "This function returns `true` if the input array is the special empty array sentinel,\nwhich is sometimes used for optimizations.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 209,
+      "description": "Convert this `SourceSpan` into a `SourceSlice`.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/util/lib/array-utils.ts",
-      "line": 36,
-      "description": "Zip two tuples with the same type and number of elements.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 227,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use startPosition instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/util/lib/intern.ts",
-      "line": 1,
-      "description": "Strongly 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™",
-      "access": "private",
-      "tagname": "",
-      "return": {
-        "description": "interned version of the provided string",
-        "type": "String"
-      },
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 236,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use withStart instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/util/lib/local-logger.ts",
-      "line": 1,
-      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\n\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 245,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use endPosition instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/util/lib/local-logger.ts",
-      "line": 11,
-      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 254,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use withEnd instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/array.ts",
-      "line": 66,
-      "description": "Flag to track whether we have *just* intercepted a call to `.push()` or\n`.unshift()`, since in those cases (and only those cases!) the `Array`\nitself checks `.length` to return from the function call.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/loc/span.ts",
+      "line": 263,
+      "description": "For compatibility with SourceLocation in AST plugins",
+      "deprecated": true,
+      "deprecationMessage": "use module instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/object.ts",
-      "line": 34,
-      "description": "This implementation of trackedObject is far too dynamic for TS to be happy with",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/location.ts",
+      "line": 12,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/object.ts",
-      "line": 118,
-      "description": "SAFETY: we are trying to mimic the same behavior as a plain object, so if anything about\n        the object that is returned behaves differently from a native object in a surprising\n        way, we should fix that and make the behavior match native objects.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/location.ts",
+      "line": 14,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/weak-map.ts",
+      "file": "packages/@glimmer/syntax/lib/source/location.ts",
+      "line": 29,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/source/source.ts",
       "line": 16,
-      "description": "SAFETY: note that when passing in an existing weak map, we can't\n        clone it as it is not iterable and not a supported type of structuredClone",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
-      "line": 10,
-      "description": "NOTE: we cannot pass a WeakSet because WeakSets are not iterable",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/source.ts",
+      "line": 27,
+      "description": "Validate that the character offset represents a position in the source string.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
-      "line": 13,
-      "description": "Creates an instanceof WeakSet from an optional list of entries",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/source/source.ts",
+      "line": 92,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
-      "line": 48,
-      "description": "In a WeakSet, there is no `.get()`, but if there was,\nwe could assume it's the same value as what we passed.\n\nSo for a WeakSet, if we try to add something that already exists\nwe no-op.\n\nWeakSet already does this internally for us,\nbut we want the ability for the reactive behavior to reflect the same behavior.\n\ni.e.: doing weakSet.add(value) should never dirty with the defaults\n      if the `value` is already in the weakSet",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "file": "packages/@glimmer/syntax/lib/traversal/visitor.ts",
+      "line": 20,
+      "deprecated": true,
+      "deprecationMessage": "use Template or Block instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/traversal/visitor.ts",
+      "line": 39,
+      "deprecated": true,
+      "deprecationMessage": "use Template or Block instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/handlebars-ast.ts",
+      "line": 1,
+      "description": "This file contains types for the raw AST returned from the Handlebars parser.\nThese types were originally imported from\nhttps://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/handlebars/index.d.ts.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/handlebars-ast.ts",
+      "line": 32,
+      "description": "`loc` is sometimes missing in the upstream Handlebars parser. This is a bug that should be\nfixed. In addition, we should use the types from the upstream parser rather than our own types,\nand if they're not accurate, we should fix them upstream.",
+      "see": [
+        "{https://github.com/handlebars-lang/handlebars-parser/blob/master/types/ast.d.ts}"
+      ],
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 22,
+      "description": "string accessor for params.name",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 35,
+      "deprecated": true,
+      "deprecationMessage": "use Template or Block instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 63,
+      "deprecated": true,
+      "deprecationMessage": "use trusting instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 111,
+      "description": "span for the open tag",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 116,
+      "description": "span for the close tag, null for void or self-closing tags",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 121,
+      "description": "string accessor for path.original",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 126,
+      "description": "string accessor for params.name",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 179,
+      "description": "alias for name",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 190,
+      "description": "alias for name",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 209,
+      "deprecated": true,
+      "deprecationMessage": "use `head` and `tail` instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 213,
+      "deprecated": true,
+      "deprecationMessage": "use `head.type` instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 217,
+      "deprecated": true,
+      "deprecationMessage": "use `head.type' instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 234,
+      "deprecated": true,
+      "deprecationMessage": "use value instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 244,
+      "deprecated": true,
+      "deprecationMessage": "use value instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 254,
+      "deprecated": true,
+      "deprecationMessage": "use value instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 264,
+      "deprecated": true,
+      "deprecationMessage": "use value instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/nodes-v1.ts",
+      "line": 274,
+      "deprecated": true,
+      "deprecationMessage": "use value instead",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v1/parser-builders.ts",
+      "line": 14,
+      "description": "The Parser Builder differentiates from the public builder API by:\n\n1. Offering fewer different ways to instantiate nodes\n2. Mandating source locations",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
+      "line": 7,
+      "description": "Corresponds to syntaxes with positional and named arguments:\n\n- SubExpression\n- Invoking Append\n- Invoking attributes\n- InvokeBlock\n\nIf `Args` is empty, the `SourceOffsets` for this node should be the collapsed position\nimmediately after the parent call node's `callee`.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
+      "line": 51,
+      "description": "Corresponds to positional arguments.\n\nIf `PositionalArguments` is empty, the `SourceOffsets` for this node should be the collapsed\nposition immediately after the parent call node's `callee`.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
+      "line": 80,
+      "description": "Corresponds to named arguments.\n\nIf `PositionalArguments` and `NamedArguments` are empty, the `SourceOffsets` for this node should\nbe the same as the `Args` node that contains this node.\n\nIf `PositionalArguments` is not empty but `NamedArguments` is empty, the `SourceOffsets` for this\nnode should be the collapsed position immediately after the last positional argument.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/args.ts",
+      "line": 114,
+      "description": "Corresponds to a single named argument.\n\n```hbs\nx=<expr>\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 8,
+      "description": "Attr nodes look like HTML attributes, but are classified as:\n\n1. `HtmlAttr`, which means a regular HTML attribute in Glimmer\n2. `SplatAttr`, which means `...attributes`\n3. `ComponentArg`, which means an attribute whose name begins with `@`, and it is therefore a\n   component argument.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 18,
+      "description": "`HtmlAttr` and `SplatAttr` are grouped together because the order of the `SplatAttr` node,\nrelative to other attributes, matters.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 24,
+      "description": "\"Attr Block\" nodes are allowed inside an open element tag in templates. They interact with the\nelement (or component).",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 30,
+      "description": "`HtmlAttr` nodes are valid HTML attributes, with or without a value.\n\nExceptions:\n\n- `...attributes` is `SplatAttr`\n- `@x=<value>` is `ComponentArg`",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 42,
+      "description": "Corresponds to an argument passed by a component (`@x=<value>`)",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 46,
+      "description": "Convert the component argument into a named argument node",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/attr-block.ts",
+      "line": 57,
+      "description": "An `ElementModifier` is just a normal call node in modifier position.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
+      "line": 13,
+      "description": "Content Nodes are allowed in content positions in templates. They correspond to behavior in the\n[Data][data] tokenization state in HTML.\n\n[data]: https://html.spec.whatwg.org/multipage/parsing.html#data-state",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
+      "line": 66,
+      "description": "Corresponds to a component invocation. When the content of a component invocation contains no\nnamed blocks, `blocks` contains a single named block named `\"default\"`. When a component\ninvocation is self-closing, `blocks` is empty.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/content.ts",
+      "line": 92,
+      "description": "Corresponds to a simple HTML element. The AST allows component arguments and modifiers to support\nfuture extensions.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 9,
+      "description": "A Handlebars literal.\n\n{@link https://handlebarsjs.com/guide/expressions.html#literal-segments}",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 24,
+      "description": "Corresponds to a Handlebars literal.",
+      "see": [
+        "{LiteralValue}"
+      ],
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 37,
+      "description": "Returns true if an input {@see ExpressionNode} is a literal.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 57,
+      "description": "Corresponds to a path in expression position.\n\n```hbs\nthis\nthis.x\n@x\n@x.y\nx\nx.y\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 74,
+      "description": "Corresponds to a known strict-mode keyword. It behaves similarly to a\nPathExpression with a FreeVarReference, but implies StrictResolution and\nis guaranteed to not have a tail, since `{{outlet.foo}}` would have been\nillegal.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 85,
+      "description": "Corresponds to a parenthesized call expression.\n\n```hbs\n(x)\n(x.y)\n(x y)\n(x.y z)\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/expr.ts",
+      "line": 97,
+      "description": "Corresponds to an interpolation in attribute value position.\n\n```hbs\n<a href=\"{{url}}.html\"\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
+      "line": 11,
+      "description": "Corresponds to an entire template.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
+      "line": 20,
+      "description": "Represents a block. In principle this could be merged with `NamedBlock`, because all cases\ninvolving blocks have at least a notional name.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
+      "line": 28,
+      "description": "Corresponds to a collection of named blocks.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
+      "line": 32,
+      "description": "Get the `NamedBlock` for a given name.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/internal-node.ts",
+      "line": 52,
+      "description": "Corresponds to a single named block. This is used for anonymous named blocks (`default` and\n`else`).",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/node.ts",
+      "line": 10,
+      "description": "This is a convenience function for creating ASTv2 nodes, with an optional name and the node's\noptions.\n\n```ts\nexport class HtmlText extends node('HtmlText').fields<{ chars: string }>() {}\n```\n\nThis creates a new ASTv2 node with the name `'HtmlText'` and one field `chars: string` (in\naddition to a `loc: SourceOffsets` field, which all nodes have).\n\n```ts\nexport class Args extends node().fields<{\n positional: PositionalArguments;\n named: NamedArguments\n}>() {}\n```\n\nThis creates a new un-named ASTv2 node with two fields (`positional: Positional` and `named:\nNamed`, in addition to the generic `loc: SourceOffsets` field).\n\nOnce you create a node using `node`, it is instantiated with all of its fields (including `loc`):\n\n```ts\nnew HtmlText({ loc: offsets, chars: someString });\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
+      "line": 6,
+      "description": "Corresponds to `this` at the head of an expression.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
+      "line": 11,
+      "description": "Corresponds to `@<ident>` at the beginning of an expression.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
+      "line": 16,
+      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is in the current\nblock's scope.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/refs.ts",
+      "line": 26,
+      "description": "Corresponds to `<ident>` at the beginning of an expression, when `<ident>` is *not* in the\ncurrent block's scope.\n\nThe `resolution: FreeVarResolution` field describes how to resolve the free variable.\n\nNote: In strict mode, it must always be a variable that is in a concrete JavaScript scope that\nthe template will be installed into.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 1,
+      "description": "A free variable is resolved according to a resolution rule:\n\n1. Strict resolution\n2. Namespaced resolution",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 15,
+      "description": "Strict resolution is used:\n\n1. in a strict mode template\n2. in an local variable invocation with dot paths",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 40,
+      "description": "A `LooseModeResolution` includes one or more namespaces to resolve the variable in\n\nIn practice, there are a limited number of possible combinations of these degrees of freedom,\nand they are captured by the `Namespaces` union below.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 47,
+      "description": "Namespaced resolution is used in an unambiguous syntax position:\n\n1. `(sexp)` (namespace: `Helper`)\n2. `{{#block}}` (namespace: `Component`)\n3. `<a {{modifier}}>` (namespace: `Modifier`)\n4. `<Component />` (namespace: `Component`)",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 59,
+      "description": "Append resolution is used when the variable should be resolved in both the `component` and\n`helper` namespaces.\n\n```hbs\n{{x}}\n```\n\n```hbs\n{{x y}}\n```\n\n^ In either case, `x` should be resolved in the `component` and `helper` namespaces.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 77,
+      "description": "Trusting append resolution is used when the variable should be resolved only in the\n`helper` namespaces.\n\n```hbs\n{{{x}}}\n```\n\n```hbs\n{{{x y}}}\n```\n\n^ In either case, `x` should be resolved in the `helper` namespace.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/objects/resolution.ts",
+      "line": 128,
+      "description": "A `Namespaced` must be resolved in one or more namespaces.\n\n```hbs\n<X />\n```\n\n^ `X` is resolved in the `component` namespace\n\n```hbs\n(x)\n```\n\n^ `x` is resolved in the `helper` namespace\n\n```hbs\n<a {{x}} />\n```\n\n^ `x` is resolved in the `modifier` namespace",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
+      "line": 49,
+      "description": "This corresponds to attribute curlies (<Foo bar={{...}}>).\nIn strict mode, this also corresponds to arg curlies.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
+      "line": 63,
+      "description": "This corresponds to append positions text curlies.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/loose-resolution.ts",
+      "line": 85,
+      "description": "A call node has a simple callee if its head is:\n\n- a `PathExpression`\n- the `PathExpression`'s head is a `VarHead`\n- it has no tail\n\nSimple heads:\n\n```\n{{x}}\n{{x y}}\n```\n\nNot simple heads:\n\n```\n{{x.y}}\n{{x.y z}}\n{{@x}}\n{{@x a}}\n{{this}}\n{{this a}}\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 68,
+      "description": "A `BlockContext` represents the block that a particular AST node is contained inside of.\n\n`BlockContext` is aware of template-wide options (such as strict mode), as well as the bindings\nthat are in-scope within that block.\n\nConcretely, it has the `PrecompileOptions` and current `SymbolTable`, and provides\nfacilities for working with those options.\n\n`BlockContext` is stateless.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 162,
+      "description": "An `ExpressionNormalizer` normalizes expressions within a block.\n\n`ExpressionNormalizer` is stateless.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 170,
+      "description": "The `normalize` method takes an arbitrary expression and its original syntax context and\nnormalizes it to an ASTv2 expression.",
+      "see": [
+        "{SyntaxContext}"
+      ],
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 258,
+      "description": "The `callParts` method takes ASTv1.CallParts as well as a syntax context and normalizes\nit to an ASTv2 CallParts.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 307,
+      "description": "The `ref` method normalizes an `ASTv1.PathHead` into an `ASTv2.VariableReference`.\nThis method is extremely important, because it is responsible for normalizing free\nvariables into an an ASTv2.PathHead *with appropriate context*.\n\nThe syntax context is originally determined by the syntactic position that this `PathHead`\ncame from, and is ultimately attached to the `ASTv2.VariableReference` here. In ASTv2,\nthe `VariableReference` node bears full responsibility for loose mode rules that control\nthe behavior of free variables.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 354,
+      "description": "`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 443,
+      "description": "Normalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 491,
+      "description": "Normalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 545,
+      "description": "Normalizes an ASTv1.ElementNode to:\n\n- ASTv2.NamedBlock if the tag name begins with `:`\n- ASTv2.Component if the tag name matches the component heuristics\n- ASTv2.SimpleElement if the tag name doesn't match the component heuristics\n\nA tag name represents a component if:\n\n- it begins with `@`\n- it is exactly `this` or begins with `this.`\n- the part before the first `.` is a reference to an in-scope variable binding\n- it begins with an uppercase character",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 630,
+      "description": "This method handles attribute values that are curlies, as well as curlies nested inside of\ninterpolations:\n\n```hbs\n<a href={{url}} />\n<a href=\"{{url}}.html\" />\n```",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 673,
+      "description": "attrPart is the narrowed down list of valid attribute values that are also\nallowed as a concat part (you can't nest concats).",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
+      "line": 781,
+      "description": "This function classifies the head of an ASTv1.Element into an ASTv2.PathHead (if the\nelement is a component) or `'ElementHead'` (if the element is a simple element).\n\nRules:\n\n1. If the variable is an `@arg`, return an `AtHead`\n2. If the variable is `this`, return a `ThisHead`\n3. If the variable is in the current scope:\n  a. If the scope is the root scope, then return a Free `LocalVarHead`\n  b. Else, return a standard `LocalVarHead`\n4. If the tag name is a path and the variable is not in the current scope, Syntax Error\n5. If the variable is uppercase return a FreeVar(ResolveAsComponentHead)\n6. Otherwise, return `'ElementHead'`",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
+      "line": 12,
+      "description": "Gets the correct Token from the Node based on it's type",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
+      "line": 65,
+      "description": "Adds tokens to the tokensSet based on their node.type",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/get-template-locals.ts",
+      "line": 84,
+      "description": "Parses and traverses a given template to extract all template locals\nreferenced that could possible come from the parent scope. Can exclude known keywords\noptionally.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/keywords.ts",
+      "line": 20,
+      "description": "This includes the full list of keywords currently in use in the template\nlanguage, and where their valid usages are.",
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/index.ts",
+      "line": 41,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/syntax/index.ts",
+      "line": 44,
+      "class": "@glimmer/tracking",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@glimmer/tracking/index.ts",
+      "line": 17,
+      "description": "Marks a property as tracked. By default, values that are rendered in Ember app\ntemplates are _static_, meaning that updates to them won't cause the\napplication to rerender. Marking a property as tracked means that when that\nproperty changes, any templates that used that property, directly or\nindirectly, will rerender. For instance, consider this component:\n\n```gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\nimport { action } from '@ember/object';\n\nexport default class CounterComponent extends Component {\n  @tracked count = 0;\n\n  get timesTen() {\n    return this.count * 10;\n  }\n\n  @action\n  plusOne() {\n    this.count += 1;\n  }\n  \n  <template>\n    <div>Count: {{this.count}}</div>\n    <div>Times Ten: {{this.timesTen}}</div>\n    <div>\n      <button {{on \"click\" this.plusOne}}>\n        Plus One\n      </button>\n    </div>\n  </template>\n}\n```\n\nBoth the `{{this.count}}` and the `{{this.timesTen}}` properties in the\ntemplate will update whenever the button is clicked. Any tracked properties\nthat are used in any way to calculate a value that is used in the template\nwill cause a rerender when updated - this includes through method calls and\nother means:\n\n```gjs\nimport Component from '@glimmer/component';\nimport { tracked } from '@glimmer/tracking';\n\nclass Entry {\n  @tracked name;\n  @tracked phoneNumber;\n\n  constructor(name, phoneNumber) {\n    this.name = name;\n    this.phoneNumber = phoneNumber;\n  }\n}\n\nexport default class PhoneBookComponent extends Component {\n  entries = [\n    new Entry('Pizza Palace', 5551234),\n    new Entry('1st Street Cleaners', 5554321),\n    new Entry('Plants R Us', 5552468),\n  ];\n\n  // Any usage of this property will update whenever any of the names in the\n  // entries arrays are updated\n  get names() {\n    return this.entries.map(e => e.name);\n  }\n\n  // Any usage of this property will update whenever any of the numbers in the\n  // entries arrays are updated\n  get numbers() {\n    return this.getFormattedNumbers();\n  }\n\n  getFormattedNumbers() {\n    return this.entries\n      .map(e => e.phoneNumber)\n      .map(number => {\n        let numberString = '' + number;\n\n        return numberString.slice(0, 3) + '-' + numberString.slice(3);\n      });\n  }\n}\n```\n\nIt's important to note that setting tracked properties will always trigger an\nupdate, even if the property is set to the same value as it was before.\n\n```js\nlet entry = new Entry('Pizza Palace', 5551234);\n// if entry was used when rendering, this would cause a rerender, even though\n// the name is being set to the same value as it was before\nentry.name = entry.name;\n```\n\n`tracked` can also be used with the classic Ember object model in a similar\nmanner to classic computed properties:\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked(),\n  phoneNumber: tracked()\n});\n```\n\nOften this is unnecessary, but to ensure robust auto-tracking behavior it is\nadvisable to mark tracked state appropriately wherever possible.\nThis form of `tracked` also accepts an optional configuration object\ncontaining either an initial `value` or an `initializer` function (but not\nboth).\n\n```javascript\nimport EmberObject from '@ember/object';\nimport { tracked } from '@glimmer/tracking';\n\nconst Entry = EmberObject.extend({\n  name: tracked({ value: 'Zoey' }),\n  favoriteSongs: tracked({\n    initializer: () => ['Raspberry Beret', 'Time After Time']\n  })\n});\n```",
+      "itemtype": "method",
+      "name": "tracked",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/tracking/index.ts",
+      "line": 151,
+      "description": "The `@cached` decorator can be used on getters in order to cache the return\nvalue of the getter. This is useful when a getter is expensive and used very\noften. For instance, in this guest list class, we have the `sortedGuests`\ngetter that sorts the guests alphabetically:\n\n```js\nimport { tracked } from '@glimmer/tracking';\n\nclass GuestList {\n  @tracked guests = ['Zoey', 'Tomster'];\n\n  get sortedGuests() {\n    return this.guests.slice().sort()\n  }\n}\n```\n\nEvery time `sortedGuests` is accessed, a new array will be created and sorted,\nbecause JavaScript getters do not cache by default. When the guest list is\nsmall, like the one in the example, this is not a problem. However, if the guest\nlist were to grow very large, it would mean that we would be doing a large\namount of work each time we accessed `sortedGetters`. With `@cached`, we can\ncache the value instead:\n\n```js\nimport { tracked, cached } from '@glimmer/tracking';\n\nclass GuestList {\n  @tracked guests = ['Zoey', 'Tomster'];\n\n  @cached\n  get sortedGuests() {\n    return this.guests.slice().sort()\n  }\n}\n```\n\nNow the `sortedGuests` getter will be cached based on _autotracking_. It will\nonly rerun and create a new sorted array when the `guests` tracked property is\nupdated.\n\nIn general, you should avoid using `@cached` unless you have confirmed that the\ngetter you are decorating is computationally expensive. `@cached` adds a small\namount of overhead to the getter, making it more expensive. While this overhead\nis small, if `@cached` is overused it can add up to a large impact overall in\nyour app. Many getters and tracked properties are only accessed once, rendered,\nand then never rerendered, so adding `@cached` when it is unnecessary can\nnegatively impact performance.",
+      "itemtype": "method",
+      "name": "cached",
+      "static": 1,
+      "access": "public",
+      "tagname": "",
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/util/lib/array-utils.ts",
+      "line": 10,
+      "description": "This function returns `true` if the input array is the special empty array sentinel,\nwhich is sometimes used for optimizations.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/util/lib/array-utils.ts",
+      "line": 36,
+      "description": "Zip two tuples with the same type and number of elements.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/util/lib/intern.ts",
+      "line": 1,
+      "description": "Strongly 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™",
+      "access": "private",
+      "tagname": "",
+      "return": {
+        "description": "interned version of the provided string",
+        "type": "String"
+      },
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/util/lib/local-logger.ts",
+      "line": 1,
+      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\n\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/util/lib/local-logger.ts",
+      "line": 11,
+      "description": "This constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/array.ts",
+      "line": 66,
+      "description": "Flag to track whether we have *just* intercepted a call to `.push()` or\n`.unshift()`, since in those cases (and only those cases!) the `Array`\nitself checks `.length` to return from the function call.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/object.ts",
+      "line": 34,
+      "description": "This implementation of trackedObject is far too dynamic for TS to be happy with",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/object.ts",
+      "line": 118,
+      "description": "SAFETY: we are trying to mimic the same behavior as a plain object, so if anything about\n        the object that is returned behaves differently from a native object in a surprising\n        way, we should fix that and make the behavior match native objects.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/weak-map.ts",
+      "line": 16,
+      "description": "SAFETY: note that when passing in an existing weak map, we can't\n        clone it as it is not iterable and not a supported type of structuredClone",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
+      "line": 10,
+      "description": "NOTE: we cannot pass a WeakSet because WeakSets are not iterable",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
+      "line": 13,
+      "description": "Creates an instanceof WeakSet from an optional list of entries",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
+      "line": 48,
+      "description": "In a WeakSet, there is no `.get()`, but if there was,\nwe could assume it's the same value as what we passed.\n\nSo for a WeakSet, if we try to add something that already exists\nwe no-op.\n\nWeakSet already does this internally for us,\nbut we want the ability for the reactive behavior to reflect the same behavior.\n\ni.e.: doing weakSet.add(value) should never dirty with the defaults\n      if the `value` is already in the weakSet",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
+      "line": 62,
+      "description": "This looks a little silly, where a always will === b,\nbut see the note above.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/debug.ts",
+      "line": 104,
+      "description": "Creates a global autotracking transaction. This will prevent any backflow\nin any `track` calls within the transaction, even if they are not\nexternally consumed.\n\n`runInAutotrackingTransaction` can be called within itself, and it will add\nonto the existing transaction if one exists.\n\nTODO: Only throw an error if the `track` is consumed.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/tracking.ts",
+      "line": 10,
+      "description": "An object that that tracks @tracked properties that were consumed.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/tracking.ts",
+      "line": 42,
+      "description": "Whenever a tracked computed property is entered, the current tracker is\nsaved off and a new tracker is replaced.\n\nAny tracked properties consumed are added to the current tracker.\n\nWhen a tracked computed property is exited, the tracker's tags are\ncombined and added to the parent tracker.\n\nThe consequence is that each tracked computed property has a tag\nthat corresponds to the tracked properties consumed inside of\nitself, including child tracked computed properties.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/validators.ts",
+      "line": 50,
+      "description": "`value` receives a tag and returns an opaque Revision based on that tag. This\nsnapshot can then later be passed to `validate` with the same tag to\ndetermine if the tag has changed at all since the time that `value` was\ncalled.",
+      "params": [
+        {
+          "name": "tag",
+          "description": ""
+        }
+      ],
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/validator/lib/validators.ts",
+      "line": 62,
+      "description": "`validate` receives a tag and a snapshot from a previous call to `value` with\nthe same tag, and determines if the tag is still valid compared to the\nsnapshot. If the tag's state has changed at all since then, `validate` will\nreturn false, otherwise it will return true. This is used to determine if a\ncalculation related to the tags should be rerun.",
+      "params": [
+        {
+          "name": "tag",
+          "description": ""
+        },
+        {
+          "name": "snapshot",
+          "description": ""
+        }
+      ],
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/vm/lib/registers.ts",
+      "line": 1,
+      "description": "Registers\n\nFor the most part, these follows MIPS naming conventions, however the\nregister numbers are different.",
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/@glimmer/vm/index.ts",
+      "line": 5,
+      "class": "TestAdapter",
+      "module": "@glimmer/tracking"
+    },
+    {
+      "file": "packages/ember-testing/lib/adapters/adapter.ts",
+      "line": 20,
+      "description": "This callback will be called whenever an async operation is about to start.\n\nOverride this to call your framework's methods that handle async\noperations.",
+      "access": "public",
+      "tagname": "",
+      "itemtype": "method",
+      "name": "asyncStart",
+      "class": "TestAdapter",
+      "module": "@ember/test"
+    },
+    {
+      "file": "packages/ember-testing/lib/adapters/adapter.ts",
+      "line": 31,
+      "description": "This callback will be called whenever an async operation has completed.",
+      "access": "public",
+      "tagname": "",
+      "itemtype": "method",
+      "name": "asyncEnd",
+      "class": "TestAdapter",
+      "module": "@ember/test"
+    },
+    {
+      "file": "packages/ember-testing/lib/adapters/adapter.ts",
+      "line": 39,
+      "description": "Override this method with your testing framework's false assertion.\nThis function is called whenever an exception occurs causing the testing\npromise to fail.\n\nQUnit example:\n\n```javascript\n  exception: function(error) {\n    ok(false, error);\n  };\n```",
+      "access": "public",
+      "tagname": "",
+      "itemtype": "method",
+      "name": "exception",
+      "params": [
+        {
+          "name": "error",
+          "description": "The exception to be raised.",
+          "type": "String"
+        }
+      ],
+      "class": "TestAdapter",
+      "module": "@ember/test"
+    },
+    {
+      "file": "packages/ember-testing/lib/test/waiters.ts",
+      "line": 7,
+      "description": "This allows ember-testing to play nicely with other asynchronous\nevents, such as an application that is waiting for a CSS3\ntransition or an IndexDB transaction. The waiter runs periodically\nafter each async helper (i.e. `click`, `andThen`, `visit`, etc) has executed,\nuntil the returning result is truthy. After the waiters finish, the next async helper\nis executed and the process repeats.\n\nFor example:\n\n```javascript\nimport { registerWaiter } from '@ember/test';\n\nregisterWaiter(function() {\n  return myPendingTransactions() === 0;\n});\n```\nThe `context` argument allows you to optionally specify the `this`\nwith which your callback will be invoked.\n\nFor example:\n\n```javascript\nimport { registerWaiter } from '@ember/test';\n\nregisterWaiter(MyDB, MyDB.hasPendingTransactions);\n```",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "itemtype": "method",
+      "name": "registerWaiter",
+      "params": [
+        {
+          "name": "context",
+          "description": "(optional)",
+          "type": "Object"
+        },
+        {
+          "name": "callback",
+          "description": "",
+          "type": "Function"
+        }
+      ],
+      "since": "1.2.0",
+      "class": "@ember/test",
+      "module": "@ember/test"
+    },
+    {
+      "file": "packages/ember-testing/lib/test/waiters.ts",
+      "line": 70,
+      "description": "`unregisterWaiter` is used to unregister a callback that was\nregistered with `registerWaiter`.",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "itemtype": "method",
+      "name": "unregisterWaiter",
+      "params": [
+        {
+          "name": "context",
+          "description": "(optional)",
+          "type": "Object"
+        },
+        {
+          "name": "callback",
+          "description": "",
+          "type": "Function"
+        }
+      ],
+      "since": "1.2.0",
+      "class": "@ember/test",
+      "module": "@ember/test"
+    },
+    {
+      "file": "packages/ember-testing/lib/test/waiters.ts",
+      "line": 98,
+      "description": "Iterates through each registered test waiter, and invokes\nits callback. If any waiter returns false, this method will return\ntrue indicating that the waiters have not settled yet.\n\nThis is generally used internally from the acceptance/integration test\ninfrastructure.",
+      "access": "public",
+      "tagname": "",
+      "static": 1,
+      "itemtype": "method",
+      "name": "checkWaiters",
+      "class": "@ember/test",
+      "module": "@ember/test"
+    }
+  ],
+  "warnings": [
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/-internals/container/lib/container.ts:198"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/helpers/each-in.ts:13"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/helpers/each-in.ts:189"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/helpers/readonly.ts:9"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/helpers/unbound.ts:10"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/syntax/mount.ts:17"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/-internals/glimmer/lib/syntax/outlet.ts:32"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/string.ts:47"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/string.ts:58"
+    },
+    {
+      "message": "unknown tag: note",
+      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:325"
+    },
+    {
+      "message": "unknown tag: decorator",
+      "line": " packages/@ember/-internals/metal/lib/cached.ts:7"
+    },
+    {
+      "message": "unknown tag: decorator",
+      "line": " packages/@ember/-internals/metal/lib/tracked.ts:14"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@ember/-internals/owner/index.ts:730"
+    },
+    {
+      "message": "replacing incorrect tag: function with method",
+      "line": " packages/@ember/-internals/utils/lib/spec.ts:1"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/component/index.ts:40"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/destroyable/index.ts:31"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/destroyable/index.ts:58"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/destroyable/index.ts:80"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/helper/index.ts:276"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:349"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:386"
+    },
+    {
+      "message": "unknown tag: exampleimport",
+      "line": " packages/@ember/helper/index.ts:414"
+    },
+    {
+      "message": "unknown tag: exampleimport",
+      "line": " packages/@ember/helper/index.ts:445"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:493"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:562"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:587"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:612"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:637"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:662"
+    },
+    {
+      "message": "unknown tag: exampleimport",
+      "line": " packages/@ember/helper/index.ts:690"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:718"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:743"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:768"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:793"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:819"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:844"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1109"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1150"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1193"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1238"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1328"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1368"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1484"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1596"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1674"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@ember/helper/index.ts:1714"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@ember/object/mixin.ts:605"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@ember/object/mixin.ts:628"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@ember/object/mixin.ts:649"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:8"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:51"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:94"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:138"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:179"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/reactive/collections.ts:223"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/renderer/index.ts:11"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/routing/route-info.ts:91"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/routing/route.ts:2095"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@ember/runloop/index.ts:88"
+    },
+    {
+      "message": "replacing incorrect tag: returns with return",
+      "line": " packages/@ember/template-compiler/lib/template.ts:256"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:10"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:62"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:74"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/index.js:32"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/index.js:49"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/dist/index.js:66"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/src/-private/component.ts:36"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/src/-private/component.ts:79"
+    },
+    {
+      "message": "unknown tag: internal",
+      "line": " packages/@glimmer/component/src/-private/component.ts:97"
+    },
+    {
+      "message": "unknown tag: import",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:21"
+    },
+    {
+      "message": "unknown tag: glimmer",
+      "line": " packages/@glimmer/global-context/index.ts:21"
+    },
+    {
+      "message": "unknown tag: debugging",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:42"
+    },
+    {
+      "message": "unknown tag: glimmer",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:1"
+    },
+    {
+      "message": "unknown tag: noimport",
+      "line": " packages/@glimmer/runtime/lib/modifiers/on.ts:253"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:171"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:184"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
+    },
+    {
+      "message": "unknown tag: utility",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
+    },
+    {
+      "message": "unknown tag: debug",
+      "line": " packages/@glimmer/runtime/lib/scope.ts:86"
+    },
+    {
+      "message": "Missing item type\nThis \"upgrades\" a route template into a invocable component. Conceptually\nit can be 1:1 for each unique `Template`, but it's also cheap to construct,\nso unless the stability is desirable for other reasons, it's probably not\nworth caching this.",
+      "line": " packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts:113"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/component-managers/unwrap-template.ts:3"
+    },
+    {
+      "message": "Missing item type\nThe `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
+      "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:132"
+    },
+    {
+      "message": "Missing item type\nThe HTML class attribute.",
+      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:151"
+    },
+    {
+      "message": "Missing item type\nThe HTML type attribute.",
+      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:162"
+    },
+    {
+      "message": "Missing item type\nThe default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:40"
+    },
+    {
+      "message": "Missing item type\nThe default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
+      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:53"
+    },
+    {
+      "message": "Missing item type\nThis reference is used to get the `[]` tag of iterables, so we can trigger\nupdates to `{{each}}` when it changes. It is put into place by a template\ntransform at build time, similar to the (-each-in) helper",
+      "line": " packages/@ember/-internals/glimmer/lib/helpers/-track-array.ts:12"
+    },
+    {
+      "message": "Missing item type\nThis is usually inherited from the parent (all the way up to the app\ninstance). However, engines uses this to swap out the owner when crossing\na mount point.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:5"
+    },
+    {
+      "message": "Missing item type\nThe name of the route/template",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:12"
+    },
+    {
+      "message": "Missing item type\nThe controller (the self of the outlet component)",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:17"
+    },
+    {
+      "message": "Missing item type\nThe model (the resolved value of the model hook)",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:22"
+    },
+    {
+      "message": "Missing item type\nThe route's template – this is either a Template or a component, and it\ngets normalized during the render process.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:27"
+    },
+    {
+      "message": "Missing item type\nRepresents what was rendered into this outlet.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:35"
+    },
+    {
+      "message": "Missing item type\nRepresents what, if any, should be rendered into the next {{outlet}} found\nat this level.\n\nThis used to be a dictionary of children outlets, including the {{outlet}}\n\"main\" outlet any {{outlet \"named\"}} named outlets. Since named outlets\nare not a thing anymore, this can now just be a single`child`.",
+      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:40"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:114"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:122"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:135"
+    },
+    {
+      "message": "Missing item type\nThe type of a function-based helper.",
+      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:325"
+    },
+    {
+      "message": "Missing item type\nDestroys the render tree and removes all rendered content from the element rendered into",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:546"
+    },
+    {
+      "message": "Missing item type\nThe GlimmerRenderResult from the last render. Used to get positional\ninformation (firstNode) when a re-render replaces the content, so\nthat the new content is placed at the same DOM position.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:554"
+    },
+    {
+      "message": "Missing item type\nThe component definition to render.\n\nAny component that has had its manager registered is valid.\nFor the component-types that ship with ember, manager registration\ndoes not need to be worried about.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:585"
+    },
+    {
+      "message": "Missing item type\nThe element to render the component in to.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:599"
+    },
+    {
+      "message": "Missing item type\nOptional owner. Defaults to `{}`, can be any object, but will need to implement the [Owner](https://api.emberjs.com/ember/release/classes/Owner) API for components within this render tree to access services.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:604"
+    },
+    {
+      "message": "Missing item type\nOptionally configure the rendering environment",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:608"
+    },
+    {
+      "message": "Missing item type\nWhen false, modifiers will not run.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:612"
+    },
+    {
+      "message": "Missing item type\nAll other options are forwarded to the underlying renderer.\n(its API is currently private and out of scope for this RFC,\n so passing additional things here is also considered private API)",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:616"
+    },
+    {
+      "message": "Missing item type\nThese args get passed to the rendered component\n\nIf your args are reactive, re-rendering will happen automatically.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:624"
+    },
+    {
+      "message": "Missing item type\nSAFETY: we should figure out what we need out of a `document` and narrow the API.\n        this exercise should also end up beginning to define what we need for CLI rendering (or to other outputs)",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:633"
+    },
+    {
+      "message": "Missing item type\nReplace all contents, if we've rendered multiple times.\n\nhttps://github.com/emberjs/rfcs/pull/1099/files#diff-2b962105b9083ca84579cdc957f27f49407440f3c5078083fa369ec18cc46da8R365\n\nWe could later add an option to not do this behavior\n\nNOTE: destruction is async",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:654"
+    },
+    {
+      "message": "Missing item type\nWe can only replace the inner HTML the first time.\nBecause destruction is async, it won't be safe to\ndo this again, and we'll have to rely on the above destroy.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:665"
+    },
+    {
+      "message": "Missing item type\nIf there's an existing render result with valid bounds, use its\nfirstNode as the nextSibling so that new content is inserted at\nthe same DOM position. This ensures stable ordering when multiple\nrenderComponent calls target the same element and one is re-invoked\n(e.g., due to tracked dependency changes).\n\nThe old content's DOM nodes are still present (destruction is async),\nso firstNode() is a valid position reference. The new content is placed\nBEFORE the old content. When the old content is eventually destroyed\n(async clear of bounds), the new content remains in the correct position.",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:674"
+    },
+    {
+      "message": "Missing item type\nSAFETY: are there consequences for being looser with *this* owner?\n        the public API for `owner` is kinda `Partial<InternalOwner>`\n        aka: implement only what you need.\n        But for actual ember apps, you *need* to implement everything\n        an app needs (which will actually change and become less over time)",
+      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:742"
+    },
+    {
+      "message": "Missing item type\nTest skipped because when an error occurs,\nwe mess up the cache used by renderComponent.",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:445"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:560"
+    },
+    {
+      "message": "Missing item type\nNOTE: subsequent renders to the same element are prepended to the element's children",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:759"
+    },
+    {
+      "message": "Missing item type\nERROR in conflict with the NOTE on this test.\nthe elementns flip locations... which is kinda bonkers",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:828"
+    },
+    {
+      "message": "Missing item type\nWe need to pass a scope so that we get a strict-mode component.",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:925"
+    },
+    {
+      "message": "Missing item type\nThis function is used to hide a variable from the transpiler, so that it\ndoesn't get removed as \"unused\". It does not actually do anything with the\nvariable, it just makes it be part of an expression that the transpiler\nwon't remove.\n\nIt's a bit of a hack, but it's necessary for testing.",
+      "line": " packages/@ember/-internals/glimmer/tests/integration/components/runtime-template-compiler-implicit-test.ts:494"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:91"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:93"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:95"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:97"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:99"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:101"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:103"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:105"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:107"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:110"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:112"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:114"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:116"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:120"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:143"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:157"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:162"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:167"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:172"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:177"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:182"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:197"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:210"
     },
     {
-      "file": "packages/@glimmer/validator/lib/collections/weak-set.ts",
-      "line": 62,
-      "description": "This looks a little silly, where a always will === b,\nbut see the note above.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:217"
     },
     {
-      "file": "packages/@glimmer/validator/lib/debug.ts",
-      "line": 104,
-      "description": "Creates a global autotracking transaction. This will prevent any backflow\nin any `track` calls within the transaction, even if they are not\nexternally consumed.\n\n`runInAutotrackingTransaction` can be called within itself, and it will add\nonto the existing transaction if one exists.\n\nTODO: Only throw an error if the `track` is consumed.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:224"
     },
     {
-      "file": "packages/@glimmer/validator/lib/tracking.ts",
-      "line": 10,
-      "description": "An object that that tracks @tracked properties that were consumed.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:231"
     },
     {
-      "file": "packages/@glimmer/validator/lib/tracking.ts",
-      "line": 42,
-      "description": "Whenever a tracked computed property is entered, the current tracker is\nsaved off and a new tracker is replaced.\n\nAny tracked properties consumed are added to the current tracker.\n\nWhen a tracked computed property is exited, the tracker's tags are\ncombined and added to the parent tracker.\n\nThe consequence is that each tracked computed property has a tag\nthat corresponds to the tracked properties consumed inside of\nitself, including child tracked computed properties.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:238"
     },
     {
-      "file": "packages/@glimmer/validator/lib/validators.ts",
-      "line": 50,
-      "description": "`value` receives a tag and returns an opaque Revision based on that tag. This\nsnapshot can then later be passed to `validate` with the same tag to\ndetermine if the tag has changed at all since the time that `value` was\ncalled.",
-      "params": [
-        {
-          "name": "tag",
-          "description": ""
-        }
-      ],
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:255"
     },
     {
-      "file": "packages/@glimmer/validator/lib/validators.ts",
-      "line": 62,
-      "description": "`validate` receives a tag and a snapshot from a previous call to `value` with\nthe same tag, and determines if the tag is still valid compared to the\nsnapshot. If the tag's state has changed at all since then, `validate` will\nreturn false, otherwise it will return true. This is used to determine if a\ncalculation related to the tags should be rerun.",
-      "params": [
-        {
-          "name": "tag",
-          "description": ""
-        },
-        {
-          "name": "snapshot",
-          "description": ""
-        }
-      ],
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:270"
     },
     {
-      "file": "packages/@glimmer/vm/lib/registers.ts",
-      "line": 1,
-      "description": "Registers\n\nFor the most part, these follows MIPS naming conventions, however the\nregister numbers are different.",
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:284"
     },
     {
-      "file": "packages/@glimmer/vm/index.ts",
-      "line": 5,
-      "class": "TestAdapter",
-      "module": "@glimmer/tracking"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:289"
     },
     {
-      "file": "packages/ember-testing/lib/adapters/adapter.ts",
-      "line": 20,
-      "description": "This callback will be called whenever an async operation is about to start.\n\nOverride this to call your framework's methods that handle async\noperations.",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "asyncStart",
-      "class": "TestAdapter",
-      "module": "@ember/test"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:309"
     },
     {
-      "file": "packages/ember-testing/lib/adapters/adapter.ts",
-      "line": 31,
-      "description": "This callback will be called whenever an async operation has completed.",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "asyncEnd",
-      "class": "TestAdapter",
-      "module": "@ember/test"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:323"
     },
     {
-      "file": "packages/ember-testing/lib/adapters/adapter.ts",
-      "line": 39,
-      "description": "Override this method with your testing framework's false assertion.\nThis function is called whenever an exception occurs causing the testing\npromise to fail.\n\nQUnit example:\n\n```javascript\n  exception: function(error) {\n    ok(false, error);\n  };\n```",
-      "access": "public",
-      "tagname": "",
-      "itemtype": "method",
-      "name": "exception",
-      "params": [
-        {
-          "name": "error",
-          "description": "The exception to be raised.",
-          "type": "String"
-        }
-      ],
-      "class": "TestAdapter",
-      "module": "@ember/test"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:329"
     },
     {
-      "file": "packages/ember-testing/lib/test/waiters.ts",
-      "line": 7,
-      "description": "This allows ember-testing to play nicely with other asynchronous\nevents, such as an application that is waiting for a CSS3\ntransition or an IndexDB transaction. The waiter runs periodically\nafter each async helper (i.e. `click`, `andThen`, `visit`, etc) has executed,\nuntil the returning result is truthy. After the waiters finish, the next async helper\nis executed and the process repeats.\n\nFor example:\n\n```javascript\nimport { registerWaiter } from '@ember/test';\n\nregisterWaiter(function() {\n  return myPendingTransactions() === 0;\n});\n```\nThe `context` argument allows you to optionally specify the `this`\nwith which your callback will be invoked.\n\nFor example:\n\n```javascript\nimport { registerWaiter } from '@ember/test';\n\nregisterWaiter(MyDB, MyDB.hasPendingTransactions);\n```",
-      "access": "public",
-      "tagname": "",
-      "static": 1,
-      "itemtype": "method",
-      "name": "registerWaiter",
-      "params": [
-        {
-          "name": "context",
-          "description": "(optional)",
-          "type": "Object"
-        },
-        {
-          "name": "callback",
-          "description": "",
-          "type": "Function"
-        }
-      ],
-      "since": "1.2.0",
-      "class": "@ember/test",
-      "module": "@ember/test"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:334"
     },
     {
-      "file": "packages/ember-testing/lib/test/waiters.ts",
-      "line": 70,
-      "description": "`unregisterWaiter` is used to unregister a callback that was\nregistered with `registerWaiter`.",
-      "access": "public",
-      "tagname": "",
-      "static": 1,
-      "itemtype": "method",
-      "name": "unregisterWaiter",
-      "params": [
-        {
-          "name": "context",
-          "description": "(optional)",
-          "type": "Object"
-        },
-        {
-          "name": "callback",
-          "description": "",
-          "type": "Function"
-        }
-      ],
-      "since": "1.2.0",
-      "class": "@ember/test",
-      "module": "@ember/test"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:355"
     },
     {
-      "file": "packages/ember-testing/lib/test/waiters.ts",
-      "line": 98,
-      "description": "Iterates through each registered test waiter, and invokes\nits callback. If any waiter returns false, this method will return\ntrue indicating that the waiters have not settled yet.\n\nThis is generally used internally from the acceptance/integration test\ninfrastructure.",
-      "access": "public",
-      "tagname": "",
-      "static": 1,
-      "itemtype": "method",
-      "name": "checkWaiters",
-      "class": "@ember/test",
-      "module": "@ember/test"
-    }
-  ],
-  "warnings": [
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:370"
+    },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/container/lib/container.ts:198"
+      "message": "Missing item type\nFlattening is based on a global revision counter. If the revision has\nbumped it means that somewhere in a class inheritance chain something has\nchanged, so we need to reflatten everything. This can only happen if:\n\n1. A meta has been flattened (listener has been called)\n2. The meta is a prototype meta with children who have inherited its\n   listeners\n3. A new listener is subsequently added to the meta (e.g. via `.reopen()`)\n\nThis is a very rare occurrence, so while the counter is global it shouldn't\nbe updated very often in practice.",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:477"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/string.ts:47"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:551"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/string.ts:58"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/meta/lib/meta.ts:582"
     },
     {
-      "message": "unknown tag: note",
-      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:325"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/metal/lib/computed.ts:715"
     },
     {
-      "message": "unknown tag: decorator",
-      "line": " packages/@ember/-internals/metal/lib/cached.ts:7"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/metal/lib/computed.ts:721"
     },
     {
-      "message": "unknown tag: decorator",
+      "message": "Missing item type\nPrimarily used for cases where we are redefining a class, e.g. mixins/reopen\nbeing applied later. Revalidates all the observers, resetting their tags.",
+      "line": " packages/@ember/-internals/metal/lib/observer.ts:156"
+    },
+    {
+      "message": "Missing item type",
       "line": " packages/@ember/-internals/metal/lib/tracked.ts:14"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@ember/-internals/owner/index.ts:730"
+      "message": "Missing item type\nA type registry for the DI system, which other participants in the DI system\ncan register themselves into with declaration merging. The contract for this\ntype is that its keys are the `Type` from a `FullName`, and each value for a\n`Type` is another registry whose keys are the `Name` from a `FullName`. The\nmechanic for providing a registry is [declaration merging][handbook].\n\n[handbook]: https://www.typescriptlang.org/docs/handbook/declaration-merging.html\n\nFor example, Ember's `@ember/service` module includes this set of definitions:\n\n```ts\nexport default class Service extends EmberObject {}\n\n// For concrete singleton classes to be merged into.\ninterface Registry extends Record<string, Service> {}\n\ndeclare module '@ember/owner' {\n  service: Registry;\n}\n```\n\nDeclarations of services can then include the registry:\n\n```ts\nimport Service from '@ember/service';\n\nexport default class Session extends Service {\n  login(username: string, password: string) {\n    // ...\n  }\n}\n\ndeclare module '@ember/service' {\n  interface Registry {\n    session: Session;\n  }\n}\n```\n\nThen users of the `Owner` API will be able to do things like this with strong\ntype safety guarantees:\n\n```ts\ngetOwner(this)?.lookup('service:session').login(\"hello\", \"1234abcd\");\n```",
+      "line": " packages/@ember/-internals/owner/index.ts:24"
     },
     {
-      "message": "replacing incorrect tag: function with method",
-      "line": " packages/@ember/-internals/utils/lib/spec.ts:1"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/owner/index.ts:79"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/component/index.ts:40"
+      "message": "Missing item type\nA record mapping all known items of a given type: if the item is known it\nwill be `true`; otherwise it will be `false` or `undefined`.",
+      "line": " packages/@ember/-internals/owner/index.ts:408"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/destroyable/index.ts:31"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/owner/index.ts:730"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/destroyable/index.ts:58"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:21"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/destroyable/index.ts:80"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts:21"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/helper/index.ts:274"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts:31"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:605"
+      "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```",
+      "line": " packages/@ember/-internals/string/index.ts:93"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:628"
+      "message": "Missing item type",
+      "line": " packages/@ember/-internals/utils/lib/guid.ts:8"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@ember/object/mixin.ts:649"
+      "message": "Missing item type\nGenerates a universally unique identifier. This method\nis used internally by Ember for assisting with\nthe generation of GUID's and other unique identifiers.",
+      "line": " packages/@ember/-internals/utils/lib/guid.ts:14"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:8"
+      "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": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:51"
+      "message": "Missing item type",
+      "line": " packages/@ember/application/index.ts:33"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:94"
+      "message": "Missing item type",
+      "line": " packages/@ember/application/index.ts:38"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:138"
+      "message": "Missing item type\nUnfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
+      "line": " packages/@ember/application/index.ts:688"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:179"
+      "message": "Missing item type\nOverrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
+      "line": " packages/@ember/application/instance.ts:81"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/reactive/collections.ts:223"
+      "message": "Missing item type\nThis hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
+      "line": " packages/@ember/application/instance.ts:141"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/renderer/index.ts:11"
+      "message": "Missing item type\nTells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
+      "line": " packages/@ember/application/instance.ts:158"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/routing/route-info.ts:91"
+      "message": "Missing item type\nSets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
+      "line": " packages/@ember/application/instance.ts:169"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/routing/route.ts:2095"
+      "message": "Missing item type\nDirects the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
+      "line": " packages/@ember/application/instance.ts:190"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@ember/runloop/index.ts:88"
+      "message": "Missing item type",
+      "line": " packages/@ember/application/instance.ts:202"
     },
     {
-      "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/template-compiler/lib/template.ts:256"
+      "message": "Missing item type\nReturns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
+      "line": " packages/@ember/application/instance.ts:224"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:36"
+      "message": "Missing item type\nNavigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transition was aborted due to an error.",
+      "line": " packages/@ember/application/instance.ts:239"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:79"
+      "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:1915"
     },
     {
-      "message": "unknown tag: internal",
-      "line": " packages/@glimmer/component/src/-private/component.ts:97"
+      "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:1932"
     },
     {
-      "message": "unknown tag: import",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:21"
+      "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:1956"
     },
     {
-      "message": "unknown tag: glimmer",
-      "line": " packages/@glimmer/global-context/index.ts:21"
+      "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:1961"
     },
     {
-      "message": "unknown tag: debugging",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:42"
+      "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:1966"
     },
     {
-      "message": "unknown tag: glimmer",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:1"
+      "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:1971"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:171"
+      "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:1976"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:184"
+      "message": "Missing item type\nReverse objects in the array. Works just like `reverse()` but it is\nKVO-compliant.",
+      "line": " packages/@ember/array/index.ts:1981"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
+      "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:1986"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
+      "message": "Missing item type\nRemoves each object in the passed array from the receiver.",
+      "line": " packages/@ember/array/index.ts:2008"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
+      "message": "Missing item type\nAdds each object in the passed enumerable to the receiver.",
+      "line": " packages/@ember/array/index.ts:2029"
     },
     {
-      "message": "unknown tag: utility",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:178"
     },
     {
-      "message": "unknown tag: debug",
-      "line": " packages/@glimmer/runtime/lib/scope.ts:86"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:180"
     },
     {
-      "message": "Missing item type\nThis \"upgrades\" a route template into a invocable component. Conceptually\nit can be 1:1 for each unique `Template`, but it's also cheap to construct,\nso unless the stability is desirable for other reasons, it's probably not\nworth caching this.",
-      "line": " packages/@ember/-internals/glimmer/lib/component-managers/route-template.ts:113"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:183"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/component-managers/unwrap-template.ts:3"
+      "line": " packages/@ember/array/proxy.ts:185"
     },
     {
-      "message": "Missing item type\nThe `change` and `input` actions need to be overridden in the `Input`\nsubclass. Unfortunately, some ember-source builds currently uses babel\nloose mode to transpile its classes. Having the `@action` decorator on the\nsuper class creates a getter on the prototype, and when the subclass\noverrides the method, the loose mode transpilation would emit something\nlike `Subclass.prototype['change'] = function change() { ... }`, which\nfails because `prototype['change']` is getter-only/readonly. The correct\nsolution is to use `Object.defineProperty(prototype, 'change', ...)` but\nthat requires disabling loose mode. For now, the workaround is to add the\ndecorator only on the subclass. This is more of a configuration issue on\nour own builds and doesn't really affect apps.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/abstract-input.ts:132"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:188"
     },
     {
-      "message": "Missing item type\nThe HTML class attribute.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:171"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:190"
     },
     {
-      "message": "Missing item type\nThe HTML type attribute.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/input.ts:182"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:192"
     },
     {
-      "message": "Missing item type\nThe default HTML id attribute. We don't really _need_ one, this is just\nadded for compatibility as it's hard to tell if people rely on it being\npresent, and it doens't really hurt.\n\nHowever, don't rely on this internally, like passing it to `getElementId`.\nThis can be (and often is) overriden by passing an `id` attribute on the\ninvocation, which shadows this default id via `...attributes`.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:40"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:194"
     },
     {
-      "message": "Missing item type\nThe default HTML class attribute. Similar to the above, we don't _need_\nthem, they are just added for compatibility as it's similarly hard to tell\nif people rely on it in their CSS etc, and it doens't really hurt.",
-      "line": " packages/@ember/-internals/glimmer/lib/components/internal.ts:53"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:196"
     },
     {
-      "message": "Missing item type\nThis reference is used to get the `[]` tag of iterables, so we can trigger\nupdates to `{{each}}` when it changes. It is put into place by a template\ntransform at build time, similar to the (-each-in) helper",
-      "line": " packages/@ember/-internals/glimmer/lib/helpers/-track-array.ts:12"
+      "message": "Missing item type",
+      "line": " packages/@ember/array/proxy.ts:198"
     },
     {
-      "message": "Missing item type\nThis is usually inherited from the parent (all the way up to the app\ninstance). However, engines uses this to swap out the owner when crossing\na mount point.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:5"
+      "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:36"
     },
     {
-      "message": "Missing item type\nThe name of the route/template",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:12"
+      "message": "Missing item type\nA convenience alias for {@link TemplateOnlyComponent}",
+      "line": " packages/@ember/component/template-only.ts:44"
     },
     {
-      "message": "Missing item type\nThe controller (the self of the outlet component)",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:17"
+      "message": "Missing item type",
+      "line": " packages/@ember/controller/index.ts:34"
     },
     {
-      "message": "Missing item type\nThe model (the resolved value of the model hook)",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:22"
+      "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"
     },
     {
-      "message": "Missing item type\nThe route's template – this is either a Template or a component, and it\ngets normalized during the render process.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:27"
+      "message": "Missing item type",
+      "line": " packages/@ember/deprecated-features/index.ts:4"
     },
     {
-      "message": "Missing item type\nRepresents what was rendered into this outlet.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:35"
+      "message": "Missing item type",
+      "line": " packages/@ember/engine/index.ts:470"
     },
     {
-      "message": "Missing item type\nRepresents what, if any, should be rendered into the next {{outlet}} found\nat this level.\n\nThis used to be a dictionary of children outlets, including the {{outlet}}\n\"main\" outlet any {{outlet \"named\"}} named outlets. Since named outlets\nare not a thing anymore, this can now just be a single`child`.",
-      "line": " packages/@ember/-internals/glimmer/lib/utils/outlet.ts:40"
+      "message": "Missing item type\nUnfortunately, a lot of existing code assumes booting an instance is\nsynchronous – specifically, a lot of tests assume the last call to\n`app.advanceReadiness()` or `app.reset()` will result in a new instance\nbeing fully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this\nassumption, so we created the asynchronous version above that returns a\npromise. But until we have migrated all the code, we would have to expose\nthis method for use *internally* in places where we need to boot an instance\nsynchronously.",
+      "line": " packages/@ember/engine/instance.ts:132"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:114"
+      "line": " packages/@ember/object/type-tests/core/index.test.ts:10"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/views/outlet.ts:122"
+      "line": " packages/@ember/object/type-tests/core/index.test.ts:19"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:135"
+      "line": " packages/@ember/object/type-tests/core/index.test.ts:28"
     },
     {
-      "message": "Missing item type\nThe type of a function-based helper.",
-      "line": " packages/@ember/-internals/glimmer/lib/helper.ts:325"
+      "message": "Missing item type\nZero-argument case",
+      "line": " packages/@ember/object/type-tests/ember-object.test.ts:11"
     },
     {
-      "message": "Missing item type\nDestroys the render tree and removes all rendered content from the element rendered into",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:546"
+      "message": "Missing item type\nOne-argument case",
+      "line": " packages/@ember/object/type-tests/ember-object.test.ts:22"
     },
     {
-      "message": "Missing item type\nThe GlimmerRenderResult from the last render. Used to get positional\ninformation (firstNode) when a re-render replaces the content, so\nthat the new content is placed at the same DOM position.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:554"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/core.ts:233"
     },
     {
-      "message": "Missing item type\nThe component definition to render.\n\nAny component that has had its manager registered is valid.\nFor the component-types that ship with ember, manager registration\ndoes not need to be worried about.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:585"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/core.ts:237"
     },
     {
-      "message": "Missing item type\nThe element to render the component in to.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:599"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:537"
     },
     {
-      "message": "Missing item type\nOptional owner. Defaults to `{}`, can be any object, but will need to implement the [Owner](https://api.emberjs.com/ember/release/classes/Owner) API for components within this render tree to access services.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:604"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:540"
     },
     {
-      "message": "Missing item type\nOptionally configure the rendering environment",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:608"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:543"
     },
     {
-      "message": "Missing item type\nWhen false, modifiers will not run.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:612"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:546"
     },
     {
-      "message": "Missing item type\nAll other options are forwarded to the underlying renderer.\n(its API is currently private and out of scope for this RFC,\n so passing additional things here is also considered private API)",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:616"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:549"
     },
     {
-      "message": "Missing item type\nThese args get passed to the rendered component\n\nIf your args are reactive, re-rendering will happen automatically.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:624"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:554"
     },
     {
-      "message": "Missing item type\nSAFETY: we should figure out what we need out of a `document` and narrow the API.\n        this exercise should also end up beginning to define what we need for CLI rendering (or to other outputs)",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:633"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:587"
     },
     {
-      "message": "Missing item type\nReplace all contents, if we've rendered multiple times.\n\nhttps://github.com/emberjs/rfcs/pull/1099/files#diff-2b962105b9083ca84579cdc957f27f49407440f3c5078083fa369ec18cc46da8R365\n\nWe could later add an option to not do this behavior\n\nNOTE: destruction is async",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:654"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:644"
     },
     {
-      "message": "Missing item type\nWe can only replace the inner HTML the first time.\nBecause destruction is async, it won't be safe to\ndo this again, and we'll have to rely on the above destroy.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:665"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:670"
     },
     {
-      "message": "Missing item type\nIf there's an existing render result with valid bounds, use its\nfirstNode as the nextSibling so that new content is inserted at\nthe same DOM position. This ensures stable ordering when multiple\nrenderComponent calls target the same element and one is re-invoked\n(e.g., due to tracked dependency changes).\n\nThe old content's DOM nodes are still present (destruction is async),\nso firstNode() is a valid position reference. The new content is placed\nBEFORE the old content. When the old content is eventually destroyed\n(async clear of bounds), the new content remains in the correct position.",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:674"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:677"
     },
     {
-      "message": "Missing item type\nSAFETY: are there consequences for being looser with *this* owner?\n        the public API for `owner` is kinda `Partial<InternalOwner>`\n        aka: implement only what you need.\n        But for actual ember apps, you *need* to implement everything\n        an app needs (which will actually change and become less over time)",
-      "line": " packages/@ember/-internals/glimmer/lib/renderer.ts:742"
+      "message": "Missing item type",
+      "line": " packages/@ember/object/mixin.ts:684"
     },
     {
-      "message": "Missing item type\nTest skipped because when an error occurs,\nwe mess up the cache used by renderComponent.",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:445"
+      "message": "Missing item type",
+      "line": " packages/@ember/routing/lib/location-utils.ts:1"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:560"
+      "line": " packages/@ember/routing/lib/location-utils.ts:15"
     },
     {
-      "message": "Missing item type\nNOTE: subsequent renders to the same element are prepended to the element's children",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:759"
+      "message": "Missing item type",
+      "line": " packages/@ember/routing/lib/location-utils.ts:24"
     },
     {
-      "message": "Missing item type\nERROR in conflict with the NOTE on this test.\nthe elementns flip locations... which is kinda bonkers",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:828"
+      "message": "Missing item type\nReplaces the current location, making sure we explicitly include the origin\nto prevent redirecting to a different origin.",
+      "line": " packages/@ember/routing/lib/location-utils.ts:41"
     },
     {
-      "message": "Missing item type\nWe need to pass a scope so that we get a strict-mode component.",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/render-component-test.ts:925"
+      "message": "Missing item type\ntriggers the callback when the URL changes.",
+      "line": " packages/@ember/routing/location.ts:104"
     },
     {
-      "message": "Missing item type\nThis function is used to hide a variable from the transpiler, so that it\ndoesn't get removed as \"unused\". It does not actually do anything with the\nvariable, it just makes it be part of an expression that the transpiler\nwon't remove.\n\nIt's a bit of a hack, but it's necessary for testing.",
-      "line": " packages/@ember/-internals/glimmer/tests/integration/components/runtime-template-compiler-implicit-test.ts:494"
+      "message": "Missing item type",
+      "line": " packages/@ember/routing/route.ts:266"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:91"
+      "line": " packages/@ember/routing/route.ts:268"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:93"
+      "line": " packages/@ember/routing/route.ts:271"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:95"
+      "line": " packages/@ember/routing/route.ts:273"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:97"
+      "line": " packages/@ember/routing/route.ts:1546"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:99"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:101"
+      "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"
+    },
+    {
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:103"
+      "line": " packages/@ember/runloop/index.ts:88"
+    },
+    {
+      "message": "Missing item type\nA type registry for Ember `Service`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 Service from '@ember/service';\n\nexport default class ExampleService extends Service {\n  // ...\n}\n\ndeclare module '@ember/service' {\n  export interface Registry {\n    example: ExampleService;\n  }\n}\n```\n\nThen `@service` can check that the service is registered correctly, and APIs\nlike `owner.lookup('service:example')` can return `ExampleService`.",
+      "line": " packages/@ember/service/index.ts:107"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:105"
+      "line": " packages/@ember/template-compiler/lib/plugins/allowed-globals.ts:1"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:107"
+      "message": "Missing item type\nThe variable name used to inject the keywords object into the\ntemplate's evaluation scope. auto-import-builtins rewrites bare\nkeyword references (e.g. `on`) to property accesses on this\nvariable (e.g. `__ember_keywords__.on`).",
+      "line": " packages/@ember/template-compiler/lib/compile-options.ts:31"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:110"
+      "message": "Missing item type\nAll possible options passed to `template()` may specify a `moduleName`.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:11"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:112"
+      "message": "Missing item type\nWhether the template should be treated as a strict-mode template. Defaults\nto `true`.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:16"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:114"
+      "message": "Missing item type\nWhen using `template` in a class, you call it in a `static` block and pass\nthe class as the `component` option.\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      // explicit or implicit option goes here\n    );\n  }\n}\n```\n\nFor the full explicit form, see {@linkcode ExplicitClassOptions}. For the\nfull implicit form, see {@linkcode ImplicitClassOptions}.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:23"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:116"
+      "message": "Missing item type\nWhen using `template` outside of a class (i.e. a \"template-only component\"), you can pass\na `scope` option that explicitly provides the lexical scope for the template.\n\nThis is called the \"explicit form\".\n\n```ts\nconst greeting = 'Hello';\nconst HelloWorld = template('{{greeting}} World!', { scope: () => ({ greeting }) });\n```",
+      "line": " packages/@ember/template-compiler/lib/template.ts:45"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:120"
+      "message": "Missing item type\nWhen using `template` *inside* a class (see\n{@linkcode BaseClassTemplateOptions}), you can pass a `scope` option that\nexplicitly provides the lexical scope for the template, just like a template-only\ncomponent (see {@linkcode ExplicitTemplateOnlyOptions}).\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      // explicit or implicit option goes here\n    );\n  }\n}\n```\n\n## The Scope Function's `instance` Parameter\n\nHowever, the explicit `scope` function in a *class* also takes an `instance` option\nthat provides access to the component's instance.\n\nOnce it's supported in Handlebars, this will make it possible to represent private\nfields when using the explicit form.\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.#greeting}}, {{@place}}!',\n      { component: this },\n      scope: (instance) => ({ '#greeting': instance.#greeting }),\n    );\n  }\n}\n```",
+      "line": " packages/@ember/template-compiler/lib/template.ts:60"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:143"
+      "message": "Missing item type\nThe *implicit* form of the `template` function takes an `eval` option that\nallows the runtime compiler to evaluate local template variables without\nneeding to maintain an explicit list of the local variables used in the\ntemplate scope.\n\nThe eval options *must* be passed in the following form:\n\n```ts\n{\n  eval() { return eval(arguments[0]) }\n}\n```\n\n## Requirements of the `eval` Option\n\n**The syntactic form presented above is the only form you should use when\npassing an `eval` option.**\n\nThis is _required_ if you want your code to be compatible with the\ncompile-time implementation of `@ember/template-compiler`. While the runtime\ncompiler offers a tiny bit of additional wiggle room, you still need to follow\nvery strict rules.\n\nWe don't recommend trying to memorize the rules. Instead, we recommend using\nthe snippet presented above and supported by the compile-time implementation.\n\n### The Technical Requirements of the `eval` Option\n\nThe `eval` function is passed a single parameter that is a JavaScript\nidentifier. This will be extended in the future to support private fields.\n\nSince keywords in JavaScript are contextual (e.g. `await` and `yield`), the\nparameter might be a keyword. The `@ember/template-compiler/runtime` expects\nthe function to throw a `SyntaxError` if the identifier name is not valid in\nthe current scope. (The direct `eval` function takes care of this out of the\nbox.)\n\nRequirements:\n\n1. The `eval` method must receive its parameter as `arguments[0]`, which\n   ensures that the variable name passed to `eval()` is not shadowed by the\n   function's parameter name.\n2. The `eval` option must be a function or concise method, and not an arrow.\n   This is because arrows do not have their own `arguments`, which breaks\n   (1).\n3. The `eval` method must call \"*direct* `eval`\", and not an alias of `eval`.\n   Direct `eval` evaluates the code in the scope it was called from, while\n   aliased versions of `eval` (including `new Function`) evaluate the code in\n   the global scope.\n4. The `eval` method must return the result of calling \"direct `eval`\".\n\nThe easiest way to achieve these requirements is to use the exact syntax\npresented above. This is *also* the only way to be compatible\n\n## Rationale\n\nThis is useful for two reasons:\n\n1. This form is a useful _intermediate_ form for the compile-time toolchain.\n   It allows the content-tag preprocessor to convert the `<template>` syntax\n   into valid JavaScript without needing to involve full-fledged lexical\n   analysis.\n2. This form is a convenient form for manual prototyping when using the\n   runtime compiler directly. While it requires some extra typing relative to\n   `<template>`, it's a mechanical 1:1 transformation of the syntax.\n\nIn practice, implementations that use a runtime compiler (for example, a\nplayground running completely in the browser) should probably use the\n`content-tag` preprocessor to convert the template into the implicit form,\nand then rely on `@ember/template-compiler/runtime` to evaluate the template.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:102"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:157"
+      "message": "Missing item type\nWhen using `template` outside of a class (i.e. a \"template-only component\"), you can pass\nan `eval` option that _implicitly_ provides the lexical scope for the template.\n\nThis is called the \"implicit form\".\n\n```ts\nconst greeting = 'Hello';\nconst HelloWorld = template('{{greeting}} World!', {\n  eval() { return arguments[0] }\n});\n```\n\nFor more details on the requirements of the `eval` option, see {@linkcode ImplicitEvalOption}.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:182"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:162"
+      "message": "Missing item type\nWhen using `template` inside of a class, you can pass an `eval` option that\n_implicitly_ provides the lexical scope for the template, just as you can\nwith a {@linkcode ImplicitTemplateOnlyOptions | template-only component}.\n\nThis is called the \"implicit form\".\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      eval() { return arguments[0] }\n    );\n  }\n}\n```\n\n## Note  on Private Fields\n\nThe current implementation of `@ember/template-compiler` does not support\nprivate fields, but once the Handlebars parser adds support for private field\nsyntax and it's implemented in the Glimmer compiler, the implicit form should\nbe able to support them.",
+      "line": " packages/@ember/template-compiler/lib/template.ts:199"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:167"
+      "message": "Missing item type\nBuilds the source wireformat JSON block",
+      "line": " packages/@ember/template-compiler/lib/template.ts:256"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:172"
+      "message": "Missing item type\nExists for historical reasons, should not be in new code, as\nthe module name does not correspond to anything meaningful at runtime.",
+      "line": " packages/@ember/template-compiler/lib/types.ts:31"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:177"
+      "message": "Missing item type\nNot available at runtime",
+      "line": " packages/@ember/template-compiler/lib/types.ts:37"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:182"
+      "message": "Missing item type\nUtils unique to the runtime compiler",
+      "line": " packages/@ember/template-compiler/lib/types.ts:42"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:197"
+      "message": "Missing item type\nThis supports template blocks defined in class bodies.\n\nManual form:\n\n```ts\nclass MyComponent {\n  static {\n    template(templateContent, {\n      component: this,\n      eval: () => eval(arguments[0])\n    })\n  }\n}\n```\n\nGJS form (compiled to the manual form via `content-tag`):\n\n```ts\nclass MyComponent {\n  <template>Template Content</template>\n}\n```",
+      "line": " packages/@ember/template-compiler/lib/types.ts:50"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:210"
+      "message": "Missing item type\nDifferences:\n\n- strict mode variables always refer to in-scope variables\n- loose mode variables use this algorithm:\n  1. otherwise, fall back to `this.<name>`",
+      "line": " packages/@glimmer/compiler/lib/builder/builder-interface.ts:70"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:217"
+      "message": "Missing item type\nThe special value 'splat' is used to indicate that the attribute is a splat",
+      "line": " packages/@glimmer/compiler/lib/builder/builder-interface.ts:588"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:224"
+      "message": "Missing item type\nA \"generic\" keyword is something like `has-block`, which makes sense in the context\nof sub-expression or append",
+      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts:108"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:231"
+      "message": "Missing item type\nThis function builds keyword definitions for a particular type of AST node (`KeywordType`).\n\nYou can build keyword definitions for:\n\n- `Expr`: A `SubExpression` or `PathExpression`\n- `Block`: A `BlockStatement`\n  - A `BlockStatement` is a keyword candidate if its head is a\n    `PathExpression`\n- `Append`: An `AppendStatement`\n\nA node is a keyword candidate if:\n\n- A `PathExpression` is a keyword candidate if it has no tail, and its\n  head expression is a `LocalVarHead` or `FreeVarHead` whose name is\n  the keyword's name.\n- A `SubExpression`, `AppendStatement`, or `BlockStatement` is a keyword\n  candidate if its head is a keyword candidate.\n\nThe keyword infrastructure guarantees that:\n\n- If a node is not a keyword candidate, it is never passed to any keyword's\n  `assert` method.\n- If a node is not the `KeywordType` for a particular keyword, it will not\n  be passed to the keyword's `assert` method.\n\n`Expr` keywords are used in expression positions and should return HIR\nexpressions. `Block` and `Append` keywords are used in statement\npositions and should return HIR statements.\n\nA keyword definition has two parts:\n\n- `match`, which determines whether an AST node matches the keyword, and can\n  optionally return some information extracted from the AST node.\n- `translate`, which takes a matching AST node as well as the extracted\n  information and returns an appropriate HIR instruction.\n\n# Example\n\nThis keyword:\n\n- turns `(hello)` into `\"hello\"`\n  - as long as `hello` is not in scope\n- makes it an error to pass any arguments (such as `(hello world)`)\n\n```ts\nkeywords('SubExpr').kw('hello', {\n  assert(node: ExprKeywordNode): Result<void> | false {\n    // we don't want to transform `hello` as a `PathExpression`\n    if (node.type !== 'SubExpression') {\n      return false;\n    }\n\n    // node.head would be `LocalVarHead` if `hello` was in scope\n    if (node.head.type !== 'FreeVarHead') {\n      return false;\n    }\n\n    if (node.params.length || node.hash) {\n      return Err(generateSyntaxError(`(hello) does not take any arguments`), node.loc);\n    } else {\n      return Ok();\n    }\n  },\n\n  translate(node: ASTv2.SubExpression): hir.Expression {\n    return ASTv2.builders.literal(\"hello\", node.loc)\n  }\n})\n```\n\nThe keyword infrastructure checks to make sure that the node is the right\ntype before calling `assert`, so you only need to consider `SubExpression`\nand `PathExpression` here. It also checks to make sure that the node passed\nto `assert` has the keyword name in the right place.\n\nNote the important difference between returning `false` from `assert`,\nwhich just means that the node didn't match, and returning `Err`, which\nmeans that the node matched, but there was a keyword-specific syntax\nerror.",
+      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts:227"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:238"
+      "message": "Missing item type\nNormalize paths into `hir.Path` or a `hir.Expr` that corresponds to the ref.\n\nTODO since keywords don't support tails anyway, distinguish PathExpression from\nVariableReference in ASTv2.",
+      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/visitors/expressions.ts:51"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:255"
+      "message": "Missing item type\nThis is the mutable state for this compiler pass.",
+      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/context.ts:10"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:270"
+      "message": "Missing item type\nNormalize the AST from @glimmer/syntax into the HIR. The HIR has special\ninstructions for keywords like `{{yield}}`, `(has-block)` and\n`{{#in-element}}`.\n\nMost importantly, it also classifies HTML element syntax into:\n\n1. simple HTML element (with optional splattributes)\n2. component invocation\n\nBecause the @glimmer/syntax AST gives us a string for an element's tag,\nthis pass also normalizes that string into an expression.\n\n```\n// normalized into a path expression whose head is `this` and tail is\n// `[\"x\"]`\n<this.x />\n\n{{#let expr as |t|}}\n  // `\"t\"` is normalized into a variable lookup.\n  <t />\n\n  // normalized into a path expression whose head is the variable lookup\n  // `t` and tail is `[\"input\"]`.\n  <t.input />\n{{/let}}\n\n// normalized into a free variable lookup for `SomeComponent` (with the\n// context `ComponentHead`).\n<SomeComponent />\n\n// normalized into a path expression whose head is the free variable\n// `notInScope` (with the context `Expression`), and whose tail is\n// `[\"SomeComponent\"]`. In resolver mode, this path will be rejected later,\n// since it cannot serve as an input to the resolver.\n<notInScope.SomeComponent />\n```",
+      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/index.ts:17"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:284"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:289"
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:30"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:309"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:323"
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:74"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:329"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:334"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:355"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:370"
+      "message": "Missing item type\nCalled before the component has been removed from the DOM.",
+      "line": " packages/@glimmer/component/dist/-private/component.d.ts:239"
     },
     {
-      "message": "Missing item type\nFlattening is based on a global revision counter. If the revision has\nbumped it means that somewhere in a class inheritance chain something has\nchanged, so we need to reflatten everything. This can only happen if:\n\n1. A meta has been flattened (listener has been called)\n2. The meta is a prototype meta with children who have inherited its\n   listeners\n3. A new listener is subsequently added to the meta (e.g. via `.reopen()`)\n\nThis is a very rare occurrence, so while the counter is global it shouldn't\nbe updated very often in practice.",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:477"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:551"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/meta/lib/meta.ts:582"
+      "line": " packages/@glimmer/component/dist/index.js:47"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/computed.ts:715"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/computed.ts:721"
+      "line": " packages/@glimmer/component/dist/index.js:66"
     },
     {
-      "message": "Missing item type\nPrimarily used for cases where we are redefining a class, e.g. mixins/reopen\nbeing applied later. Revalidates all the observers, resetting their tags.",
-      "line": " packages/@ember/-internals/metal/lib/observer.ts:156"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/metal/lib/tracked.ts:14"
+      "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"
     },
     {
-      "message": "Missing item type\nA type registry for the DI system, which other participants in the DI system\ncan register themselves into with declaration merging. The contract for this\ntype is that its keys are the `Type` from a `FullName`, and each value for a\n`Type` is another registry whose keys are the `Name` from a `FullName`. The\nmechanic for providing a registry is [declaration merging][handbook].\n\n[handbook]: https://www.typescriptlang.org/docs/handbook/declaration-merging.html\n\nFor example, Ember's `@ember/service` module includes this set of definitions:\n\n```ts\nexport default class Service extends EmberObject {}\n\n// For concrete singleton classes to be merged into.\ninterface Registry extends Record<string, Service> {}\n\ndeclare module '@ember/owner' {\n  service: Registry;\n}\n```\n\nDeclarations of services can then include the registry:\n\n```ts\nimport Service from '@ember/service';\n\nexport default class Session extends Service {\n  login(username: string, password: string) {\n    // ...\n  }\n}\n\ndeclare module '@ember/service' {\n  interface Registry {\n    session: Session;\n  }\n}\n```\n\nThen users of the `Owner` API will be able to do things like this with strong\ntype safety guarantees:\n\n```ts\ngetOwner(this)?.lookup('service:session').login(\"hello\", \"1234abcd\");\n```",
-      "line": " packages/@ember/-internals/owner/index.ts:24"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/owner/index.ts:79"
+      "message": "Missing item type\nCalled before the component has been removed from the DOM.",
+      "line": " packages/@glimmer/component/dist/index.js:244"
     },
     {
-      "message": "Missing item type\nA record mapping all known items of a given type: if the item is known it\nwill be `true`; otherwise it will be `false` or `undefined`.",
-      "line": " packages/@ember/-internals/owner/index.ts:408"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/owner/index.ts:730"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/container_proxy.ts:21"
+      "line": " packages/@glimmer/component/src/-private/component.ts:56"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/registry_proxy.ts:21"
+      "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"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/-internals/runtime/lib/mixins/target_action_support.ts:31"
+      "line": " packages/@glimmer/component/src/-private/component.ts:97"
     },
     {
-      "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```",
-      "line": " packages/@ember/-internals/string/index.ts:93"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/-internals/utils/lib/guid.ts:8"
+      "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"
     },
     {
-      "message": "Missing item type\nGenerates a universally unique identifier. This method\nis used internally by Ember for assisting with\nthe generation of GUID's and other unique identifiers.",
-      "line": " packages/@ember/-internals/utils/lib/guid.ts:14"
+      "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"
     },
     {
-      "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\nCalled before the component has been removed from the DOM.",
+      "line": " packages/@glimmer/component/src/-private/component.ts:282"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/application/index.ts:33"
+      "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/src/-private/ember-component-manager.ts:24"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/application/index.ts:38"
+      "message": "Missing item type\nA dynamic operand has a value that can't be easily represented as an embedded string.",
+      "line": " packages/@glimmer/debug/lib/dism/dism.ts:43"
     },
     {
-      "message": "Missing item type\nUnfortunately, a lot of existing code assumes the booting process is\n\"synchronous\". Specifically, a lot of tests assumes the last call to\n`app.advanceReadiness()` or `app.reset()` will result in the app being\nfully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this assumption,\nso we created the asynchronous version above that returns a promise. But until\nwe have migrated all the code, we would have to expose this method for use\n*internally* in places where we need to boot an app \"synchronously\".",
-      "line": " packages/@ember/application/index.ts:688"
+      "message": "Missing item type\nA variable is a numeric offset into the stack (relative to the $fp register).",
+      "line": " packages/@glimmer/debug/lib/dism/dism.ts:63"
     },
     {
-      "message": "Missing item type\nOverrides the base `EngineInstance._bootSync` method with concerns relevant\nto booting application (instead of engine) instances.\n\nThis method should only contain synchronous boot concerns. Asynchronous\nboot concerns should eventually be moved to the `boot` method, which\nreturns a promise.\n\nUntil all boot code has been made asynchronous, we need to continue to\nexpose this method for use *internally* in places where we need to boot an\ninstance synchronously.",
-      "line": " packages/@ember/application/instance.ts:81"
+      "message": "Missing item type\nThe `LogFragmentBuffer` is responsible for collecting the fragments that are logged to the\n`DebugLogger` so that they can be accumulated during a group and flushed together.\n\nThis queuing serves two purposes:\n\n1. To allow the individual fragments that make up a single line to append their values to\n   the current line. To accomplish this, each fragment can append static content and its\n   formatting specifier (e.g. `%o`) to the accumulated {@link #template} *and* append the\n   value to format to the {@link #substitutions} array.\n2. To allow logs that refer to objects to be represented as footnotes in the current line,\n   with the footnote to be printed in a later line.\n\nThis allows a list of fragments, each of which represent formattable values, to be flattened\ninto a single template string and an array of values to format.\n\n## Footnotes\n\nAn opcode slice containing constant references will be logged like this:\n\n```\n...\n362. (PushArgs names=[] block-names=[] flags=16)\n366. (Helper helper=[0])\n[0] glimmerHelper()\n368. (PopFrame)\n369. (Fetch register=$v0)\n371. (Primitive constant=\"/index.html\")\n...\n```\n\nThe fragment for line `366` includes an `ObjectFragment` for the helper value. When logged,\nthe object will be represented as a footnote and the value will be printed in a later\nline.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:6"
     },
     {
-      "message": "Missing item type\nThis hook is called by the root-most Route (a.k.a. the ApplicationRoute)\nwhen it has finished creating the root View. By default, we simply take the\nview and append it to the `rootElement` specified on the Application.\n\nIn cases like FastBoot and testing, we can override this hook and implement\ncustom behavior, such as serializing to a string and sending over an HTTP\nsocket rather than appending to DOM.",
-      "line": " packages/@ember/application/instance.ts:141"
+      "message": "Missing item type\nThe first parameter to the `console.log` family of APIs is a *template* that can use\nformat specifiers (e.g. `%c`, `%o`, and `%O`) to refer to subsequent parameters.\n\nWhen a fragment is appended to a line,",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:42"
     },
     {
-      "message": "Missing item type\nTells the router to start routing. The router will ask the location for the\ncurrent URL of the page to determine the initial URL to start routing to.\nTo start the app at a specific URL, call `handleURL` instead.",
-      "line": " packages/@ember/application/instance.ts:158"
+      "message": "Missing item type\nEach format specified in the {@link #template} corresponds to a value in the\n`#substitutions` array.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:50"
     },
     {
-      "message": "Missing item type\nSets up the router, initializing the child router and configuring the\nlocation before routing begins.\n\nBecause setup should only occur once, multiple calls to `setupRouter`\nbeyond the first call have no effect.\n\nThis is commonly used in order to confirm things that rely on the router\nare functioning properly from tests that are primarily rendering related.\n\nFor example, from within [ember-qunit](https://github.com/emberjs/ember-qunit)'s\n`setupRenderingTest` calling `this.owner.setupRouter()` would allow that\nrendering test to confirm that any `<LinkTo></LinkTo>`'s that are rendered\nhave the correct URL.",
-      "line": " packages/@ember/application/instance.ts:169"
+      "message": "Missing item type\nThe logging options for the buffer, which currently only contains `showSubtle`.\n\nWhen fragments call the buffer's {@linkcode append} method, they specify whether the\ncontent to append is subtle or not. If the buffer is not configured to show subtle\ncontent, the content is not appended.\n\nThis allows fragments to append content to the buffer without having to know how the\nbuffer is configured.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:56"
     },
     {
-      "message": "Missing item type\nDirects the router to route to a particular URL. This is useful in tests,\nfor example, to tell the app to start at a particular URL.",
-      "line": " packages/@ember/application/instance.ts:190"
+      "message": "Missing item type\nA single line can produce multiple queued log entries. This happens when fragments\nappend *footnotes* to the buffer. A *reference* to the footnote is appended to the\nprimary line, and a line containing the *value* of the footnote is appended to the\n`#queued` array.\n\nBoth the primary line and any queued footnotes are flushed together when the buffer\nis flushed.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:68"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/application/instance.ts:202"
+      "message": "Missing item type\nAdd a footnoted value to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.\n\nThis method takes two callbacks: `add` and `append`.\n\nThe `append` callback behaves like {@linkcode append}, but without the `subtle` argument. If\n`addFootnoted` is called with `subtle: false`, then the callback will never be called, so\nthere is no need to pass the `subtle` argument again.\n\nThe `add` callback is responsible for appending the footnote itself to the buffer. The first\nparameter to `add` (`useNumber`) specifies whether the caller has used the footnote number\nto refer to the footnote.\n\nThis is typically true, but fragments can specify an alternative annotation that should be used\ninstead of the default footnote number. In that case, the footnote number is not used, and the\nnext footnote is free to use it.\n\nThe `add` callback also takes a template string and an optional list of substitutions, which\ndescribe the way the footnote itself should be formatted.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:85"
     },
     {
-      "message": "Missing item type\nReturns the current URL of the app instance. This is useful when your\napp does not update the browsers URL bar (i.e. it uses the `'none'`\nlocation adapter).",
-      "line": " packages/@ember/application/instance.ts:224"
+      "message": "Missing item type\nAppend a fragment to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.",
+      "line": " packages/@glimmer/debug/lib/render/buffer.ts:134"
     },
     {
-      "message": "Missing item type\nNavigate the instance to a particular URL. This is useful in tests, for\nexample, or to tell the app to start at a particular URL. This method\nreturns a promise that resolves with the app instance when the transition\nis complete, or rejects if the transition was aborted due to an error.",
-      "line": " packages/@ember/application/instance.ts:239"
+      "message": "Missing item type\nThe prepend function returns a subtle fragment if the contents are subtle.",
+      "line": " packages/@glimmer/debug/lib/render/combinators.ts:6"
     },
     {
-      "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:1915"
+      "message": "Missing item type\nThe append function returns a subtle fragment if the contents are subtle.",
+      "line": " packages/@glimmer/debug/lib/render/combinators.ts:13"
     },
     {
-      "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:1932"
+      "message": "Missing item type\nThe `wrap` function returns a subtle fragment if the contents are subtle.",
+      "line": " packages/@glimmer/debug/lib/render/combinators.ts:19"
     },
     {
-      "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:1956"
+      "message": "Missing item type\nA compact array makes the wrapping `[]` subtle if there's only one element.",
+      "line": " packages/@glimmer/debug/lib/render/combinators.ts:53"
     },
     {
-      "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:1961"
+      "message": "Missing item type\nA Loggable is either:\n\n1. a single log line\n2. a log line as a header followed by a group of log entries",
+      "line": " packages/@glimmer/debug/lib/render/entry.ts:1"
     },
     {
-      "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:1966"
+      "message": "Missing item type\nLogLine represents a single line in the log. The line is logged *either* by passing the `line`\nvalues to `console.{log,info,debug,warn,error}` *or* by passing them to `console.group` to\nrepresent the header of a group.",
+      "line": " packages/@glimmer/debug/lib/render/entry.ts:11"
     },
     {
-      "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:1971"
+      "message": "Missing item type\nLogGroup represents a group of log entries. It is logged by calling *either* `console.group` or\n`console.groupCollapsed` (depending on the value of `collapsed`).",
+      "line": " packages/@glimmer/debug/lib/render/entry.ts:21"
     },
     {
-      "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:1976"
+      "message": "Missing item type\nA leaf fragment that represents an arbitrary value.\n\nWhen the value is a primitive, the fragment is appended to the buffer as if it was an instance of\nthe appropriate leaf fragment type (e.g. strings are appended as if they were `StringFragment`).\n\nOtherwise, `ValueFragment` is appended to the current line as a footnote reference and the value\nitself is appended to a later line that *defines* the footnote using the `%O` format specifier.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:19"
     },
     {
-      "message": "Missing item type\nReverse objects in the array. Works just like `reverse()` but it is\nKVO-compliant.",
-      "line": " packages/@ember/array/index.ts:1981"
+      "message": "Missing item type\nThe `ValueFragment` is appended to the current line as a footnote reference (e.g. `[1]`) and\nthe value itself is appended to a later line that *defines* the footnote (e.g. `[1]\nObjectHere`).\n\nBy default, the footnote reference is an incrementing number per log line, and the footnote\nvalue is formatted using the `%O` format specifier.\n\nThe `display` property can be provided to override these defaults.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:32"
     },
     {
-      "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:1986"
+      "message": "Missing item type\nA leaf fragment that represents a string value.\n\nCorresponds to the `%s` format specifier.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:48"
     },
     {
-      "message": "Missing item type\nRemoves each object in the passed array from the receiver.",
-      "line": " packages/@ember/array/index.ts:2008"
+      "message": "Missing item type\nA leaf fragment that represents an integer value.\n\nCorresponds to the `%d` format specifier.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:58"
     },
     {
-      "message": "Missing item type\nAdds each object in the passed enumerable to the receiver.",
-      "line": " packages/@ember/array/index.ts:2029"
+      "message": "Missing item type\nA leaf fragment that represents a float value.\n\nCorresponds to the `%f` format specifier.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:68"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:178"
+      "message": "Missing item type\nA leaf fragment that represents a DOM node.\n\nCorresponds to the `%o` format specifier.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:78"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:180"
+      "message": "Missing item type\nThe list of leaf fragment types correspond exactly to the list of console.log\nformat specifiers.",
+      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:88"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:183"
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:21"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:185"
+      "message": "Missing item type\nFragment is the most fundamental building block of the debug logger.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:25"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:188"
+      "message": "Missing item type\nA subtle fragment is only printed if the `showSubtle` option is set.\n\nReturns true if this fragment is a subtle leaf or is a multi fragment\nwith all subtle leaves.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:68"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:190"
+      "message": "Missing item type\nIf the current fragment is not empty, apply `ifPresent` to the current\nfragment. Otherwise, do nothing.\n\nIf the current fragment is subtle, the result is also subtle.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:78"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:192"
+      "message": "Missing item type\nA fragment is empty if it should not be printed with the provided display options.\n\nThis means that if a fragment is subtle and `showSubtle` is false, the fragment is empty.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:90"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:194"
+      "message": "Missing item type\nReturns an array of {@linkcode LeafFragment}s that make up the current\nfragment.\n\nThis effectively flattens any number of nested multi-fragments into a flat array of leaf\nfragments.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:99"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:196"
+      "message": "Missing item type\nReturns a fragment with the specified subtle status without mutating the current fragment.\n\nIf `isSubtle` is true, the fragment will also be styled with the `subtle` style.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:116"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/array/proxy.ts:198"
+      "message": "Missing item type\nApply the specified styles to the current fragment (if it's a leaf) or all\nof its children (if it's a multi-fragment).\n\nKeep in mind that merging styles might be very difficult to undo, so treat\nthis as a low-level operation, and prefer to use higher-level concepts like\n`subtle` if you can instead.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:144"
     },
     {
-      "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:36"
+      "message": "Missing item type\nConvert the current fragment into a string with no additional formatting.\nThe primary purpose for this method is to support converting a fragment\ninto a string for inclusion in thrown Errors. If you're going to *log*\na fragment, log it using `DebugLogger` and don't convert it to\na string first.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:168"
     },
     {
-      "message": "Missing item type\nA convenience alias for {@link TemplateOnlyComponent}",
-      "line": " packages/@ember/component/template-only.ts:44"
+      "message": "Missing item type\nShould the current fragment be printed with the provided display options?\n\nImportantly, if the current fragment contains subtle content but the `showSubtle` option is\nfalse, `#shouldShow` will return false.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:191"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/controller/index.ts:34"
+      "message": "Missing item type\nConvert this fragment into a Loggable for logging through the `DebugLogger`.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:213"
     },
     {
-      "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"
+      "message": "Missing item type\nAppend this fragment to the low-level `LogFragmentBuffer`.",
+      "line": " packages/@glimmer/debug/lib/render/fragment.ts:226"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/deprecated-features/index.ts:4"
+      "message": "Missing item type\nA dynamic operand has a value that can't be easily represented as an embedded string.",
+      "line": " packages/@glimmer/debug/lib/debug.ts:235"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/engine/index.ts:470"
+      "message": "Missing item type\nA variable is a numeric offset into the stack (relative to the $fp register).",
+      "line": " packages/@glimmer/debug/lib/debug.ts:255"
     },
     {
-      "message": "Missing item type\nUnfortunately, a lot of existing code assumes booting an instance is\nsynchronous – specifically, a lot of tests assume the last call to\n`app.advanceReadiness()` or `app.reset()` will result in a new instance\nbeing fully-booted when the current runloop completes.\n\nWe would like new code (like the `visit` API) to stop making this\nassumption, so we created the asynchronous version above that returns a\npromise. But until we have migrated all the code, we would have to expose\nthis method for use *internally* in places where we need to boot an instance\nsynchronously.",
-      "line": " packages/@ember/engine/instance.ts:132"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/debug/lib/metadata.ts:34"
     },
     {
-      "message": "Missing item type\nUsing the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```\n<template>\n  {{#each-in (hash givenName='Jen' familyName='Weber') as |key value|}}\n    <p>{{key}}: {{value}}</p>\n  {{/each-in}}\n</template>\n```",
-      "line": " packages/@ember/helper/index.ts:346"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/debug/lib/metadata.ts:36"
     },
     {
-      "message": "Missing item type\nUsing the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```js\n\n<template>\n  <ul>\n  {{#each (array 'Tom Dale' 'Yehuda Katz' @anotherPerson) as |person|}}\n    <li>{{person}}</li>\n  {{/each}}\n  </ul>\n</template>\n```",
-      "line": " packages/@ember/helper/index.ts:361"
+      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\nFF\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
+      "line": " packages/@glimmer/debug-util/lib/assert.ts:19"
     },
     {
-      "message": "Missing item type\nThe `{{concat}}` helper makes it easy to dynamically send a number of\nparameters to a component or helper as a single parameter in the format of a\nconcatenated string.\n\nFor example:\n\n```js\nimport { concat } from '@ember/helper';\n\n<template>\n  {{get @foo (concat \"item\" @index)}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
-      "line": " packages/@ember/helper/index.ts:379"
+      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
+      "line": " packages/@glimmer/debug-util/lib/assert.ts:29"
     },
     {
-      "message": "Missing item type\nThe `{{get}}` helper makes it easy to dynamically look up a property on an\nobject or an element in an array. The second argument to `{{get}}` can be a\nstring or a number, depending on the object being accessed.\n\nTo access a property on an object with a string key:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someObject \"objectKey\"}}\n</template>\n```\n\nTo access the first element in an array:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @someArray 0}}\n</template>\n```\n\nTo access a property on an object with a dynamic key:\n\n```js\nimport { get } from '@ember/helper';\n\n<template>\n  {{get @address @field}}\n</template>\n```\n\nThis will display the result of `@foo.item1` when `index` is `1`, and\n`this.foo.item2` when `index` is `2`, etc.",
-      "line": " packages/@ember/helper/index.ts:400"
+      "message": "Missing item type\nAn object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function does nothing (and is removed\nby the minifier in builder).",
+      "line": " packages/@glimmer/debug-util/lib/debug-brand.ts:15"
     },
     {
-      "message": "Missing item type\n`{{fn}}` is a helper that receives a function and some arguments, and returns\na new function that combines. This allows you to pass parameters along to\nfunctions in your templates:\n\n```js\nimport { fn } from '@ember/helper';\n\nfunction showAlert(message) {\n  alert(`The message is: '${message}'`);\n}\n\n<template>\n  <button type=\"button\" {{on \"click\" (fn showAlert \"Hello!\")}}>\n    Click me!\n  </button>\n</template>\n```",
-      "line": " packages/@ember/helper/index.ts:441"
+      "message": "Missing item type\nAn object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function always returns undefined. However,\nthis function should only be called by the trace logger, which should only\nrun in trace `LOCAL_DEBUG` + `LOCAL_TRACE_LOGGING` mode.",
+      "line": " packages/@glimmer/debug-util/lib/debug-brand.ts:38"
     },
     {
-      "message": "Missing item type\nUse the {{uniqueId}} helper to generate a unique ID string suitable for use as\nan ID attribute in the DOM.\n\nEach invocation of {{uniqueId}} will return a new, unique ID string.\nYou can use the `let` helper to create an ID that can be reused within a template.\n\n```js\nimport { uniqueId } from '@ember/helper';\n\n<template>\n  {{#let (uniqueId) as |emailId|}}\n    <label for={{emailId}}>Email address</label>\n    <input id={{emailId}} type=\"email\" />\n  {{/let}}\n</template>\n```",
-      "line": " packages/@ember/helper/index.ts:578"
+      "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/@ember/object/type-tests/core/index.test.ts:10"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/type-tests/core/index.test.ts:19"
+      "message": "Missing item type\nInterfaces\n\nTODO: Move these into @glimmer/interfaces, move @glimmer/interfaces to",
+      "line": " packages/@glimmer/global-context/index.ts:21"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/type-tests/core/index.test.ts:28"
+      "message": "Missing item type\nSchedules a VM revalidation.\n\nNote: this has a default value so that tags can warm themselves when first loaded.",
+      "line": " packages/@glimmer/global-context/index.ts:37"
     },
     {
-      "message": "Missing item type\nZero-argument case",
-      "line": " packages/@ember/object/type-tests/ember-object.test.ts:11"
+      "message": "Missing item type\nSchedules a destructor to run",
+      "line": " packages/@glimmer/global-context/index.ts:44"
     },
     {
-      "message": "Missing item type\nOne-argument case",
-      "line": " packages/@ember/object/type-tests/ember-object.test.ts:22"
+      "message": "Missing item type\nFinalizes destruction",
+      "line": " packages/@glimmer/global-context/index.ts:55"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:233"
+      "message": "Missing item type\nHook to provide iterators for `{{each}}` loops",
+      "line": " packages/@glimmer/global-context/index.ts:62"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/core.ts:237"
+      "message": "Missing item type\nHook to specify truthiness within Glimmer templates",
+      "line": " packages/@glimmer/global-context/index.ts:69"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:537"
+      "message": "Missing item type\nHook for specifying how Glimmer should access properties in cases where it\nneeds to. For instance, accessing an object's values in templates.",
+      "line": " packages/@glimmer/global-context/index.ts:76"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:540"
+      "message": "Missing item type\nHook for specifying how Glimmer should update props in cases where it needs\nto. For instance, when updating a template reference (e.g. 2-way-binding)",
+      "line": " packages/@glimmer/global-context/index.ts:85"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:543"
+      "message": "Missing item type\nHook for specifying how Glimmer should access paths in cases where it needs\nto. For instance, the `key` value of `{{each}}` loops.",
+      "line": " packages/@glimmer/global-context/index.ts:95"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:546"
+      "message": "Missing item type\nHook for specifying how Glimmer should update paths in cases where it needs\nto. For instance, when updating a template reference (e.g. 2-way-binding)",
+      "line": " packages/@glimmer/global-context/index.ts:104"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:549"
+      "message": "Missing item type\nHook to warn if a style binding string or value was not marked as trusted\n(e.g. HTMLSafe)",
+      "line": " packages/@glimmer/global-context/index.ts:113"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:554"
+      "message": "Missing item type\nHook to customize assertion messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
+      "line": " packages/@glimmer/global-context/index.ts:119"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:587"
+      "message": "Missing item type\nHook to customize deprecation messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
+      "line": " packages/@glimmer/global-context/index.ts:135"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:644"
+      "message": "Missing item type\nA Handlebars statement",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:303"
     },
     {
       "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:670"
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:344"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:677"
+      "message": "Missing item type\nA JSON object that the Block was serialized into.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:362"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/object/mixin.ts:684"
+      "message": "Missing item type\nA JSON object that the compiled TemplateBlock was serialized into.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:369"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/lib/location-utils.ts:1"
+      "message": "Missing item type\nA JSON object that the compiled Template was serialized into.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:378"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/lib/location-utils.ts:15"
+      "message": "Missing item type\nA string of JSON containing a SerializedTemplateBlock",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:387"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/lib/location-utils.ts:24"
+      "message": "Missing item type\nA JSON object containing the SerializedTemplateBlock as JSON and TemplateMeta.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:392"
     },
     {
-      "message": "Missing item type\nReplaces the current location, making sure we explicitly include the origin\nto prevent redirecting to a different origin.",
-      "line": " packages/@ember/routing/lib/location-utils.ts:41"
+      "message": "Missing item type\nA string of Javascript containing a SerializedTemplateWithLazyBlock to be\nconcatenated into a Javascript module.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:403"
     },
     {
-      "message": "Missing item type\ntriggers the callback when the URL changes.",
-      "line": " packages/@ember/routing/location.ts:104"
+      "message": "Missing item type\nA VariableResolutionContext explains how a variable name should be resolved.",
+      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/resolution.d.ts:1"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:266"
+      "message": "Missing item type\nThe Encoder receives a stream of opcodes from the syntax compiler and turns\nthem into a binary program.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:134"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:268"
+      "message": "Missing item type\nFinalize the current compilation unit, add a `(Return)`, and push the opcodes from\nthe buffer into the program. At this point, some of the opcodes might still be\nplaceholders, such as in the case of recursively compiled templates.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:139"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:271"
+      "message": "Missing item type\nPush a syscall into the program with up to three optional\noperands.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:149"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:273"
+      "message": "Missing item type\nStart a new labels block. A labels block is a scope for labels that\ncan be referred to before they are declared. For example, when compiling\nan `if`, the `JumpUnless` opcode occurs before the target label. To\naccommodate this use-case ergonomically, the `Encoder` allows a syntax\nto create a labels block and then refer to labels that have not yet\nbeen declared. Once the block is complete, a second pass replaces the\nlabel names with offsets.\n\nThe pattern is:\n\n```ts\nencoder.reserve(Op.JumpUnless);\nencoder.target(encoder.pos, 'ELSE');\n```\n\nThe `reserve` method creates a placeholder opcode with space for a target\nin the future, and the `target` method registers the blank operand position\nto be replaced with an offset to `ELSE`, once it's known.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:163"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/routing/route.ts:1546"
+      "message": "Missing item type\nFinish the current labels block and replace label names with offsets,\nnow that all of the offsets are known.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:185"
     },
     {
-      "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"
+      "message": "Missing item type\nMark the current position with a label name. This label name\ncan be used by any other opcode in this label block.",
+      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:191"
     },
     {
-      "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"
+      "message": "Missing item type\n`AppendingBlock` is the interface used by the `ElementBuilder` to keep track of which nodes have\nbeen appended to a block. Ultimately, an `AppendingBlock` is finalized and used as a `FixedBlock`\nor `ResettableBlock` during the updating phase.",
+      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:15"
     },
     {
-      "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"
+      "message": "Missing item type\nA `FixedBlock` is a block that is only rendered once, during initial render. Its *children* may\nchange during the updating phase, and this may cause its *bounds* to change, but the block itself\nremains stable.",
+      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:30"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/runloop/index.ts:88"
+      "message": "Missing item type\nA `ResettableBlock` can be reset during the updating phase and rendered again.\n\nThis occurs for two reasons:\n\n1. The block represents an element in a list, and the element has been removed\n2. The block represents a conditional, and the condition has changed",
+      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:38"
     },
     {
-      "message": "Missing item type\nA type registry for Ember `Service`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 Service from '@ember/service';\n\nexport default class ExampleService extends Service {\n  // ...\n}\n\ndeclare module '@ember/service' {\n  export interface Registry {\n    example: ExampleService;\n  }\n}\n```\n\nThen `@service` can check that the service is registered correctly, and APIs\nlike `owner.lookup('service:example')` can return `ExampleService`.",
-      "line": " packages/@ember/service/index.ts:107"
+      "message": "Missing item type\nDescribes the capabilities of a particular component. The capabilities are\nprovided to the Glimmer compiler and VM via the ComponentDefinition, which\nincludes a ComponentCapabilities record.\n\nCertain features in the VM come with some overhead, so the compiler and\nruntime use this information to skip unnecessary work for component types\nthat don't need it.\n\nFor example, a component that is template-only (i.e., it does not have an\nassociated JavaScript class to instantiate) can skip invoking component\nmanager hooks related to lifecycle events by setting the `elementHook`\ncapability to `false`.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:16"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@ember/template-compiler/lib/plugins/allowed-globals.ts:1"
+      "message": "Missing item type\nWhether a component's template is static across all instances of that\ncomponent, or can vary per instance. This should usually be `false` except\nfor cases of backwards-compatibility.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:31"
     },
     {
-      "message": "Missing item type\nThe variable name used to inject the keywords object into the\ntemplate's evaluation scope. auto-import-builtins rewrites bare\nkeyword references (e.g. `on`) to property accesses on this\nvariable (e.g. `__ember_keywords__.on`).",
-      "line": " packages/@ember/template-compiler/lib/compile-options.ts:31"
+      "message": "Missing item type\nWhether a \"wrapped\" component's root element can change after being\nrendered. This flag is only used by the WrappedBuilder and should be\n`false` except for cases of backwards-compatibility.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:38"
     },
     {
-      "message": "Missing item type\nAll possible options passed to `template()` may specify a `moduleName`.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:11"
+      "message": "Missing item type\nSetting the `prepareArgs` flag to true enables the `prepareArgs` hook on\nthe component manager, which would otherwise not be called.\n\nThe component manager's `prepareArgs` hook allows it to programmatically\nadd or remove positional and named arguments for a component before the\ncomponent is invoked. This flag should usually be `false` except for cases\nof backwards-compatibility.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:47"
     },
     {
-      "message": "Missing item type\nWhether the template should be treated as a strict-mode template. Defaults\nto `true`.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:16"
+      "message": "Missing item type\nWhether a reified `Arguments` object will get passed to the component\nmanager's `create` hook. If a particular component does not access passed\narguments from JavaScript (via the `this.args` property in Glimmer.js, for\nexample), this flag can be set to `false` to avoid the work of\ninstantiating extra data structures to expose the arguments to JavaScript.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:58"
     },
     {
-      "message": "Missing item type\nWhen using `template` in a class, you call it in a `static` block and pass\nthe class as the `component` option.\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      // explicit or implicit option goes here\n    );\n  }\n}\n```\n\nFor the full explicit form, see {@linkcode ExplicitClassOptions}. For the\nfull implicit form, see {@linkcode ImplicitClassOptions}.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:23"
+      "message": "Missing item type\nWhether the component needs the caller component",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:67"
     },
     {
-      "message": "Missing item type\nWhen using `template` outside of a class (i.e. a \"template-only component\"), you can pass\na `scope` option that explicitly provides the lexical scope for the template.\n\nThis is called the \"explicit form\".\n\n```ts\nconst greeting = 'Hello';\nconst HelloWorld = template('{{greeting}} World!', { scope: () => ({ greeting }) });\n```",
-      "line": " packages/@ember/template-compiler/lib/template.ts:45"
+      "message": "Missing item type\nWhether to call the `didSplatAttributes` hook on the component manager.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:72"
     },
     {
-      "message": "Missing item type\nWhen using `template` *inside* a class (see\n{@linkcode BaseClassTemplateOptions}), you can pass a `scope` option that\nexplicitly provides the lexical scope for the template, just like a template-only\ncomponent (see {@linkcode ExplicitTemplateOnlyOptions}).\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      // explicit or implicit option goes here\n    );\n  }\n}\n```\n\n## The Scope Function's `instance` Parameter\n\nHowever, the explicit `scope` function in a *class* also takes an `instance` option\nthat provides access to the component's instance.\n\nOnce it's supported in Handlebars, this will make it possible to represent private\nfields when using the explicit form.\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.#greeting}}, {{@place}}!',\n      { component: this },\n      scope: (instance) => ({ '#greeting': instance.#greeting }),\n    );\n  }\n}\n```",
-      "line": " packages/@ember/template-compiler/lib/template.ts:60"
+      "message": "Missing item type\nWhether to call the `didCreateElement` hook on the component manager.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:77"
     },
     {
-      "message": "Missing item type\nThe *implicit* form of the `template` function takes an `eval` option that\nallows the runtime compiler to evaluate local template variables without\nneeding to maintain an explicit list of the local variables used in the\ntemplate scope.\n\nThe eval options *must* be passed in the following form:\n\n```ts\n{\n  eval() { return eval(arguments[0]) }\n}\n```\n\n## Requirements of the `eval` Option\n\n**The syntactic form presented above is the only form you should use when\npassing an `eval` option.**\n\nThis is _required_ if you want your code to be compatible with the\ncompile-time implementation of `@ember/template-compiler`. While the runtime\ncompiler offers a tiny bit of additional wiggle room, you still need to follow\nvery strict rules.\n\nWe don't recommend trying to memorize the rules. Instead, we recommend using\nthe snippet presented above and supported by the compile-time implementation.\n\n### The Technical Requirements of the `eval` Option\n\nThe `eval` function is passed a single parameter that is a JavaScript\nidentifier. This will be extended in the future to support private fields.\n\nSince keywords in JavaScript are contextual (e.g. `await` and `yield`), the\nparameter might be a keyword. The `@ember/template-compiler/runtime` expects\nthe function to throw a `SyntaxError` if the identifier name is not valid in\nthe current scope. (The direct `eval` function takes care of this out of the\nbox.)\n\nRequirements:\n\n1. The `eval` method must receive its parameter as `arguments[0]`, which\n   ensures that the variable name passed to `eval()` is not shadowed by the\n   function's parameter name.\n2. The `eval` option must be a function or concise method, and not an arrow.\n   This is because arrows do not have their own `arguments`, which breaks\n   (1).\n3. The `eval` method must call \"*direct* `eval`\", and not an alias of `eval`.\n   Direct `eval` evaluates the code in the scope it was called from, while\n   aliased versions of `eval` (including `new Function`) evaluate the code in\n   the global scope.\n4. The `eval` method must return the result of calling \"direct `eval`\".\n\nThe easiest way to achieve these requirements is to use the exact syntax\npresented above. This is *also* the only way to be compatible\n\n## Rationale\n\nThis is useful for two reasons:\n\n1. This form is a useful _intermediate_ form for the compile-time toolchain.\n   It allows the content-tag preprocessor to convert the `<template>` syntax\n   into valid JavaScript without needing to involve full-fledged lexical\n   analysis.\n2. This form is a convenient form for manual prototyping when using the\n   runtime compiler directly. While it requires some extra typing relative to\n   `<template>`, it's a mechanical 1:1 transformation of the syntax.\n\nIn practice, implementations that use a runtime compiler (for example, a\nplayground running completely in the browser) should probably use the\n`content-tag` preprocessor to convert the template into the implicit form,\nand then rely on `@ember/template-compiler/runtime` to evaluate the template.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:102"
+      "message": "Missing item type\nWhether the component manager has an update hook.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:82"
     },
     {
-      "message": "Missing item type\nWhen using `template` outside of a class (i.e. a \"template-only component\"), you can pass\nan `eval` option that _implicitly_ provides the lexical scope for the template.\n\nThis is called the \"implicit form\".\n\n```ts\nconst greeting = 'Hello';\nconst HelloWorld = template('{{greeting}} World!', {\n  eval() { return arguments[0] }\n});\n```\n\nFor more details on the requirements of the `eval` option, see {@linkcode ImplicitEvalOption}.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:182"
+      "message": "Missing item type\nWhether the component needs an additional dynamic scope frame.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:87"
     },
     {
-      "message": "Missing item type\nWhen using `template` inside of a class, you can pass an `eval` option that\n_implicitly_ provides the lexical scope for the template, just as you can\nwith a {@linkcode ImplicitTemplateOnlyOptions | template-only component}.\n\nThis is called the \"implicit form\".\n\n```ts\nclass MyComponent extends Component {\n  static {\n    template('{{this.greeting}}, {{@place}}!',\n      { component: this },\n      eval() { return arguments[0] }\n    );\n  }\n}\n```\n\n## Note  on Private Fields\n\nThe current implementation of `@ember/template-compiler` does not support\nprivate fields, but once the Handlebars parser adds support for private field\nsyntax and it's implemented in the Glimmer compiler, the implicit form should\nbe able to support them.",
-      "line": " packages/@ember/template-compiler/lib/template.ts:199"
+      "message": "Missing item type\nWhether there is a component instance to create. If this is false,\nthe component is a \"template only component\"",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:92"
     },
     {
-      "message": "Missing item type\nBuilds the source wireformat JSON block",
-      "line": " packages/@ember/template-compiler/lib/template.ts:256"
+      "message": "Missing item type\nWhether or not the component has a `willDestroy` hook that should fire\nprior to the component being removed from the DOM.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:98"
     },
     {
-      "message": "Missing item type\nExists for historical reasons, should not be in new code, as\nthe module name does not correspond to anything meaningful at runtime.",
-      "line": " packages/@ember/template-compiler/lib/types.ts:31"
+      "message": "Missing item type\nWhether or not the component pushes an owner onto the owner stack. This is\nused for engines.",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:104"
     },
     {
-      "message": "Missing item type\nNot available at runtime",
-      "line": " packages/@ember/template-compiler/lib/types.ts:37"
+      "message": "Missing item type\nEnum used for bit flags version of the capabilities, used once the component\nhas been loaded for the first time",
+      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:111"
     },
     {
-      "message": "Missing item type\nUtils unique to the runtime compiler",
-      "line": " packages/@ember/template-compiler/lib/types.ts:42"
+      "message": "Missing item type\nAll parts of `DebugVmState` are _snapshots_. They will not change if the piece of VM state that\nthey reference changes.",
+      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:40"
     },
     {
-      "message": "Missing item type\nThis supports template blocks defined in class bodies.\n\nManual form:\n\n```ts\nclass MyComponent {\n  static {\n    template(templateContent, {\n      component: this,\n      eval: () => eval(arguments[0])\n    })\n  }\n}\n```\n\nGJS form (compiled to the manual form via `content-tag`):\n\n```ts\nclass MyComponent {\n  <template>Template Content</template>\n}\n```",
-      "line": " packages/@ember/template-compiler/lib/types.ts:50"
+      "message": "Missing item type\nThese values are the same for the entire program",
+      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:45"
     },
     {
-      "message": "Missing item type\nDifferences:\n\n- strict mode variables always refer to in-scope variables\n- loose mode variables use this algorithm:\n  1. otherwise, fall back to `this.<name>`",
-      "line": " packages/@glimmer/compiler/lib/builder/builder-interface.ts:70"
+      "message": "Missing item type\nThese values can change for each opcode. You can get a snapshot a specific stack by calling\n`stacks.<name>.snapshot()`.",
+      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:50"
     },
     {
-      "message": "Missing item type\nThe special value 'splat' is used to indicate that the attribute is a splat",
-      "line": " packages/@glimmer/compiler/lib/builder/builder-interface.ts:588"
+      "message": "Missing item type\nA single program can mix and match multiple owners. This can happen component is curried from a\ntemplate with one owner and then rendered in a second owner.\n\nNote: Owners can change when new root scopes are created (including when rendering a\ncomponent), but not in child scopes.",
+      "line": " packages/@glimmer/interfaces/lib/runtime/scope.d.ts:14"
     },
     {
-      "message": "Missing item type\nA \"generic\" keyword is something like `has-block`, which makes sense in the context\nof sub-expression or append",
-      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts:108"
+      "message": "Missing item type\nRegisters\n\nFor the most part, these follows MIPS naming conventions, however the\nregister numbers are different.",
+      "line": " packages/@glimmer/interfaces/lib/runtime/vm-state.d.ts:13"
     },
     {
-      "message": "Missing item type\nThis function builds keyword definitions for a particular type of AST node (`KeywordType`).\n\nYou can build keyword definitions for:\n\n- `Expr`: A `SubExpression` or `PathExpression`\n- `Block`: A `BlockStatement`\n  - A `BlockStatement` is a keyword candidate if its head is a\n    `PathExpression`\n- `Append`: An `AppendStatement`\n\nA node is a keyword candidate if:\n\n- A `PathExpression` is a keyword candidate if it has no tail, and its\n  head expression is a `LocalVarHead` or `FreeVarHead` whose name is\n  the keyword's name.\n- A `SubExpression`, `AppendStatement`, or `BlockStatement` is a keyword\n  candidate if its head is a keyword candidate.\n\nThe keyword infrastructure guarantees that:\n\n- If a node is not a keyword candidate, it is never passed to any keyword's\n  `assert` method.\n- If a node is not the `KeywordType` for a particular keyword, it will not\n  be passed to the keyword's `assert` method.\n\n`Expr` keywords are used in expression positions and should return HIR\nexpressions. `Block` and `Append` keywords are used in statement\npositions and should return HIR statements.\n\nA keyword definition has two parts:\n\n- `match`, which determines whether an AST node matches the keyword, and can\n  optionally return some information extracted from the AST node.\n- `translate`, which takes a matching AST node as well as the extracted\n  information and returns an appropriate HIR instruction.\n\n# Example\n\nThis keyword:\n\n- turns `(hello)` into `\"hello\"`\n  - as long as `hello` is not in scope\n- makes it an error to pass any arguments (such as `(hello world)`)\n\n```ts\nkeywords('SubExpr').kw('hello', {\n  assert(node: ExprKeywordNode): Result<void> | false {\n    // we don't want to transform `hello` as a `PathExpression`\n    if (node.type !== 'SubExpression') {\n      return false;\n    }\n\n    // node.head would be `LocalVarHead` if `hello` was in scope\n    if (node.head.type !== 'FreeVarHead') {\n      return false;\n    }\n\n    if (node.params.length || node.hash) {\n      return Err(generateSyntaxError(`(hello) does not take any arguments`), node.loc);\n    } else {\n      return Ok();\n    }\n  },\n\n  translate(node: ASTv2.SubExpression): hir.Expression {\n    return ASTv2.builders.literal(\"hello\", node.loc)\n  }\n})\n```\n\nThe keyword infrastructure checks to make sure that the node is the right\ntype before calling `assert`, so you only need to consider `SubExpression`\nand `PathExpression` here. It also checks to make sure that the node passed\nto `assert` has the keyword name in the right place.\n\nNote the important difference between returning `false` from `assert`,\nwhich just means that the node didn't match, and returning `Err`, which\nmeans that the node matched, but there was a keyword-specific syntax\nerror.",
-      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/keywords/impl.ts:227"
+      "message": "Missing item type\nA special version of `Optional` that is used for values that are expected to be initialized. This\ndocuments the intent that the value will be initialized before it is used, and therefore that\nnull assertions or `?.` are not appropriate.",
+      "line": " packages/@glimmer/interfaces/lib/core.d.ts:7"
     },
     {
-      "message": "Missing item type\nNormalize paths into `hir.Path` or a `hir.Expr` that corresponds to the ref.\n\nTODO since keywords don't support tails anyway, distinguish PathExpression from\nVariableReference in ASTv2.",
-      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/visitors/expressions.ts:51"
+      "message": "Missing item type\nA type that has an index signature, but nothing else is know about it. Useful in generic code\nthat needs to index into an opaque, user-specified object.",
+      "line": " packages/@glimmer/interfaces/lib/core.d.ts:16"
     },
     {
-      "message": "Missing item type\nThis is the mutable state for this compiler pass.",
-      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/context.ts:10"
+      "message": "Missing item type\nThis is needed because the normal IteratorResult in the TypeScript\nstandard library is generic over the value in each tick and not over\nthe return value. It represents a standard ECMAScript IteratorResult.",
+      "line": " packages/@glimmer/interfaces/lib/core.d.ts:33"
     },
     {
-      "message": "Missing item type\nNormalize the AST from @glimmer/syntax into the HIR. The HIR has special\ninstructions for keywords like `{{yield}}`, `(has-block)` and\n`{{#in-element}}`.\n\nMost importantly, it also classifies HTML element syntax into:\n\n1. simple HTML element (with optional splattributes)\n2. component invocation\n\nBecause the @glimmer/syntax AST gives us a string for an element's tag,\nthis pass also normalizes that string into an expression.\n\n```\n// normalized into a path expression whose head is `this` and tail is\n// `[\"x\"]`\n<this.x />\n\n{{#let expr as |t|}}\n  // `\"t\"` is normalized into a variable lookup.\n  <t />\n\n  // normalized into a path expression whose head is the variable lookup\n  // `t` and tail is `[\"input\"]`.\n  <t.input />\n{{/let}}\n\n// normalized into a free variable lookup for `SomeComponent` (with the\n// context `ComponentHead`).\n<SomeComponent />\n\n// normalized into a path expression whose head is the free variable\n// `notInScope` (with the context `Expression`), and whose tail is\n// `[\"SomeComponent\"]`. In resolver mode, this path will be rejected later,\n// since it cannot serve as an input to the resolver.\n<notInScope.SomeComponent />\n```",
-      "line": " packages/@glimmer/compiler/lib/passes/1-normalization/index.ts:17"
+      "message": "Missing item type\nReturn the number of entries in the table. A handle is legal if\nit is less than this number.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:42"
     },
     {
-      "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"
+      "message": "Missing item type\nThe `EvaluationContext` is the context that remains the same across all of the templates and\nevaluations in a single program.\n\nNote that multiple programs can co-exist on the same page, sharing tracking logic (and the\nglobal tracking context) but having different *evaluation* contexts.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:51"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/component/src/-private/component.ts:56"
+      "message": "Missing item type\nThe program's environment, which contains customized framework behavior.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:59"
     },
     {
-      "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"
+      "message": "Missing item type\nThe compiled program itself: the constants and heap",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:63"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/component/src/-private/component.ts:97"
+      "message": "Missing item type\nThe offsets to stdlib functions",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:67"
     },
     {
-      "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"
+      "message": "Missing item type\nA framework-specified resolver for resolving free variables in classic templates.\n\nA strict component can invoke a classic component and vice versa, but only classic components\nwill use the resolver. If no resolver is available in the `ProgramContext`, only strict components\nwill compile and run.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:71"
     },
     {
-      "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"
+      "message": "Missing item type\nOptions for compiling a specific template. This carries\nalong the static information associated with the entire\ntemplate when compiling blocks nested inside of it.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:83"
     },
     {
-      "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"
+      "message": "Missing item type\nConstants are interned values that are referenced as numbers in the program.\nThe constant pool is a part of the program, and is always transmitted\ntogether with the program.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:98"
     },
     {
-      "message": "Missing item type\nCalled before the component has been removed from the DOM.",
-      "line": " packages/@glimmer/component/src/-private/component.ts:282"
+      "message": "Missing item type\nResolution happens when components are first loaded, either via the resolver\nor via looking them up in template scope.",
+      "line": " packages/@glimmer/interfaces/lib/program.d.ts:109"
     },
     {
-      "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/src/-private/ember-component-manager.ts:24"
+      "message": "Missing item type\nThis file describes the interface between compilation time\nand runtime.\n\n# Locators\n\nCompile time and runtime must share the same Locator. A Locator is an\nobject that describes the location of a template, and is roughly a\nmodule name. The compiler and runtime may use the Locator to locally\nresolve names relative to the template the name was found in, but must\nshare resolution rules between compilation time and runtime.\n\nFor example, given this template with Locator\n`{ module: 'components/Articles/Container' }:\n\n```\n<TabBar />\n```\n\nThe compiler may resolve `<TabBar>` to `components/Articles/TabBar`. The\nimportant thing is that the compiler and runtime share resolution rules.\n\n# CompileTimeLookup\n\nWhen compiling an application, the `CompileTimeLookup` is responsible\nfor resolving helpers, modifiers, and components into \"handles\"\n(numbers) that can be embedded into the program and used at runtime.\n\n# RuntimeResolver\n\nThe `RuntimeResolver` has two responsibilities.\n\n1. To turn handles created by the `CompileTimeLookup` into live helpers,\n   modifiers, and components.\n2. To resolve dynamic components at runtime that come from\n   calls to `{{component dynamic}}`.\n\nThe `CompileTimeLookup` and `RuntimeResolver` must maintain symmetry\nbetween:\n\n* `resolver.resolve(lookup.lookupComponentDefinition(name, referrer))`; and\n* `resolver.lookupComponentDefinition(name, referrer))`\n\n# Coupling\n\nIn practice, the `CompileTimeLookup` and `RuntimeResolver` are two parts\nof one system. The goal of this system is to allow the `CompileTimeLookup`\nto do as much resolution as possible ahead of time, while still allowing\nthe `RuntimeResolver` to do dynamic resolution when necessary.",
+      "line": " packages/@glimmer/interfaces/lib/serialize.d.ts:1"
     },
     {
-      "message": "Missing item type\nA dynamic operand has a value that can't be easily represented as an embedded string.",
-      "line": " packages/@glimmer/debug/lib/dism/dism.ts:43"
+      "message": "Missing item type\nFor debugging",
+      "line": " packages/@glimmer/interfaces/lib/stack.d.ts:13"
     },
     {
-      "message": "Missing item type\nA variable is a numeric offset into the stack (relative to the $fp register).",
-      "line": " packages/@glimmer/debug/lib/dism/dism.ts:63"
+      "message": "Missing item type\nThis union represents all of the possible tag types for the monomorphic tag class.\nOther custom tag classes can exist, such as CurrentTag and VolatileTag, but for\nperformance reasons, any type of tag that is meant to be used frequently should\nbe added to the monomorphic tag.",
+      "line": " packages/@glimmer/interfaces/lib/tags.d.ts:12"
     },
     {
-      "message": "Missing item type\nThe `LogFragmentBuffer` is responsible for collecting the fragments that are logged to the\n`DebugLogger` so that they can be accumulated during a group and flushed together.\n\nThis queuing serves two purposes:\n\n1. To allow the individual fragments that make up a single line to append their values to\n   the current line. To accomplish this, each fragment can append static content and its\n   formatting specifier (e.g. `%o`) to the accumulated {@link #template} *and* append the\n   value to format to the {@link #substitutions} array.\n2. To allow logs that refer to objects to be represented as footnotes in the current line,\n   with the footnote to be printed in a later line.\n\nThis allows a list of fragments, each of which represent formattable values, to be flattened\ninto a single template string and an array of values to format.\n\n## Footnotes\n\nAn opcode slice containing constant references will be logged like this:\n\n```\n...\n362. (PushArgs names=[] block-names=[] flags=16)\n366. (Helper helper=[0])\n[0] glimmerHelper()\n368. (PopFrame)\n369. (Fetch register=$v0)\n371. (Primitive constant=\"/index.html\")\n...\n```\n\nThe fragment for line `366` includes an `ObjectFragment` for the helper value. When logged,\nthe object will be represented as a footnote and the value will be printed in a later\nline.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:6"
+      "message": "Missing item type\nEnvironment specific template.",
+      "line": " packages/@glimmer/interfaces/lib/template.d.ts:30"
     },
     {
-      "message": "Missing item type\nThe first parameter to the `console.log` family of APIs is a *template* that can use\nformat specifiers (e.g. `%c`, `%o`, and `%O`) to refer to subsequent parameters.\n\nWhen a fragment is appended to a line,",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:42"
+      "message": "Missing item type\nModule name associated with the template, used for debugging purposes",
+      "line": " packages/@glimmer/interfaces/lib/template.d.ts:36"
     },
     {
-      "message": "Missing item type\nEach format specified in the {@link #template} corresponds to a value in the\n`#substitutions` array.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:50"
+      "message": "Missing item type\nhttps://astexplorer.net/#/gist/c3f41b75af73006f64476775e73f7daa/e6e3e120df8404b1bff308bec3ed89eaaf0b05f2\n\nThis plugin exists because, _even when we inline",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:1"
     },
     {
-      "message": "Missing item type\nThe logging options for the buffer, which currently only contains `showSubtle`.\n\nWhen fragments call the buffer's {@linkcode append} method, they specify whether the\ncontent to append is subtle or not. If the buffer is not configured to show subtle\ncontent, the content is not appended.\n\nThis allows fragments to append content to the buffer without having to know how the\nbuffer is configured.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:56"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:44"
     },
     {
-      "message": "Missing item type\nA single line can produce multiple queued log entries. This happens when fragments\nappend *footnotes* to the buffer. A *reference* to the footnote is appended to the\nprimary line, and a line containing the *value* of the footnote is appended to the\n`#queued` array.\n\nBoth the primary line and any queued footnotes are flushed together when the buffer\nis flushed.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:68"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:51"
     },
     {
-      "message": "Missing item type\nAdd a footnoted value to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.\n\nThis method takes two callbacks: `add` and `append`.\n\nThe `append` callback behaves like {@linkcode append}, but without the `subtle` argument. If\n`addFootnoted` is called with `subtle: false`, then the callback will never be called, so\nthere is no need to pass the `subtle` argument again.\n\nThe `add` callback is responsible for appending the footnote itself to the buffer. The first\nparameter to `add` (`useNumber`) specifies whether the caller has used the footnote number\nto refer to the footnote.\n\nThis is typically true, but fragments can specify an alternative annotation that should be used\ninstead of the default footnote number. In that case, the footnote number is not used, and the\nnext footnote is free to use it.\n\nThe `add` callback also takes a template string and an optional list of substitutions, which\ndescribe the way the footnote itself should be formatted.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:85"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:62"
     },
     {
-      "message": "Missing item type\nAppend a fragment to the current buffer.\n\nIf the `subtle` option is set, the fragment will only be printed if the buffer is configured\nto show subtle content.",
-      "line": " packages/@glimmer/debug/lib/render/buffer.ts:134"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:72"
     },
     {
-      "message": "Missing item type\nThe prepend function returns a subtle fragment if the contents are subtle.",
-      "line": " packages/@glimmer/debug/lib/render/combinators.ts:6"
+      "message": "Missing item type\nDo we want to support local aliasing / re-assignment?\nif so, this would break",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:82"
     },
     {
-      "message": "Missing item type\nThe append function returns a subtle fragment if the contents are subtle.",
-      "line": " packages/@glimmer/debug/lib/render/combinators.ts:13"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:92"
     },
     {
-      "message": "Missing item type\nThe `wrap` function returns a subtle fragment if the contents are subtle.",
-      "line": " packages/@glimmer/debug/lib/render/combinators.ts:19"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:114"
     },
     {
-      "message": "Missing item type\nA compact array makes the wrapping `[]` subtle if there's only one element.",
-      "line": " packages/@glimmer/debug/lib/render/combinators.ts:53"
+      "message": "Missing item type\nIf the specified flag is set as a boolean flag with no value, `true` is returned.\n\nOtherwise, this function returns true if the flag value is a pattern that matches `value`.\n\nThe pattern can have a `*`, which matches any number of characters.",
+      "line": " packages/@glimmer/local-debug-flags/index.ts:129"
     },
     {
-      "message": "Missing item type\nA Loggable is either:\n\n1. a single log line\n2. a log line as a header followed by a group of log entries",
-      "line": " packages/@glimmer/debug/lib/render/entry.ts:1"
+      "message": "Missing item type\nThere is also Reflect.getPrototypeOf,\nwhich errors when non-objects are passed.\n\nSince our conditional for figuring out whether to render primitives or not\nmay contain non-object values, we don't want to throw errors when we call this.",
+      "line": " packages/@glimmer/manager/lib/internal/api.ts:28"
     },
     {
-      "message": "Missing item type\nLogLine represents a single line in the log. The line is logged *either* by passing the `line`\nvalues to `console.{log,info,debug,warn,error}` *or* by passing them to `console.group` to\nrepresent the header of a group.",
-      "line": " packages/@glimmer/debug/lib/render/entry.ts:11"
+      "message": "Missing item type\nThe CustomComponentManager allows addons to provide custom component\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom component manager, which\nimplements a set of hooks that determine component behavior.\n\nTo create a custom component manager, instantiate a new CustomComponentManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomComponentManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a component, the component manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n\n* `create()` - invoked when a new instance of a component should be created\n* `update()` - invoked when the arguments passed to a component change\n* `getContext()` - returns the object that should be",
+      "line": " packages/@glimmer/manager/lib/public/component.ts:85"
     },
     {
-      "message": "Missing item type\nLogGroup represents a group of log entries. It is logged by calling *either* `console.group` or\n`console.groupCollapsed` (depending on the value of `collapsed`).",
-      "line": " packages/@glimmer/debug/lib/render/entry.ts:21"
+      "message": "Missing item type\nStores internal state about a component instance after it's been created.",
+      "line": " packages/@glimmer/manager/lib/public/component.ts:208"
     },
     {
-      "message": "Missing item type\nA leaf fragment that represents an arbitrary value.\n\nWhen the value is a primitive, the fragment is appended to the buffer as if it was an instance of\nthe appropriate leaf fragment type (e.g. strings are appended as if they were `StringFragment`).\n\nOtherwise, `ValueFragment` is appended to the current line as a footnote reference and the value\nitself is appended to a later line that *defines* the footnote using the `%O` format specifier.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:19"
+      "message": "Missing item type\nThe CustomModifierManager allows addons to provide custom modifier\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom modifier manager, which\nimplements a set of hooks that determine modifier behavior.\nTo create a custom modifier manager, instantiate a new CustomModifierManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomModifierManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a modifier, the modifier manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n* `createModifier()` - invoked when a new instance of a modifier should be created\n* `installModifier()` - invoked when the modifier is installed on the element\n* `updateModifier()` - invoked when the arguments passed to a modifier change\n* `destroyModifier()` - invoked when the modifier is about to be destroyed",
+      "line": " packages/@glimmer/manager/lib/public/modifier.ts:50"
     },
     {
-      "message": "Missing item type\nThe `ValueFragment` is appended to the current line as a footnote reference (e.g. `[1]`) and\nthe value itself is appended to a later line that *defines* the footnote (e.g. `[1]\nObjectHere`).\n\nBy default, the footnote reference is an incrementing number per log line, and the footnote\nvalue is formatted using the `%O` format specifier.\n\nThe `display` property can be provided to override these defaults.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:32"
+      "message": "Missing item type\nConverts a ComponentCapabilities object into a 32-bit integer representation.",
+      "line": " packages/@glimmer/manager/lib/util/capabilities.ts:48"
     },
     {
-      "message": "Missing item type\nA leaf fragment that represents a string value.\n\nCorresponds to the `%s` format specifier.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:48"
+      "message": "Missing item type\nYield to a block located at a particular symbol location.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:28"
     },
     {
-      "message": "Missing item type\nA leaf fragment that represents an integer value.\n\nCorresponds to the `%d` format specifier.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:58"
+      "message": "Missing item type\nPush an (optional) yieldable block onto the stack. The yieldable block must be known\nstatically at compile time.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:48"
     },
     {
-      "message": "Missing item type\nA leaf fragment that represents a float value.\n\nCorresponds to the `%f` format specifier.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:68"
+      "message": "Missing item type\nInvoke a block that is known statically at compile time.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:63"
     },
     {
-      "message": "Missing item type\nA leaf fragment that represents a DOM node.\n\nCorresponds to the `%o` format specifier.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:78"
+      "message": "Missing item type\nInvoke a static block, preserving some number of stack entries for use in\nupdating.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:79"
     },
     {
-      "message": "Missing item type\nThe list of leaf fragment types correspond exactly to the list of console.log\nformat specifiers.",
-      "line": " packages/@glimmer/debug/lib/render/fragment-type.ts:88"
+      "message": "Missing item type\nA convenience for pushing some arguments on the stack and\nrunning some code if the code needs to be re-executed during\nupdating execution if some of the arguments have changed.\n\n# Initial Execution\n\nThe `args` function should push zero or more arguments onto\nthe stack and return the number of arguments pushed.\n\nThe `body` function provides the instructions to execute both\nduring initial execution and during updating execution.\n\nInternally, this function starts by pushing a new frame, so\nthat the body can return and sets the return point ($ra) to\nthe ENDINITIAL label.\n\nIt then executes the `args` function, which adds instructions\nresponsible for pushing the arguments for the block to the\nstack. These arguments will be restored to the stack before\nupdating execution.\n\nNext, it adds the Enter opcode, which marks the current position\nin the DOM, and remembers the current $pc (the next instruction)\nas the first instruction to execute during updating execution.\n\nNext, it runs `body`, which adds the opcodes that should\nexecute both during initial execution and during updating execution.\nIf the `body` wishes to finish early, it should Jump to the\n`FINALLY` label.\n\nNext, it adds the FINALLY label, followed by:\n\n- the Exit opcode, which finalizes the marked DOM started by the\n  Enter opcode.\n- the Return opcode, which returns to the current return point\n  ($ra).\n\nFinally, it adds the ENDINITIAL label followed by the PopFrame\ninstruction, which restores $fp, $sp and $ra.\n\n# Updating Execution\n\nUpdating execution for this `replayable` occurs if the `body` added an\nassertion, via one of the `JumpIf`, `JumpUnless` or `AssertSame` opcodes.\n\nIf, during updating executon, the assertion fails, the initial VM is\nrestored, and the stored arguments are pushed onto the stack. The DOM\nbetween the starting and ending markers is cleared, and the VM's cursor\nis set to the area just cleared.\n\nThe return point ($ra) is set to -1, the exit instruction.\n\nFinally, the $pc is set to to the instruction saved off by the\nEnter opcode during initial execution, and execution proceeds as\nusual.\n\nThe only difference is that when a `Return` instruction is\nencountered, the program jumps to -1 rather than the END label,\nand the PopFrame opcode is not needed.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts:73"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:21"
+      "message": "Missing item type\nA specialized version of the `replayable` convenience that allows the\ncaller to provide different code based upon whether the item at\nthe top of the stack is true or false.\n\nAs in `replayable`, the `ifTrue` and `ifFalse` code can invoke `return`.\n\nDuring the initial execution, a `return` will continue execution\nin the cleanup code, which finalizes the current DOM block and pops\nthe current frame.\n\nDuring the updating execution, a `return` will exit the updating\nroutine, as it can reuse the DOM block and is always only a single\nframe deep.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts:187"
     },
     {
-      "message": "Missing item type\nFragment is the most fundamental building block of the debug logger.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:25"
+      "message": "Missing item type\n<Foo/>\n<Foo></Foo>\n<Foo @arg={{true}} />",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:78"
     },
     {
-      "message": "Missing item type\nA subtle fragment is only printed if the `showSubtle` option is set.\n\nReturns true if this fragment is a subtle leaf or is a multi fragment\nwith all subtle leaves.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:68"
+      "message": "Missing item type\n(helper)\n(helper arg)",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:144"
     },
     {
-      "message": "Missing item type\nIf the current fragment is not empty, apply `ifPresent` to the current\nfragment. Otherwise, do nothing.\n\nIf the current fragment is subtle, the result is also subtle.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:78"
+      "message": "Missing item type\n<div {{modifier}}/>\n<div {{modifier arg}}/>\n<Foo {{modifier}}/>",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:191"
     },
     {
-      "message": "Missing item type\nA fragment is empty if it should not be printed with the provided display options.\n\nThis means that if a fragment is subtle and `showSubtle` is false, the fragment is empty.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:90"
+      "message": "Missing item type\n{{component-or-helper arg}}",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:254"
     },
     {
-      "message": "Missing item type\nReturns an array of {@linkcode LeafFragment}s that make up the current\nfragment.\n\nThis effectively flattens any number of nested multi-fragments into a flat array of leaf\nfragments.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:99"
+      "message": "Missing item type\n{{maybeHelperOrComponent}}",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:344"
     },
     {
-      "message": "Missing item type\nReturns a fragment with the specified subtle status without mutating the current fragment.\n\nIf `isSubtle` is true, the fragment will also be styled with the `subtle` style.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:116"
+      "message": "Missing item type\nCompile arguments, pushing an Arguments object onto the stack.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/shared.ts:16"
     },
     {
-      "message": "Missing item type\nApply the specified styles to the current fragment (if it's a leaf) or all\nof its children (if it's a multi-fragment).\n\nKeep in mind that merging styles might be very difficult to undo, so treat\nthis as a low-level operation, and prefer to use higher-level concepts like\n`subtle` if you can instead.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:144"
+      "message": "Missing item type\nCompile an optional list of positional arguments, which pushes each argument\nonto the stack and returns the number of parameters compiled",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/shared.ts:89"
     },
     {
-      "message": "Missing item type\nConvert the current fragment into a string with no additional formatting.\nThe primary purpose for this method is to support converting a fragment\ninto a string for inclusion in thrown Errors. If you're going to *log*\na fragment, log it using `DebugLogger` and don't convert it to\na string first.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:168"
+      "message": "Missing item type\nAppend content to the DOM. This standard function triages content and does the\nright thing based upon whether it's a string, safe string, component, fragment\nor node.",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/stdlib.ts:31"
     },
     {
-      "message": "Missing item type\nShould the current fragment be printed with the provided display options?\n\nImportantly, if the current fragment contains subtle content but the `showSubtle` option is\nfalse, `#shouldShow` will return false.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:191"
+      "message": "Missing item type\nPush a reference onto the stack corresponding to a statically known primitive",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:34"
     },
     {
-      "message": "Missing item type\nConvert this fragment into a Loggable for logging through the `DebugLogger`.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:213"
+      "message": "Missing item type\nPush an encoded representation of a JavaScript primitive on the stack",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:43"
     },
     {
-      "message": "Missing item type\nAppend this fragment to the low-level `LogFragmentBuffer`.",
-      "line": " packages/@glimmer/debug/lib/render/fragment.ts:226"
+      "message": "Missing item type\nInvoke a foreign function (a \"helper\") based on a statically known handle",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:58"
     },
     {
-      "message": "Missing item type\nA dynamic operand has a value that can't be easily represented as an embedded string.",
-      "line": " packages/@glimmer/debug/lib/debug.ts:235"
+      "message": "Missing item type\nInvoke a foreign function (a \"helper\") based on a dynamically loaded definition",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:79"
     },
     {
-      "message": "Missing item type\nA variable is a numeric offset into the stack (relative to the $fp register).",
-      "line": " packages/@glimmer/debug/lib/debug.ts:255"
+      "message": "Missing item type\nEvaluate statements in the context of new dynamic scope entries. Move entries from the\nstack into named entries in the dynamic scope, then evaluate the statements, then pop\nthe dynamic scope",
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:108"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/debug/lib/metadata.ts:34"
+      "message": "Missing item type\nWraps a template js in a template module to change it into a factory\nthat handles lazy parsing the template and to create per env singletons\nof the template.",
+      "line": " packages/@glimmer/opcode-compiler/lib/template.ts:39"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/debug/lib/metadata.ts:36"
+      "message": "Missing item type\nFramework objects in a Glimmer application may receive an owner object.\nGlimmer is unopinionated about this owner, but will forward it through its\ninternal resolution system, and through its managers if it is provided.",
+      "line": " packages/@glimmer/owner/index.ts:8"
     },
     {
-      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\nFF\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
-      "line": " packages/@glimmer/debug-util/lib/assert.ts:19"
+      "message": "Missing item type\n`setOwner` set's an object's owner",
+      "line": " packages/@glimmer/owner/index.ts:17"
     },
     {
-      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
-      "line": " packages/@glimmer/debug-util/lib/assert.ts:29"
+      "message": "Missing item type\nDefault component template, which is a plain yield",
+      "line": " packages/@glimmer/program/lib/util/default-template.ts:4"
     },
     {
-      "message": "Missing item type\nAn object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function does nothing (and is removed\nby the minifier in builder).",
-      "line": " packages/@glimmer/debug-util/lib/debug-brand.ts:15"
+      "message": "Missing item type\nThe Program Heap is responsible for dynamically allocating\nmemory in which we read/write the VM's instructions\nfrom/to. When we malloc we pass out a VMHandle, which\nis used as an indirect way of accessing the memory during\nexecution of the VM. Internally we track the different\nregions of the memory in an int array known as the table.\n\nThe table 32-bit aligned and has the following layout:\n\n| ... | hp (u32) |       info (u32)   | size (u32) |\n| ... |  Handle  | Scope Size | State | Size       |\n| ... | 32bits   | 30bits     | 2bits | 32bit      |\n\nWith this information we effectively have the ability to\ncontrol when we want to free memory. That being said you\ncan not free during execution as raw address are only\nvalid during the execution. This means you cannot close\nover them as you will have a bad memory access exception.",
+      "line": " packages/@glimmer/program/lib/program.ts:20"
     },
     {
-      "message": "Missing item type\nAn object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function always returns undefined. However,\nthis function should only be called by the trace logger, which should only\nrun in trace `LOCAL_DEBUG` + `LOCAL_TRACE_LOGGING` mode.",
-      "line": " packages/@glimmer/debug-util/lib/debug-brand.ts:38"
+      "message": "Missing item type\nThe heap uses the [Mark-Compact Algorithm](https://en.wikipedia.org/wiki/Mark-compact_algorithm) to shift\nreachable memory to the bottom of the heap and freeable\nmemory to the top of the heap. When we have shifted all\nthe reachable memory to the top of the heap, we move the\noffset to the next free position.",
+      "line": " packages/@glimmer/program/lib/program.ts:122"
     },
     {
-      "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\nWhen iterating over a list, it's possible that an item with the same unique\nkey could be encountered twice:\n\n```js\nlet arr = ['same', 'different', 'same', 'same'];\n```\n\nIn general, we want to treat these items as _unique within the list_. To do\nthis, we track the occurences of every item as we iterate the list, and when\nan item occurs more than once, we generate a new unique key just for that\nitem, and that occurence within the list. The next time we iterate the list,\nand encounter an item for the nth time, we can get the _same_ key, and let\nGlimmer know that it should reuse the DOM for the previous nth occurence.",
+      "line": " packages/@glimmer/reference/lib/iterable.ts:135"
     },
     {
-      "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"
+      "message": "Missing item type\nThe VM creates a new ComponentInstance data structure for every component\ninvocation it encounters.\n\nSimilar to how a ComponentDefinition contains state about all components of a\nparticular type, a ComponentInstance contains state specific to a particular\ninstance of a component type. It also contains a pointer back to its\ncomponent type's ComponentDefinition.",
+      "line": " packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:107"
     },
     {
-      "message": "Missing item type\nInterfaces\n\nTODO: Move these into @glimmer/interfaces, move @glimmer/interfaces to",
-      "line": " packages/@glimmer/global-context/index.ts:21"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/component/interfaces.ts:8"
     },
     {
-      "message": "Missing item type\nSchedules a VM revalidation.\n\nNote: this has a default value so that tags can warm themselves when first loaded.",
-      "line": " packages/@glimmer/global-context/index.ts:37"
+      "message": "Missing item type\nPerforms a strict equality comparison.\n\nleft === right",
+      "line": " packages/@glimmer/runtime/lib/helpers/eq.ts:3"
     },
     {
-      "message": "Missing item type\nSchedules a destructor to run",
-      "line": " packages/@glimmer/global-context/index.ts:44"
+      "message": "Missing item type\nPerforms a greater than comparison.\n\nleft > right",
+      "line": " packages/@glimmer/runtime/lib/helpers/gt.ts:3"
     },
     {
-      "message": "Missing item type\nFinalizes destruction",
-      "line": " packages/@glimmer/global-context/index.ts:55"
+      "message": "Missing item type\nPerforms a greater than or equal comparison.\n\nleft >= right",
+      "line": " packages/@glimmer/runtime/lib/helpers/gte.ts:3"
     },
     {
-      "message": "Missing item type\nHook to provide iterators for `{{each}}` loops",
-      "line": " packages/@glimmer/global-context/index.ts:62"
+      "message": "Missing item type\nPerforms a less than comparison.\n\nleft < right",
+      "line": " packages/@glimmer/runtime/lib/helpers/lt.ts:3"
     },
     {
-      "message": "Missing item type\nHook to specify truthiness within Glimmer templates",
-      "line": " packages/@glimmer/global-context/index.ts:69"
+      "message": "Missing item type\nPerforms a less than or equal comparison.\n\nleft <= right",
+      "line": " packages/@glimmer/runtime/lib/helpers/lte.ts:3"
     },
     {
-      "message": "Missing item type\nHook for specifying how Glimmer should access properties in cases where it\nneeds to. For instance, accessing an object's values in templates.",
-      "line": " packages/@glimmer/global-context/index.ts:76"
+      "message": "Missing item type\nPerforms a strict inequality comparison.\n\nleft !== right",
+      "line": " packages/@glimmer/runtime/lib/helpers/neq.ts:3"
     },
     {
-      "message": "Missing item type\nHook for specifying how Glimmer should update props in cases where it needs\nto. For instance, when updating a template reference (e.g. 2-way-binding)",
-      "line": " packages/@glimmer/global-context/index.ts:85"
+      "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"
     },
     {
-      "message": "Missing item type\nHook for specifying how Glimmer should access paths in cases where it needs\nto. For instance, the `key` value of `{{each}}` loops.",
-      "line": " packages/@glimmer/global-context/index.ts:95"
+      "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"
     },
     {
-      "message": "Missing item type\nHook for specifying how Glimmer should update paths in cases where it needs\nto. For instance, when updating a template reference (e.g. 2-way-binding)",
-      "line": " packages/@glimmer/global-context/index.ts:104"
+      "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"
     },
     {
-      "message": "Missing item type\nHook to warn if a style binding string or value was not marked as trusted\n(e.g. HTMLSafe)",
-      "line": " packages/@glimmer/global-context/index.ts:113"
+      "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"
     },
     {
-      "message": "Missing item type\nHook to customize assertion messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
-      "line": " packages/@glimmer/global-context/index.ts:119"
+      "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"
     },
     {
-      "message": "Missing item type\nHook to customize deprecation messages in the VM. Usages can be stripped out\nby using the @glimmer/vm-babel-plugins package.",
-      "line": " packages/@glimmer/global-context/index.ts:135"
+      "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"
     },
     {
-      "message": "Missing item type\nA Handlebars statement",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:303"
+      "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"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:344"
+      "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"
     },
     {
-      "message": "Missing item type\nA JSON object that the Block was serialized into.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:362"
+      "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"
     },
     {
-      "message": "Missing item type\nA JSON object that the compiled TemplateBlock was serialized into.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:369"
+      "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"
     },
     {
-      "message": "Missing item type\nA JSON object that the compiled Template was serialized into.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:378"
+      "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"
     },
     {
-      "message": "Missing item type\nA string of JSON containing a SerializedTemplateBlock",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:387"
+      "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"
     },
     {
-      "message": "Missing item type\nA JSON object containing the SerializedTemplateBlock as JSON and TemplateMeta.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:392"
+      "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"
     },
     {
-      "message": "Missing item type\nA string of Javascript containing a SerializedTemplateWithLazyBlock to be\nconcatenated into a Javascript module.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/api.d.ts:403"
+      "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"
     },
     {
-      "message": "Missing item type\nA VariableResolutionContext explains how a variable name should be resolved.",
-      "line": " packages/@glimmer/interfaces/lib/compile/wire-format/resolution.d.ts:1"
+      "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"
     },
     {
-      "message": "Missing item type\nThe Encoder receives a stream of opcodes from the syntax compiler and turns\nthem into a binary program.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:134"
+      "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"
     },
     {
-      "message": "Missing item type\nFinalize the current compilation unit, add a `(Return)`, and push the opcodes from\nthe buffer into the program. At this point, some of the opcodes might still be\nplaceholders, such as in the case of recursively compiled templates.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:139"
+      "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"
     },
     {
-      "message": "Missing item type\nPush a syscall into the program with up to three optional\noperands.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:149"
+      "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"
     },
     {
-      "message": "Missing item type\nStart a new labels block. A labels block is a scope for labels that\ncan be referred to before they are declared. For example, when compiling\nan `if`, the `JumpUnless` opcode occurs before the target label. To\naccommodate this use-case ergonomically, the `Encoder` allows a syntax\nto create a labels block and then refer to labels that have not yet\nbeen declared. Once the block is complete, a second pass replaces the\nlabel names with offsets.\n\nThe pattern is:\n\n```ts\nencoder.reserve(Op.JumpUnless);\nencoder.target(encoder.pos, 'ELSE');\n```\n\nThe `reserve` method creates a placeholder opcode with space for a target\nin the future, and the `target` method registers the blank operand position\nto be replaced with an offset to `ELSE`, once it's known.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:163"
+      "message": "Missing item type\n## State changes\n\n- [!] push Updating Stack",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
     },
     {
-      "message": "Missing item type\nFinish the current labels block and replace label names with offsets,\nnow that all of the offsets are known.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:185"
+      "message": "Missing item type\n## State changes\n\n[!] pop Updating Stack",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
     },
     {
-      "message": "Missing item type\nMark the current position with a label name. This label name\ncan be used by any other opcode in this label block.",
-      "line": " packages/@glimmer/interfaces/lib/compile/encoder.d.ts:191"
+      "message": "Missing item type\n## State changes\n\n[!] push Updating List",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
     },
     {
-      "message": "Missing item type\n`AppendingBlock` is the interface used by the `ElementBuilder` to keep track of which nodes have\nbeen appended to a block. Ultimately, an `AppendingBlock` is finalized and used as a `FixedBlock`\nor `ResettableBlock` during the updating phase.",
-      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:15"
+      "message": "Missing item type\n## State changes\n\n[-] associate destroyable `child`",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
     },
     {
-      "message": "Missing item type\nA `FixedBlock` is a block that is only rendered once, during initial render. Its *children* may\nchange during the updating phase, and this may cause its *bounds* to change, but the block itself\nremains stable.",
-      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:30"
+      "message": "Missing item type\nGet Tree Builder",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:686"
     },
     {
-      "message": "Missing item type\nA `ResettableBlock` can be reset during the updating phase and rendered again.\n\nThis occurs for two reasons:\n\n1. The block represents an element in a list, and the element has been removed\n2. The block represents a conditional, and the condition has changed",
-      "line": " packages/@glimmer/interfaces/lib/dom/attributes.d.ts:38"
+      "message": "Missing item type\nGet current Scope",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:693"
     },
     {
-      "message": "Missing item type\nDescribes the capabilities of a particular component. The capabilities are\nprovided to the Glimmer compiler and VM via the ComponentDefinition, which\nincludes a ComponentCapabilities record.\n\nCertain features in the VM come with some overhead, so the compiler and\nruntime use this information to skip unnecessary work for component types\nthat don't need it.\n\nFor example, a component that is template-only (i.e., it does not have an\nassociated JavaScript class to instantiate) can skip invoking component\nmanager hooks related to lifecycle events by setting the `elementHook`\ncapability to `false`.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:16"
+      "message": "Missing item type\nGet current Dynamic Scope",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:700"
     },
     {
-      "message": "Missing item type\nWhether a component's template is static across all instances of that\ncomponent, or can vary per instance. This should usually be `false` except\nfor cases of backwards-compatibility.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:31"
+      "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"
     },
     {
-      "message": "Missing item type\nWhether a \"wrapped\" component's root element can change after being\nrendered. This flag is only used by the WrappedBuilder and should be\n`false` except for cases of backwards-compatibility.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:38"
+      "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"
     },
     {
-      "message": "Missing item type\nSetting the `prepareArgs` flag to true enables the `prepareArgs` hook on\nthe component manager, which would otherwise not be called.\n\nThe component manager's `prepareArgs` hook allows it to programmatically\nadd or remove positional and named arguments for a component before the\ncomponent is invoked. This flag should usually be `false` except for cases\nof backwards-compatibility.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:47"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:823"
     },
     {
-      "message": "Missing item type\nWhether a reified `Arguments` object will get passed to the component\nmanager's `create` hook. If a particular component does not access passed\narguments from JavaScript (via the `this.args` property in Glimmer.js, for\nexample), this flag can be set to `false` to avoid the work of\ninstantiating extra data structures to expose the arguments to JavaScript.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:58"
+      "message": "Missing item type\nThe program counter that subsequent evaluations should start from.",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:832"
     },
     {
-      "message": "Missing item type\nWhether the component needs the caller component",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:67"
+      "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"
     },
     {
-      "message": "Missing item type\nWhether to call the `didSplatAttributes` hook on the component manager.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:72"
+      "message": "Missing item type\nThe current value of the VM's dynamic scope",
+      "line": " packages/@glimmer/runtime/lib/vm/append.ts:843"
     },
     {
-      "message": "Missing item type\nWhether to call the `didCreateElement` hook on the component manager.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:77"
+      "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"
     },
     {
-      "message": "Missing item type\nWhether the component manager has an update hook.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:82"
+      "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"
     },
     {
-      "message": "Missing item type\nWhether the component needs an additional dynamic scope frame.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:87"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:135"
     },
     {
-      "message": "Missing item type\nWhether there is a component instance to create. If this is false,\nthe component is a \"template only component\"",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:92"
+      "message": "Missing item type\n<div>   <---------------  currentCursor.element\n  <!--%+b:1%--> <-------  would have been removed during openBlock\n  <div> <---------------  currentCursor.candidate -> cursor.element\n    <!--%+b:2%--> <-----  currentCursor.candidate.firstChild -> cursor.candidate\n    Foo\n    <!--%-b:2%-->\n  </div>\n  <!--%-b:1%-->  <------  becomes currentCursor.candidate",
+      "line": " packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:144"
     },
     {
-      "message": "Missing item type\nWhether or not the component has a `willDestroy` hook that should fire\nprior to the component being removed from the DOM.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:98"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/curried-value.ts:37"
     },
     {
-      "message": "Missing item type\nWhether or not the component pushes an owner onto the owner stack. This is\nused for engines.",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:104"
+      "message": "Missing item type\nUsed to determine the the environment is interactive (e.g. SSR is not\ninteractive). Interactive environments schedule modifiers, among other things.",
+      "line": " packages/@glimmer/runtime/lib/environment.ts:188"
     },
     {
-      "message": "Missing item type\nEnum used for bit flags version of the capabilities, used once the component\nhas been loaded for the first time",
-      "line": " packages/@glimmer/interfaces/lib/managers/internal/component.d.ts:111"
+      "message": "Missing item type\nUsed to enable debug tooling",
+      "line": " packages/@glimmer/runtime/lib/environment.ts:194"
     },
     {
-      "message": "Missing item type\nAll parts of `DebugVmState` are _snapshots_. They will not change if the piece of VM state that\nthey reference changes.",
-      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:40"
+      "message": "Missing item type\nCallback to be called when an environment transaction commits",
+      "line": " packages/@glimmer/runtime/lib/environment.ts:199"
     },
     {
-      "message": "Missing item type\nThese values are the same for the entire program",
-      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:45"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/scope.ts:45"
     },
     {
-      "message": "Missing item type\nThese values can change for each opcode. You can get a snapshot a specific stack by calling\n`stacks.<name>.snapshot()`.",
-      "line": " packages/@glimmer/interfaces/lib/runtime/local-debug.d.ts:50"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/scope.ts:47"
     },
     {
-      "message": "Missing item type\nA single program can mix and match multiple owners. This can happen component is curried from a\ntemplate with one owner and then rendered in a second owner.\n\nNote: Owners can change when new root scopes are created (including when rendering a\ncomponent), but not in child scopes.",
-      "line": " packages/@glimmer/interfaces/lib/runtime/scope.d.ts:14"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/runtime/lib/scope.ts:86"
     },
     {
-      "message": "Missing item type\nRegisters\n\nFor the most part, these follows MIPS naming conventions, however the\nregister numbers are different.",
-      "line": " packages/@glimmer/interfaces/lib/runtime/vm-state.d.ts:13"
+      "message": "Missing item type\nExamples when true:\n - link\n - liNK\n\nExamples when false:\n - Link (component)",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:74"
     },
     {
-      "message": "Missing item type\nA special version of `Optional` that is used for values that are expected to be initialized. This\ndocuments the intent that the value will be initialized before it is used, and therefore that\nnull assertions or `?.` are not appropriate.",
-      "line": " packages/@glimmer/interfaces/lib/core.d.ts:7"
+      "message": "Missing item type\nThis includes the full list of keywords currently in use in the template\nlanguage, and where their valid usages are.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:531"
     },
     {
-      "message": "Missing item type\nA type that has an index signature, but nothing else is know about it. Useful in generic code\nthat needs to index into an opaque, user-specified object.",
-      "line": " packages/@glimmer/interfaces/lib/core.d.ts:16"
+      "message": "Missing item type\nAn object branded with a local debug type has special local trace logging\nbehavior.\n\nIf `LOCAL_DEBUG` is `false`, this function does nothing (and is removed\nby the minifier in builder).",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:563"
     },
     {
-      "message": "Missing item type\nThis is needed because the normal IteratorResult in the TypeScript\nstandard library is generic over the value in each tick and not over\nthe return value. It represents a standard ECMAScript IteratorResult.",
-      "line": " packages/@glimmer/interfaces/lib/core.d.ts:33"
+      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOCAL_LOGGER should only be used inside a\nLOCAL_TRACE_LOGGING check.\n\nIt does not alleviate the need to check LOCAL_TRACE_LOGGING, which is used\nfor stripping.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:594"
     },
     {
-      "message": "Missing item type\nReturn the number of entries in the table. A handle is legal if\nit is less than this number.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:42"
+      "message": "Missing item type\nThis constant exists to make it easier to differentiate normal logs from\nerrant console.logs. LOGGER can be used outside of LOCAL_TRACE_LOGGING checks,\nand is meant to be used in the rare situation where a console.* call is\nactually appropriate.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:603"
     },
     {
-      "message": "Missing item type\nThe `EvaluationContext` is the context that remains the same across all of the templates and\nevaluations in a single program.\n\nNote that multiple programs can co-exist on the same page, sharing tracking logic (and the\nglobal tracking context) but having different *evaluation* contexts.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:51"
+      "message": "Missing item type\ngenerated from https://raw.githubusercontent.com/w3c/html/26b5126f96f736f796b9e29718138919dd513744/entities.json\ndo not edit",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:3181"
     },
     {
-      "message": "Missing item type\nThe program's environment, which contains customized framework behavior.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:59"
+      "message": "Missing item type\nWe have already computed the character position of this offset or span.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5951"
     },
     {
-      "message": "Missing item type\nThe compiled program itself: the constants and heap",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:63"
+      "message": "Missing item type\nThis offset or span was instantiated with a Handlebars SourcePosition or SourceLocation. Its\ncharacter position will be computed on demand.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5956"
     },
     {
-      "message": "Missing item type\nThe offsets to stdlib functions",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:67"
+      "message": "Missing item type\nfor (rare) situations where a node is created but there was no source location (e.g. the name\n\"default\" in default blocks when the word \"default\" never appeared in source). This is used\nby the internals when there is a legitimate reason for the internals to synthesize a node\nwith no location.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5962"
     },
     {
-      "message": "Missing item type\nA framework-specified resolver for resolving free variables in classic templates.\n\nA strict component can invoke a classic component and vice versa, but only classic components\nwill use the resolver. If no resolver is available in the `ProgramContext`, only strict components\nwill compile and run.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:71"
+      "message": "Missing item type\nFor situations where a node represents zero parts of the source (for example, empty arguments).\nIn general, we attempt to assign these nodes *some* position (empty arguments can be\npositioned immediately after the callee), but it's not always possible",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5971"
     },
     {
-      "message": "Missing item type\nOptions for compiling a specific template. This carries\nalong the static information associated with the entire\ntemplate when compiling blocks nested inside of it.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:83"
+      "message": "Missing item type\nFor situations where a source location was expected, but it didn't correspond to the node in\nthe source. This happens if a plugin creates broken locations.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5979"
     },
     {
-      "message": "Missing item type\nConstants are interned values that are referenced as numbers in the program.\nThe constant pool is a part of the program, and is always transmitted\ntogether with the program.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:98"
+      "message": "Missing item type\nThese kinds  describe spans that don't have a concrete location in the original source.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5986"
     },
     {
-      "message": "Missing item type\nResolution happens when components are first loaded, either via the resolver\nor via looking them up in template scope.",
-      "line": " packages/@glimmer/interfaces/lib/program.d.ts:109"
+      "message": "Missing item type\nThis file implements the DSL used by span and offset in places where they need to exhaustively\nconsider all combinations of states (Handlebars offsets, character offsets and invisible/broken\noffsets).\n\nIt's probably overkill, but it makes the code that uses it clear. It could be refactored or\nremoved.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:5994"
     },
     {
-      "message": "Missing item type\nThis file describes the interface between compilation time\nand runtime.\n\n# Locators\n\nCompile time and runtime must share the same Locator. A Locator is an\nobject that describes the location of a template, and is roughly a\nmodule name. The compiler and runtime may use the Locator to locally\nresolve names relative to the template the name was found in, but must\nshare resolution rules between compilation time and runtime.\n\nFor example, given this template with Locator\n`{ module: 'components/Articles/Container' }:\n\n```\n<TabBar />\n```\n\nThe compiler may resolve `<TabBar>` to `components/Articles/TabBar`. The\nimportant thing is that the compiler and runtime share resolution rules.\n\n# CompileTimeLookup\n\nWhen compiling an application, the `CompileTimeLookup` is responsible\nfor resolving helpers, modifiers, and components into \"handles\"\n(numbers) that can be embedded into the program and used at runtime.\n\n# RuntimeResolver\n\nThe `RuntimeResolver` has two responsibilities.\n\n1. To turn handles created by the `CompileTimeLookup` into live helpers,\n   modifiers, and components.\n2. To resolve dynamic components at runtime that come from\n   calls to `{{component dynamic}}`.\n\nThe `CompileTimeLookup` and `RuntimeResolver` must maintain symmetry\nbetween:\n\n* `resolver.resolve(lookup.lookupComponentDefinition(name, referrer))`; and\n* `resolver.lookupComponentDefinition(name, referrer))`\n\n# Coupling\n\nIn practice, the `CompileTimeLookup` and `RuntimeResolver` are two parts\nof one system. The goal of this system is to allow the `CompileTimeLookup`\nto do as much resolution as possible ahead of time, while still allowing\nthe `RuntimeResolver` to do dynamic resolution when necessary.",
-      "line": " packages/@glimmer/interfaces/lib/serialize.d.ts:1"
+      "message": "Missing item type\nYou didn't exhaustively match all possibilities.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6054"
     },
     {
-      "message": "Missing item type\nFor debugging",
-      "line": " packages/@glimmer/interfaces/lib/stack.d.ts:13"
+      "message": "Missing item type\nAll spans have these details in common.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6117"
     },
     {
-      "message": "Missing item type\nThis union represents all of the possible tag types for the monomorphic tag class.\nOther custom tag classes can exist, such as CurrentTag and VolatileTag, but for\nperformance reasons, any type of tag that is meant to be used frequently should\nbe added to the monomorphic tag.",
-      "line": " packages/@glimmer/interfaces/lib/tags.d.ts:12"
+      "message": "Missing item type\nA `SourceSpan` object represents a span of characters inside of a template source.\n\nThere are three kinds of `SourceSpan` objects:\n\n- `ConcreteSourceSpan`, which contains byte offsets\n- `LazySourceSpan`, which contains `SourceLocation`s from the Handlebars AST, which can be\n  converted to byte offsets on demand.\n- `InvisibleSourceSpan`, which represent source strings that aren't present in the source,\n  because:\n    - they were created synthetically\n    - their location is nonsensical (the span is broken)\n    - they represent nothing in the source (this currently happens only when a bug in the\n      upstream Handlebars parser fails to assign a location to empty blocks)\n\nAt a high level, all `SourceSpan` objects provide:\n\n- byte offsets\n- source in column and line format\n\nAnd you can do these operations on `SourceSpan`s:\n\n- collapse it to a `SourceSpan` representing its starting or ending position\n- slice out some characters, optionally skipping some characters at the beginning or end\n- create a new `SourceSpan` with a different starting or ending offset\n\nAll SourceSpan objects implement `SourceLocation`, for compatibility. All SourceSpan\nobjects have a `toJSON` that emits `SourceLocation`, also for compatibility.\n\nFor compatibility, subclasses of `AbstractSourceSpan` must implement `locDidUpdate`, which\nhappens when an AST plugin attempts to modify the `start` or `end` of a span directly.\n\nThe goal is to avoid creating any problems for use-cases like AST Explorer.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6121"
     },
     {
-      "message": "Missing item type\nEnvironment specific template.",
-      "line": " packages/@glimmer/interfaces/lib/template.d.ts:30"
+      "message": "Missing item type\nGet the starting `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6214"
     },
     {
-      "message": "Missing item type\nModule name associated with the template, used for debugging purposes",
-      "line": " packages/@glimmer/interfaces/lib/template.d.ts:36"
+      "message": "Missing item type\nGet the ending `SourcePosition` for this `SourceSpan`, lazily computing it if needed.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6221"
     },
     {
-      "message": "Missing item type\nhttps://astexplorer.net/#/gist/c3f41b75af73006f64476775e73f7daa/e6e3e120df8404b1bff308bec3ed89eaaf0b05f2\n\nThis plugin exists because, _even when we inline",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:1"
+      "message": "Missing item type\nSupport converting ASTv1 nodes into a serialized format using JSON.stringify.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6228"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:44"
+      "message": "Missing item type\nCreate a new span with the current span's end and a new beginning.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6235"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:51"
+      "message": "Missing item type\nCreate a new span with the current span's beginning and a new ending.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6242"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:62"
+      "message": "Missing item type\nConvert this `SourceSpan` into a `SourceSlice`.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6252"
     },
-    {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:72"
+    {
+      "message": "Missing item type\nFor compatibility with SourceLocation in AST plugins",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6264"
     },
     {
-      "message": "Missing item type\nDo we want to support local aliasing / re-assignment?\nif so, this would break",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:82"
+      "message": "Missing item type\nFor compatibility with SourceLocation in AST plugins",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6273"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:92"
+      "message": "Missing item type\nFor compatibility with SourceLocation in AST plugins",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6284"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/local-debug-babel-plugin/index.js:114"
+      "message": "Missing item type\nFor compatibility with SourceLocation in AST plugins",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6293"
     },
     {
-      "message": "Missing item type\nIf the specified flag is set as a boolean flag with no value, `true` is returned.\n\nOtherwise, this function returns true if the flag value is a pattern that matches `value`.\n\nThe pattern can have a `*`, which matches any number of characters.",
-      "line": " packages/@glimmer/local-debug-flags/index.ts:129"
+      "message": "Missing item type\nFor compatibility with SourceLocation in AST plugins",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6304"
     },
     {
-      "message": "Missing item type\nThere is also Reflect.getPrototypeOf,\nwhich errors when non-objects are passed.\n\nSince our conditional for figuring out whether to render primitives or not\nmay contain non-object values, we don't want to throw errors when we call this.",
-      "line": " packages/@glimmer/manager/lib/internal/api.ts:28"
+      "message": "Missing item type\nAll positions have these details in common. Most notably, all three kinds of positions can\nmust be able to attempt to convert themselves into {@see CharPosition}.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6567"
     },
     {
-      "message": "Missing item type\nThe CustomComponentManager allows addons to provide custom component\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom component manager, which\nimplements a set of hooks that determine component behavior.\n\nTo create a custom component manager, instantiate a new CustomComponentManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomComponentManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a component, the component manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n\n* `create()` - invoked when a new instance of a component should be created\n* `update()` - invoked when the arguments passed to a component change\n* `getContext()` - returns the object that should be",
-      "line": " packages/@glimmer/manager/lib/public/component.ts:85"
+      "message": "Missing item type\nUsed to indicate that an attempt to convert a `SourcePosition` to a character offset failed. It\nis separate from `null` so that `null` can be used to indicate that the computation wasn't yet\nattempted (and therefore to cache the failure)",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6572"
     },
     {
-      "message": "Missing item type\nStores internal state about a component instance after it's been created.",
-      "line": " packages/@glimmer/manager/lib/public/component.ts:208"
+      "message": "Missing item type\nA `SourceOffset` represents a single position in the source.\n\nThere are three kinds of backing data for `SourceOffset` objects:\n\n- `CharPosition`, which contains a character offset into the raw source string\n- `HbsPosition`, which contains a `SourcePosition` from the Handlebars AST, which can be\n  converted to a `CharPosition` on demand.\n- `InvisiblePosition`, which represents a position not in source (@see {InvisiblePosition})",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6578"
     },
     {
-      "message": "Missing item type\nThe CustomModifierManager allows addons to provide custom modifier\nimplementations that integrate seamlessly into Ember. This is accomplished\nthrough a delegate, registered with the custom modifier manager, which\nimplements a set of hooks that determine modifier behavior.\nTo create a custom modifier manager, instantiate a new CustomModifierManager\nclass and pass the delegate as the first argument:\n\n```js\nlet manager = new CustomModifierManager({\n  // ...delegate implementation...\n});\n```\n\n## Delegate Hooks\n\nThroughout the lifecycle of a modifier, the modifier manager will invoke\ndelegate hooks that are responsible for surfacing those lifecycle changes to\nthe end developer.\n* `createModifier()` - invoked when a new instance of a modifier should be created\n* `installModifier()` - invoked when the modifier is installed on the element\n* `updateModifier()` - invoked when the arguments passed to a modifier change\n* `destroyModifier()` - invoked when the modifier is about to be destroyed",
-      "line": " packages/@glimmer/manager/lib/public/modifier.ts:50"
+      "message": "Missing item type\nCreate a `SourceOffset` from a Handlebars `SourcePosition`. It's stored as-is, and converted\ninto a character offset on demand, which avoids unnecessarily computing the offset of every\n`SourceLocation`, but also means that broken `SourcePosition`s are not always detected.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6589"
     },
     {
-      "message": "Missing item type\nConverts a ComponentCapabilities object into a 32-bit integer representation.",
-      "line": " packages/@glimmer/manager/lib/util/capabilities.ts:48"
+      "message": "Missing item type\nCreate a `SourceOffset` that corresponds to a broken `SourcePosition`. This means that the\ncalling code determined (or knows) that the `SourceLocation` doesn't correspond correctly to\nany part of the source.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6598"
     },
     {
-      "message": "Missing item type\nYield to a block located at a particular symbol location.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:28"
+      "message": "Missing item type\nGet the character offset for this `SourceOffset`, if possible.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6610"
     },
     {
-      "message": "Missing item type\nPush an (optional) yieldable block onto the stack. The yieldable block must be known\nstatically at compile time.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:48"
+      "message": "Missing item type\nCompare this offset with another one.\n\nIf both offsets are `HbsPosition`s, they're equivalent as long as their lines and columns are\nthe same. This avoids computing offsets unnecessarily.\n\nOtherwise, two `SourceOffset`s are equivalent if their successfully computed character offsets\nare the same.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6618"
     },
     {
-      "message": "Missing item type\nInvoke a block that is known statically at compile time.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:63"
+      "message": "Missing item type\nCreate a span that starts from this source offset and ends with another source offset. Avoid\ncomputing character offsets if both `SourceOffset`s are still lazy.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6631"
     },
     {
-      "message": "Missing item type\nInvoke a static block, preserving some number of stack entries for use in\nupdating.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/blocks.ts:79"
+      "message": "Missing item type\nCreate a `SourceOffset` by moving the character position represented by this source offset\nforward or backward (if `by` is negative), if possible.\n\nIf this `SourceOffset` can't compute a valid character offset, `move` returns a broken offset.\n\nIf the resulting character offset is less than 0 or greater than the size of the source, `move`\nreturns a broken offset.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6639"
     },
     {
-      "message": "Missing item type\nA convenience for pushing some arguments on the stack and\nrunning some code if the code needs to be re-executed during\nupdating execution if some of the arguments have changed.\n\n# Initial Execution\n\nThe `args` function should push zero or more arguments onto\nthe stack and return the number of arguments pushed.\n\nThe `body` function provides the instructions to execute both\nduring initial execution and during updating execution.\n\nInternally, this function starts by pushing a new frame, so\nthat the body can return and sets the return point ($ra) to\nthe ENDINITIAL label.\n\nIt then executes the `args` function, which adds instructions\nresponsible for pushing the arguments for the block to the\nstack. These arguments will be restored to the stack before\nupdating execution.\n\nNext, it adds the Enter opcode, which marks the current position\nin the DOM, and remembers the current $pc (the next instruction)\nas the first instruction to execute during updating execution.\n\nNext, it runs `body`, which adds the opcodes that should\nexecute both during initial execution and during updating execution.\nIf the `body` wishes to finish early, it should Jump to the\n`FINALLY` label.\n\nNext, it adds the FINALLY label, followed by:\n\n- the Exit opcode, which finalizes the marked DOM started by the\n  Enter opcode.\n- the Return opcode, which returns to the current return point\n  ($ra).\n\nFinally, it adds the ENDINITIAL label followed by the PopFrame\ninstruction, which restores $fp, $sp and $ra.\n\n# Updating Execution\n\nUpdating execution for this `replayable` occurs if the `body` added an\nassertion, via one of the `JumpIf`, `JumpUnless` or `AssertSame` opcodes.\n\nIf, during updating executon, the assertion fails, the initial VM is\nrestored, and the stored arguments are pushed onto the stack. The DOM\nbetween the starting and ending markers is cleared, and the VM's cursor\nis set to the area just cleared.\n\nThe return point ($ra) is set to -1, the exit instruction.\n\nFinally, the $pc is set to to the instruction saved off by the\nEnter opcode during initial execution, and execution proceeds as\nusual.\n\nThe only difference is that when a `Return` instruction is\nencountered, the program jumps to -1 rather than the END label,\nand the PopFrame opcode is not needed.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts:73"
+      "message": "Missing item type\nCreate a new `SourceSpan` that represents a collapsed range at this source offset. Avoid\ncomputing the character offset if it has not already been computed.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6662"
     },
     {
-      "message": "Missing item type\nA specialized version of the `replayable` convenience that allows the\ncaller to provide different code based upon whether the item at\nthe top of the stack is true or false.\n\nAs in `replayable`, the `ifTrue` and `ifFalse` code can invoke `return`.\n\nDuring the initial execution, a `return` will continue execution\nin the cleanup code, which finalizes the current DOM block and pops\nthe current frame.\n\nDuring the updating execution, a `return` will exit the updating\nroutine, as it can reuse the DOM block and is always only a single\nframe deep.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/conditional.ts:187"
+      "message": "Missing item type\nConvert this `SourceOffset` into a Handlebars {@see SourcePosition} for compatibility with\nexisting plugins.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6670"
     },
     {
-      "message": "Missing item type\n<Foo/>\n<Foo></Foo>\n<Foo @arg={{true}} />",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:78"
+      "message": "Missing item type",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6681"
     },
     {
-      "message": "Missing item type\n(helper)\n(helper arg)",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:144"
+      "message": "Missing item type\nThis is already a `CharPosition`.\n\n{@see HbsPosition} for the alternative.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6688"
     },
     {
-      "message": "Missing item type\n<div {{modifier}}/>\n<div {{modifier arg}}/>\n<Foo {{modifier}}/>",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:191"
+      "message": "Missing item type\nProduce a Handlebars {@see SourcePosition} for this `CharPosition`. If this `CharPosition` was\ncomputed using {@see SourceOffset#move}, this will compute the `SourcePosition` for the offset.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6697"
     },
     {
-      "message": "Missing item type\n{{component-or-helper arg}}",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:254"
+      "message": "Missing item type\nA `CharPosition` always has an offset it can produce without any additional computation.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6709"
     },
     {
-      "message": "Missing item type\n{{maybeHelperOrComponent}}",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:344"
+      "message": "Missing item type\nConvert the current character offset to an `HbsPosition`, if it was not already computed. Once\na `CharPosition` has computed its `HbsPosition`, it will not need to do compute it again, and\nthe same `CharPosition` is retained when used as one of the ends of a `SourceSpan`, so\ncomputing the `HbsPosition` should be a one-time operation.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6716"
     },
     {
-      "message": "Missing item type\nCompile arguments, pushing an Arguments object onto the stack.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/shared.ts:16"
+      "message": "Missing item type\nLazily compute the character offset from the {@see SourcePosition}. Once an `HbsPosition` has\ncomputed its `CharPosition`, it will not need to do compute it again, and the same\n`HbsPosition` is retained when used as one of the ends of a `SourceSpan`, so computing the\n`CharPosition` should be a one-time operation.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6744"
     },
     {
-      "message": "Missing item type\nCompile an optional list of positional arguments, which pushes each argument\nonto the stack and returns the number of parameters compiled",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/shared.ts:89"
+      "message": "Missing item type\nReturn the {@see SourcePosition} that this `HbsPosition` was instantiated with. This operation\ndoes not need to compute anything.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6763"
     },
     {
-      "message": "Missing item type\nAppend content to the DOM. This standard function triages content and does the\nright thing based upon whether it's a string, safe string, component, fragment\nor node.",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/stdlib.ts:31"
+      "message": "Missing item type\nThis is already an `HbsPosition`.\n\n{@see CharPosition} for the alternative.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6774"
     },
     {
-      "message": "Missing item type\nPush a reference onto the stack corresponding to a statically known primitive",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:34"
+      "message": "Missing item type\nA broken position cannot be turned into a {@see CharacterPosition}.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6791"
     },
     {
-      "message": "Missing item type\nPush an encoded representation of a JavaScript primitive on the stack",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:43"
+      "message": "Missing item type\nThe serialization of an `InvisiblePosition is whatever Handlebars {@see SourcePosition} was\noriginally identified as broken, non-existent or synthetic.\n\nIf an `InvisiblePosition` never had an source offset at all, this method returns\n{@see UNKNOWN_POSITION} for compatibility.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6798"
     },
     {
-      "message": "Missing item type\nInvoke a foreign function (a \"helper\") based on a statically known handle",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:58"
+      "message": "Missing item type\nCompare two {@see AnyPosition} and determine whether they are equal.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6816"
     },
     {
-      "message": "Missing item type\nInvoke a foreign function (a \"helper\") based on a dynamically loaded definition",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:79"
+      "message": "Missing item type\nValidate that the character offset represents a position in the source string.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6845"
     },
     {
-      "message": "Missing item type\nEvaluate statements in the context of new dynamic scope entries. Move entries from the\nstack into named entries in the dynamic scope, then evaluate the statements, then pop\nthe dynamic scope",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/vm.ts:108"
+      "message": "Missing item type\nThe Parser Builder differentiates from the public builder API by:\n\n1. Offering fewer different ways to instantiate nodes\n2. Mandating source locations",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:7820"
     },
     {
-      "message": "Missing item type\nWraps a template js in a template module to change it into a factory\nthat handles lazy parsing the template and to create per env singletons\nof the template.",
-      "line": " packages/@glimmer/opcode-compiler/lib/template.ts:39"
+      "message": "Missing item type\nASTPlugins can make changes to the Glimmer template AST before\ncompilation begins.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9349"
     },
     {
-      "message": "Missing item type\nFramework objects in a Glimmer application may receive an owner object.\nGlimmer is unopinionated about this owner, but will forward it through its\ninternal resolution system, and through its managers if it is provided.",
-      "line": " packages/@glimmer/owner/index.ts:8"
+      "message": "Missing item type\nGets the correct Token from the Node based on it's type",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9417"
     },
     {
-      "message": "Missing item type\n`setOwner` set's an object's owner",
-      "line": " packages/@glimmer/owner/index.ts:17"
+      "message": "Missing item type\nAdds tokens to the tokensSet based on their node.type",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9460"
     },
     {
-      "message": "Missing item type\nDefault component template, which is a plain yield",
-      "line": " packages/@glimmer/program/lib/util/default-template.ts:4"
+      "message": "Missing item type\nParses and traverses a given handlebars html template to extract all template locals\nreferenced that could possible come from the parent scope. Can exclude known keywords\noptionally.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9473"
     },
     {
-      "message": "Missing item type\nThe Program Heap is responsible for dynamically allocating\nmemory in which we read/write the VM's instructions\nfrom/to. When we malloc we pass out a VMHandle, which\nis used as an indirect way of accessing the memory during\nexecution of the VM. Internally we track the different\nregions of the memory in an int array known as the table.\n\nThe table 32-bit aligned and has the following layout:\n\n| ... | hp (u32) |       info (u32)   | size (u32) |\n| ... |  Handle  | Scope Size | State | Size       |\n| ... | 32bits   | 30bits     | 2bits | 32bit      |\n\nWith this information we effectively have the ability to\ncontrol when we want to free memory. That being said you\ncan not free during execution as raw address are only\nvalid during the execution. This means you cannot close\nover them as you will have a bad memory access exception.",
-      "line": " packages/@glimmer/program/lib/program.ts:20"
+      "message": "Missing item type\nThis is a convenience function for creating ASTv2 nodes, with an optional name and the node's\noptions.\n\n```ts\nexport class HtmlText extends node('HtmlText').fields<{ chars: string }>() {}\n```\n\nThis creates a new ASTv2 node with the name `'HtmlText'` and one field `chars: string` (in\naddition to a `loc: SourceOffsets` field, which all nodes have).\n\n```ts\nexport class Args extends node().fields<{\n positional: PositionalArguments;\n named: NamedArguments\n}>() {}\n```\n\nThis creates a new un-named ASTv2 node with two fields (`positional: Positional` and `named:\nNamed`, in addition to the generic `loc: SourceOffsets` field).\n\nOnce you create a node using `node`, it is instantiated with all of its fields (including `loc`):\n\n```ts\nnew HtmlText({ loc: offsets, chars: someString });\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9536"
     },
     {
-      "message": "Missing item type\nThe heap uses the [Mark-Compact Algorithm](https://en.wikipedia.org/wiki/Mark-compact_algorithm) to shift\nreachable memory to the bottom of the heap and freeable\nmemory to the top of the heap. When we have shifted all\nthe reachable memory to the top of the heap, we move the\noffset to the next free position.",
-      "line": " packages/@glimmer/program/lib/program.ts:122"
+      "message": "Missing item type\nCorresponds to syntaxes with positional and named arguments:\n\n- SubExpression\n- Invoking Append\n- Invoking attributes\n- InvokeBlock\n\nIf `Args` is empty, the `SourceOffsets` for this node should be the collapsed position\nimmediately after the parent call node's `callee`.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9596"
     },
     {
-      "message": "Missing item type\nWhen iterating over a list, it's possible that an item with the same unique\nkey could be encountered twice:\n\n```js\nlet arr = ['same', 'different', 'same', 'same'];\n```\n\nIn general, we want to treat these items as _unique within the list_. To do\nthis, we track the occurences of every item as we iterate the list, and when\nan item occurs more than once, we generate a new unique key just for that\nitem, and that occurence within the list. The next time we iterate the list,\nand encounter an item for the nth time, we can get the _same_ key, and let\nGlimmer know that it should reuse the DOM for the previous nth occurence.",
-      "line": " packages/@glimmer/reference/lib/iterable.ts:135"
+      "message": "Missing item type\nCorresponds to positional arguments.\n\nIf `PositionalArguments` is empty, the `SourceOffsets` for this node should be the collapsed\nposition immediately after the parent call node's `callee`.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9633"
     },
     {
-      "message": "Missing item type\nThe VM creates a new ComponentInstance data structure for every component\ninvocation it encounters.\n\nSimilar to how a ComponentDefinition contains state about all components of a\nparticular type, a ComponentInstance contains state specific to a particular\ninstance of a component type. It also contains a pointer back to its\ncomponent type's ComponentDefinition.",
-      "line": " packages/@glimmer/runtime/lib/compiled/opcodes/component.ts:107"
+      "message": "Missing item type\nCorresponds to named arguments.\n\nIf `PositionalArguments` and `NamedArguments` are empty, the `SourceOffsets` for this node should\nbe the same as the `Args` node that contains this node.\n\nIf `PositionalArguments` is not empty but `NamedArguments` is empty, the `SourceOffsets` for this\nnode should be the collapsed position immediately after the last positional argument.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9657"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/component/interfaces.ts:8"
+      "message": "Missing item type\nCorresponds to a single named argument.\n\n```hbs\nx=<expr>\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9685"
     },
     {
-      "message": "Missing item type\nPerforms a strict equality comparison.\n\nleft === right",
-      "line": " packages/@glimmer/runtime/lib/helpers/eq.ts:3"
+      "message": "Missing item type\nAttr nodes look like HTML attributes, but are classified as:\n\n1. `HtmlAttr`, which means a regular HTML attribute in Glimmer\n2. `SplatAttr`, which means `...attributes`\n3. `ComponentArg`, which means an attribute whose name begins with `@`, and it is therefore a\n   component argument.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9703"
     },
     {
-      "message": "Missing item type\nPerforms a greater than comparison.\n\nleft > right",
-      "line": " packages/@glimmer/runtime/lib/helpers/gt.ts:3"
+      "message": "Missing item type\n`HtmlAttr` and `SplatAttr` are grouped together because the order of the `SplatAttr` node,\nrelative to other attributes, matters.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9712"
     },
     {
-      "message": "Missing item type\nPerforms a greater than or equal comparison.\n\nleft >= right",
-      "line": " packages/@glimmer/runtime/lib/helpers/gte.ts:3"
+      "message": "Missing item type\n\"Attr Block\" nodes are allowed inside an open element tag in templates. They interact with the\nelement (or component).",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9717"
     },
     {
-      "message": "Missing item type\nPerforms a less than comparison.\n\nleft < right",
-      "line": " packages/@glimmer/runtime/lib/helpers/lt.ts:3"
+      "message": "Missing item type\n`HtmlAttr` nodes are valid HTML attributes, with or without a value.\n\nExceptions:\n\n- `...attributes` is `SplatAttr`\n- `@x=<value>` is `ComponentArg`",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9722"
     },
     {
-      "message": "Missing item type\nPerforms a less than or equal comparison.\n\nleft <= right",
-      "line": " packages/@glimmer/runtime/lib/helpers/lte.ts:3"
+      "message": "Missing item type\nCorresponds to an argument passed by a component (`@x=<value>`)",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9733"
     },
     {
-      "message": "Missing item type\nPerforms a strict inequality comparison.\n\nleft !== right",
-      "line": " packages/@glimmer/runtime/lib/helpers/neq.ts:3"
+      "message": "Missing item type\nConvert the component argument into a named argument node",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9737"
     },
     {
-      "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"
+      "message": "Missing item type\nAn `ElementModifier` is just a normal call node in modifier position.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9748"
     },
     {
-      "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"
+      "message": "Missing item type\nContent Nodes are allowed in content positions in templates. They correspond to behavior in the\n[Data][data] tokenization state in HTML.\n\n[data]: https://html.spec.whatwg.org/multipage/parsing.html#data-state",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9753"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a component invocation. When the content of a component invocation contains no\nnamed blocks, `blocks` contains a single named block named `\"default\"`. When a component\ninvocation is self-closing, `blocks` is empty.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9780"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a simple HTML element. The AST allows component arguments and modifiers to support\nfuture extensions.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9794"
     },
     {
-      "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"
+      "message": "Missing item type\nA Handlebars literal.\n\n{@link https://handlebarsjs.com/guide/expressions.html#literal-segments}",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9808"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a Handlebars literal.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9814"
     },
     {
-      "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"
+      "message": "Missing item type\nReturns true if an input {@see ExpressionNode} is a literal.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9827"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a path in expression position.\n\n```hbs\nthis\nthis.x\n@x\n@x.y\nx\nx.y\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9844"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a known strict-mode keyword. It behaves similarly to a\nPathExpression with a FreeVarReference, but implies StrictResolution and\nis guaranteed to not have a tail, since `{{outlet.foo}}` would have been\nillegal.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9858"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a parenthesized call expression.\n\n```hbs\n(x)\n(x.y)\n(x y)\n(x.y z)\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9866"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to an interpolation in attribute value position.\n\n```hbs\n<a href=\"{{url}}.html\"\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9878"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to an entire template.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9887"
     },
     {
-      "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"
+      "message": "Missing item type\nRepresents a block. In principle this could be merged with `NamedBlock`, because all cases\ninvolving blocks have at least a notional name.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9892"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a collection of named blocks.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9898"
     },
     {
-      "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"
+      "message": "Missing item type\nGet the `NamedBlock` for a given name.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9902"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to a single named block. This is used for anonymous named blocks (`default` and\n`else`).",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9910"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to `this` at the head of an expression.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9924"
     },
     {
-      "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"
+      "message": "Missing item type\nCorresponds to `@<ident>` at the beginning of an expression.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9929"
     },
     {
-      "message": "Missing item type\n## State changes\n\n- [!] push Updating Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:630"
+      "message": "Missing item type\nCorresponds to `<ident>` at the beginning of an expression, when `<ident>` is in the current\nblock's scope.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9934"
     },
     {
-      "message": "Missing item type\n## State changes\n\n[!] pop Updating Stack",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:641"
+      "message": "Missing item type\nCorresponds to `<ident>` at the beginning of an expression, when `<ident>` is *not* in the\ncurrent block's scope.\n\nThe `resolution: FreeVarResolution` field describes how to resolve the free variable.\n\nNote: In strict mode, it must always be a variable that is in a concrete JavaScript scope that\nthe template will be installed into.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9940"
     },
     {
-      "message": "Missing item type\n## State changes\n\n[!] push Updating List",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:652"
+      "message": "Missing item type\nA free variable is resolved according to a resolution rule:\n\n1. Strict resolution\n2. Namespaced resolution",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9957"
     },
     {
-      "message": "Missing item type\n## State changes\n\n[-] associate destroyable `child`",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:667"
+      "message": "Missing item type\nStrict resolution is used:\n\n1. in a strict mode template\n2. in an local variable invocation with dot paths",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9965"
     },
     {
-      "message": "Missing item type\nGet Tree Builder",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:686"
+      "message": "Missing item type\nA `LooseModeResolution` includes one or more namespaces to resolve the variable in\n\nIn practice, there are a limited number of possible combinations of these degrees of freedom,\nand they are captured by the `Namespaces` union below.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9984"
     },
     {
-      "message": "Missing item type\nGet current Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:693"
+      "message": "Missing item type\nNamespaced resolution is used in an unambiguous syntax position:\n\n1. `(sexp)` (namespace: `Helper`)\n2. `{{#block}}` (namespace: `Component`)\n3. `<a {{modifier}}>` (namespace: `Modifier`)\n4. `<Component />` (namespace: `Component`)",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9991"
     },
     {
-      "message": "Missing item type\nGet current Dynamic Scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:700"
+      "message": "Missing item type\nAppend resolution is used when the variable should be resolved in both the `component` and\n`helper` namespaces.\n\n```hbs\n{{x}}\n```\n\n```hbs\n{{x y}}\n```\n\n^ In either case, `x` should be resolved in the `component` and `helper` namespaces.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10003"
     },
     {
-      "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"
+      "message": "Missing item type\nTrusting append resolution is used when the variable should be resolved only in the\n`helper` namespaces.\n\n```hbs\n{{{x}}}\n```\n\n```hbs\n{{{x y}}}\n```\n\n^ In either case, `x` should be resolved in the `helper` namespace.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10021"
     },
     {
-      "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"
+      "message": "Missing item type\nA `Namespaced` must be resolved in one or more namespaces.\n\n```hbs\n<X />\n```\n\n^ `X` is resolved in the `component` namespace\n\n```hbs\n(x)\n```\n\n^ `x` is resolved in the `helper` namespace\n\n```hbs\n<a {{x}} />\n```\n\n^ `x` is resolved in the `modifier` namespace",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10068"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:823"
+      "message": "Missing item type\nThis corresponds to attribute curlies (<Foo bar={{...}}>).\nIn strict mode, this also corresponds to arg curlies.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10619"
     },
     {
-      "message": "Missing item type\nThe program counter that subsequent evaluations should start from.",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:832"
+      "message": "Missing item type\nThis corresponds to append positions text curlies.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10631"
     },
     {
-      "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"
+      "message": "Missing item type\nA call node has a simple callee if its head is:\n\n- a `PathExpression`\n- the `PathExpression`'s head is a `VarHead`\n- it has no tail\n\nSimple heads:\n\n```\n{{x}}\n{{x y}}\n```\n\nNot simple heads:\n\n```\n{{x.y}}\n{{x.y z}}\n{{@x}}\n{{@x a}}\n{{this}}\n{{this a}}\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10645"
     },
     {
-      "message": "Missing item type\nThe current value of the VM's dynamic scope",
-      "line": " packages/@glimmer/runtime/lib/vm/append.ts:843"
+      "message": "Missing item type\nA `BlockContext` represents the block that a particular AST node is contained inside of.\n\n`BlockContext` is aware of template-wide options (such as strict mode), as well as the bindings\nthat are in-scope within that block.\n\nConcretely, it has the `PrecompileOptions` and current `SymbolTable`, and provides\nfacilities for working with those options.\n\n`BlockContext` is stateless.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10702"
     },
     {
-      "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"
+      "message": "Missing item type\nAn `ExpressionNormalizer` normalizes expressions within a block.\n\n`ExpressionNormalizer` is stateless.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10784"
     },
     {
-      "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"
+      "message": "Missing item type\nThe `normalize` method takes an arbitrary expression and its original syntax context and\nnormalizes it to an ASTv2 expression.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10794"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:135"
+      "message": "Missing item type\nThe `callParts` method takes ASTv1.CallParts as well as a syntax context and normalizes\nit to an ASTv2 CallParts.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10848"
     },
     {
-      "message": "Missing item type\n<div>   <---------------  currentCursor.element\n  <!--%+b:1%--> <-------  would have been removed during openBlock\n  <div> <---------------  currentCursor.candidate -> cursor.element\n    <!--%+b:2%--> <-----  currentCursor.candidate.firstChild -> cursor.candidate\n    Foo\n    <!--%-b:2%-->\n  </div>\n  <!--%-b:1%-->  <------  becomes currentCursor.candidate",
-      "line": " packages/@glimmer/runtime/lib/vm/rehydrate-builder.ts:144"
+      "message": "Missing item type\nThe `ref` method normalizes an `ASTv1.PathHead` into an `ASTv2.VariableReference`.\nThis method is extremely important, because it is responsible for normalizing free\nvariables into an an ASTv2.PathHead *with appropriate context*.\n\nThe syntax context is originally determined by the syntactic position that this `PathHead`\ncame from, and is ultimately attached to the `ASTv2.VariableReference` here. In ASTv2,\nthe `VariableReference` node bears full responsibility for loose mode rules that control\nthe behavior of free variables.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10890"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/curried-value.ts:37"
+      "message": "Missing item type\n`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10941"
     },
     {
-      "message": "Missing item type\nUsed to determine the the environment is interactive (e.g. SSR is not\ninteractive). Interactive environments schedule modifiers, among other things.",
-      "line": " packages/@glimmer/runtime/lib/environment.ts:188"
+      "message": "Missing item type\nNormalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11019"
     },
     {
-      "message": "Missing item type\nUsed to enable debug tooling",
-      "line": " packages/@glimmer/runtime/lib/environment.ts:194"
+      "message": "Missing item type\nNormalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11059"
     },
     {
-      "message": "Missing item type\nCallback to be called when an environment transaction commits",
-      "line": " packages/@glimmer/runtime/lib/environment.ts:199"
+      "message": "Missing item type\nNormalizes an ASTv1.ElementNode to:\n\n- ASTv2.NamedBlock if the tag name begins with `:`\n- ASTv2.Component if the tag name matches the component heuristics\n- ASTv2.SimpleElement if the tag name doesn't match the component heuristics\n\nA tag name represents a component if:\n\n- it begins with `@`\n- it is exactly `this` or begins with `this.`\n- the part before the first `.` is a reference to an in-scope variable binding\n- it begins with an uppercase character",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11102"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/scope.ts:45"
+      "message": "Missing item type\nThis method handles attribute values that are curlies, as well as curlies nested inside of\ninterpolations:\n\n```hbs\n<a href={{url}} />\n<a href=\"{{url}}.html\" />\n```",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11177"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/scope.ts:47"
+      "message": "Missing item type\nattrPart is the narrowed down list of valid attribute values that are also\nallowed as a concat part (you can't nest concats).",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11216"
     },
     {
-      "message": "Missing item type",
-      "line": " packages/@glimmer/runtime/lib/scope.ts:86"
+      "message": "Missing item type\nThis function classifies the head of an ASTv1.Element into an ASTv2.PathHead (if the\nelement is a component) or `'ElementHead'` (if the element is a simple element).\n\nRules:\n\n1. If the variable is an `@arg`, return an `AtHead`\n2. If the variable is `this`, return a `ThisHead`\n3. If the variable is in the current scope:\n  a. If the scope is the root scope, then return a Free `LocalVarHead`\n  b. Else, return a standard `LocalVarHead`\n4. If the tag name is a path and the variable is not in the current scope, Syntax Error\n5. If the variable is uppercase return a FreeVar(ResolveAsComponentHead)\n6. Otherwise, return `'ElementHead'`",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11311"
     },
     {
       "message": "Missing item type\nUsed to override the mechanism of printing a given AST.Node.\n\nThis will generally only be useful to source -> source codemods\nwhere you would like to specialize/override the way a given node is\nprinted (e.g. you would like to preserve as much of the original\nformatting as possible).\n\nWhen the provided override returns undefined, the default built in printing\nwill be done for the AST.Node.",