ember-source 7.1.0-alpha.2 → 7.1.0-alpha.4

package/docs/data.json

@@ -3,7 +3,7 @@
     "name": "The Ember API",
     "description": "The Ember API: a framework for building ambitious web applications",
     "url": "https://emberjs.com/",
-    "version": "7.1.0-alpha.2"
+    "version": "7.1.0-alpha.4"
   },
   "files": {
     "node_modules/rsvp/lib/rsvp/promise/all.js": {
@@ -2148,6 +2148,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/runtime/lib/helpers/eq.ts": {
+      "name": "packages/@glimmer/runtime/lib/helpers/eq.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/runtime/lib/helpers/fn.ts": {
       "name": "packages/@glimmer/runtime/lib/helpers/fn.ts",
       "modules": {},
@@ -2169,6 +2176,13 @@
       "fors": {},
       "namespaces": {}
     },
+    "packages/@glimmer/runtime/lib/helpers/neq.ts": {
+      "name": "packages/@glimmer/runtime/lib/helpers/neq.ts",
+      "modules": {},
+      "classes": {},
+      "fors": {},
+      "namespaces": {}
+    },
     "packages/@glimmer/runtime/lib/modifiers/on.ts": {
       "name": "packages/@glimmer/runtime/lib/modifiers/on.ts",
       "modules": {},
@@ -2939,7 +2953,7 @@
       "namespaces": {},
       "tag": "module",
       "file": "packages/@ember/debug/index.ts",
-      "line": 142,
+      "line": 143,
       "access": "public",
       "tagname": ""
     },
@@ -6337,7 +6351,20 @@
     },
     {
       "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 63,
+      "line": 59,
+      "description": "The `LOG_INSPECTOR_HINT` property, when true, tells Ember to log a hint\nsuggesting the Ember Inspector browser extension when it is not detected.",
+      "itemtype": "property",
+      "name": "LOG_INSPECTOR_HINT",
+      "type": "Boolean",
+      "default": "true",
+      "access": "public",
+      "tagname": "",
+      "class": "EmberENV",
+      "module": "rsvp"
+    },
+    {
+      "file": "packages/@ember/-internals/environment/lib/env.ts",
+      "line": 75,
       "description": "Whether to perform extra bookkeeping needed to make the `captureRenderTree`\nAPI work.\n\nThis has to be set before the ember JavaScript code is evaluated. This is\nusually done by setting `window.EmberENV = { _DEBUG_RENDER_TREE: true };`\nbefore the \"vendor\" `<script>` tag in `index.html`.\n\nSetting the flag after Ember is already loaded will not work correctly. It\nmay appear to work somewhat, but fundamentally broken.\n\nThis is not intended to be set directly. Ember Inspector will enable the\nflag on behalf of the user as needed.\n\nThis flag is always on in development mode.\n\nThe flag is off by default in production mode, due to the cost associated\nwith the the bookkeeping work.\n\nThe expected flow is that Ember Inspector will ask the user to refresh the\npage after enabling the feature. It could also offer a feature where the\nuser add some domains to the \"always on\" list. In either case, Ember\nInspector will inject the code on the page to set the flag if needed.",
       "itemtype": "property",
       "name": "_DEBUG_RENDER_TREE",
@@ -6350,7 +6377,7 @@
     },
     {
       "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 95,
+      "line": 107,
       "description": "Whether to force all deprecations to be enabled. This is used internally by\nEmber to enable deprecations in tests. It is not intended to be set in\nprojects.",
       "itemtype": "property",
       "name": "_ALL_DEPRECATIONS_ENABLED",
@@ -6363,7 +6390,7 @@
     },
     {
       "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 108,
+      "line": 120,
       "description": "Override the version of ember-source used to determine when deprecations \"break\".\nThis is used internally by Ember to test with deprecated features \"removed\".\nThis is never intended to be set by projects.",
       "itemtype": "property",
       "name": "_OVERRIDE_DEPRECATION_VERSION",
@@ -6376,7 +6403,7 @@
     },
     {
       "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 120,
+      "line": 132,
       "description": "Whether the app defaults to using async observers.\n\nThis is not intended to be set directly, as the implementation may change in\nthe future. Use `@ember/optional-features` instead.",
       "itemtype": "property",
       "name": "_DEFAULT_ASYNC_OBSERVERS",
@@ -6389,7 +6416,7 @@
     },
     {
       "file": "packages/@ember/-internals/environment/lib/env.ts",
-      "line": 134,
+      "line": 146,
       "description": "Controls the maximum number of scheduled rerenders without \"settling\". In general,\napplications should not need to modify this environment variable, but please\nopen an issue so that we can determine if a better default value is needed.",
       "itemtype": "property",
       "name": "_RERENDER_LOOP_LIMIT",
@@ -13297,7 +13324,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 147,
+      "line": 148,
       "description": "Display a debug notice.\n\nCalls to this function are not invoked in production builds.\n\n```javascript\nimport { debug } from '@ember/debug';\n\ndebug('I\\'m a debug notice!');\n```",
       "itemtype": "method",
       "name": "debug",
@@ -13316,7 +13343,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 168,
+      "line": 169,
       "description": "Display an info notice.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.",
       "itemtype": "method",
       "name": "info",
@@ -13327,7 +13354,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 187,
+      "line": 188,
       "description": "Alias an old, deprecated method with its new counterpart.\n\nDisplay a deprecation warning with the provided message and a stack trace\n(Chrome and Firefox only) when the assigned method is called.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.\n\n```javascript\nimport { deprecateFunc } from '@ember/debug';\n\noldMethod = deprecateFunc('Please use the new, updated method', options, newMethod);\n```",
       "itemtype": "method",
       "name": "deprecateFunc",
@@ -13361,7 +13388,7 @@
     },
     {
       "file": "packages/@ember/debug/index.ts",
-      "line": 232,
+      "line": 233,
       "description": "Run a function meant for debugging.\n\nCalls to this function are removed from production builds, so they can be\nfreely added for documentation and debugging purposes without worries of\nincuring any performance penalty.\n\n```javascript\nimport Component from '@ember/component';\nimport { runInDebug } from '@ember/debug';\n\nrunInDebug(() => {\n  Component.reopen({\n    didInsertElement() {\n      console.log(\"I'm happy\");\n    }\n  });\n});\n```",
       "itemtype": "method",
       "name": "runInDebug",
@@ -13909,7 +13936,7 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 17,
+      "line": 19,
       "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",
@@ -13936,7 +13963,7 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 71,
+      "line": 73,
       "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",
@@ -13964,7 +13991,7 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 265,
+      "line": 267,
       "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.",
       "itemtype": "method",
       "name": "invokeHelper",
@@ -13996,53 +14023,107 @@
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 337,
+      "line": 339,
       "description": "Using the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```\nimport { hash } from '@ember/helper';\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```\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `hash` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 358,
+      "line": 360,
       "description": "Using the `{{array}}` helper, you can pass arrays directly from the template\nas an argument to your components.\n\n```js\nimport { array } from '@ember/helper';\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\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `array` to use it (it is a built-in when\nwriting standalone `.hbs` files).\n```",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 381,
+      "line": 383,
       "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.\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `concat` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 406,
+      "line": 408,
       "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.\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `concat` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 451,
+      "line": 453,
       "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```",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 473,
+      "line": 475,
       "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.",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
     {
       "file": "packages/@ember/helper/index.ts",
-      "line": 493,
+      "line": 495,
       "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```",
       "class": "@ember/helper",
       "module": "@ember/helper"
     },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 516,
+      "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"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "@ember/helper",
+      "module": "@ember/helper"
+    },
+    {
+      "file": "packages/@ember/helper/index.ts",
+      "line": 540,
+      "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"
+      },
+      "access": "public",
+      "tagname": "",
+      "class": "@ember/helper",
+      "module": "@ember/helper"
+    },
     {
       "file": "packages/@ember/instrumentation/index.ts",
       "line": 107,
@@ -21478,28 +21559,28 @@
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
-      "line": 145,
+      "line": 142,
       "description": "(helper)\n(helper arg)",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
-      "line": 195,
+      "line": 189,
       "description": "<div {{modifier}}/>\n<div {{modifier arg}}/>\n<Foo {{modifier}}/>",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
-      "line": 264,
+      "line": 252,
       "description": "{{component-or-helper arg}}",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts",
-      "line": 360,
+      "line": 342,
       "description": "{{maybeHelperOrComponent}}",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
@@ -21763,6 +21844,13 @@
       "class": "@glimmer/tracking",
       "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": 13,
@@ -21807,6 +21895,13 @@
       "class": "@glimmer/tracking",
       "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",
+      "module": "@glimmer/component"
+    },
     {
       "file": "packages/@glimmer/runtime/lib/modifiers/on.ts",
       "line": 249,
@@ -22478,161 +22573,173 @@
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 6845,
+      "line": 6840,
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 6849,
       "description": "Validate that the character offset represents a position in the source string.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 7820,
+      "line": 6916,
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/syntax/dist/es/index.js",
+      "line": 7827,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9349,
+      "line": 9356,
       "description": "ASTPlugins can make changes to the Glimmer template AST before\ncompilation begins.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9417,
+      "line": 9424,
       "description": "Gets the correct Token from the Node based on it's type",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9460,
+      "line": 9467,
       "description": "Adds tokens to the tokensSet based on their node.type",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9473,
+      "line": 9480,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9536,
+      "line": 9543,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9596,
+      "line": 9603,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9633,
+      "line": 9640,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9657,
+      "line": 9664,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9685,
+      "line": 9692,
       "description": "Corresponds to a single named argument.\n\n```hbs\nx=<expr>\n```",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9703,
+      "line": 9710,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9712,
+      "line": 9719,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9717,
+      "line": 9724,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9722,
+      "line": 9729,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9733,
+      "line": 9740,
       "description": "Corresponds to an argument passed by a component (`@x=<value>`)",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9737,
+      "line": 9744,
       "description": "Convert the component argument into a named argument node",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9748,
+      "line": 9755,
       "description": "An `ElementModifier` is just a normal call node in modifier position.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9753,
+      "line": 9760,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9780,
+      "line": 9787,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9794,
+      "line": 9801,
       "description": "Corresponds to a simple HTML element. The AST allows component arguments and modifiers to support\nfuture extensions.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9808,
+      "line": 9815,
       "description": "A Handlebars literal.\n\n{@link https://handlebarsjs.com/guide/expressions.html#literal-segments}",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9814,
+      "line": 9821,
       "description": "Corresponds to a Handlebars literal.",
       "see": [
         "{LiteralValue}"
@@ -22642,189 +22749,189 @@
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9827,
+      "line": 9834,
       "description": "Returns true if an input {@see ExpressionNode} is a literal.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9844,
+      "line": 9851,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9858,
+      "line": 9865,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9866,
+      "line": 9873,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9878,
+      "line": 9885,
       "description": "Corresponds to an interpolation in attribute value position.\n\n```hbs\n<a href=\"{{url}}.html\"\n```",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9887,
+      "line": 9894,
       "description": "Corresponds to an entire template.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9892,
+      "line": 9899,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9898,
+      "line": 9905,
       "description": "Corresponds to a collection of named blocks.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9902,
+      "line": 9909,
       "description": "Get the `NamedBlock` for a given name.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9910,
+      "line": 9917,
       "description": "Corresponds to a single named block. This is used for anonymous named blocks (`default` and\n`else`).",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9924,
+      "line": 9931,
       "description": "Corresponds to `this` at the head of an expression.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9929,
+      "line": 9936,
       "description": "Corresponds to `@<ident>` at the beginning of an expression.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9934,
+      "line": 9941,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9940,
+      "line": 9947,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9957,
+      "line": 9964,
       "description": "A free variable is resolved according to a resolution rule:\n\n1. Strict resolution\n2. Namespaced resolution",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9965,
+      "line": 9972,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9984,
+      "line": 9991,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 9991,
+      "line": 9998,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10003,
+      "line": 10010,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10021,
+      "line": 10028,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10068,
+      "line": 10075,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10619,
+      "line": 10626,
       "description": "This corresponds to attribute curlies (<Foo bar={{...}}>).\nIn strict mode, this also corresponds to arg curlies.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10631,
+      "line": 10638,
       "description": "This corresponds to append positions text curlies.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10645,
+      "line": 10652,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10702,
+      "line": 10709,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10784,
+      "line": 10791,
       "description": "An `ExpressionNormalizer` normalizes expressions within a block.\n\n`ExpressionNormalizer` is stateless.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10794,
+      "line": 10801,
       "description": "The `normalize` method takes an arbitrary expression and its original syntax context and\nnormalizes it to an ASTv2 expression.",
       "see": [
         "{SyntaxContext}"
@@ -22834,63 +22941,63 @@
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10848,
+      "line": 10855,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10890,
+      "line": 10897,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 10941,
+      "line": 10948,
       "description": "`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11019,
+      "line": 11026,
       "description": "Normalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11059,
+      "line": 11066,
       "description": "Normalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11102,
+      "line": 11109,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11177,
+      "line": 11184,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11216,
+      "line": 11223,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/dist/es/index.js",
-      "line": 11311,
+      "line": 11318,
       "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"
@@ -23329,11 +23436,23 @@
     },
     {
       "file": "packages/@glimmer/syntax/lib/source/source.ts",
-      "line": 22,
+      "line": 15,
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/component"
+    },
+    {
+      "file": "packages/@glimmer/syntax/lib/source/source.ts",
+      "line": 26,
       "description": "Validate that the character offset represents a position in the source string.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
+    {
+      "file": "packages/@glimmer/syntax/lib/source/source.ts",
+      "line": 91,
+      "class": "@glimmer/tracking",
+      "module": "@glimmer/component"
+    },
     {
       "file": "packages/@glimmer/syntax/lib/traversal/visitor.ts",
       "line": 20,
@@ -23826,56 +23945,56 @@
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 309,
+      "line": 306,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 356,
+      "line": 353,
       "description": "`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 445,
+      "line": 442,
       "description": "Normalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 493,
+      "line": 490,
       "description": "Normalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
       "class": "@glimmer/tracking",
       "module": "@glimmer/component"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 547,
+      "line": 544,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 632,
+      "line": 629,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 675,
+      "line": 672,
       "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"
     },
     {
       "file": "packages/@glimmer/syntax/lib/v2/normalize.ts",
-      "line": 783,
+      "line": 780,
       "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"
@@ -24259,7 +24378,7 @@
     },
     {
       "message": "replacing incorrect tag: returns with return",
-      "line": " packages/@ember/helper/index.ts:265"
+      "line": " packages/@ember/helper/index.ts:267"
     },
     {
       "message": "unknown tag: internal",
@@ -24931,31 +25050,31 @@
     },
     {
       "message": "Missing item type\nUsing the `{{hash}}` helper, you can pass objects directly from the template\nas an argument to your components.\n\n```\nimport { hash } from '@ember/helper';\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```\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `hash` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
-      "line": " packages/@ember/helper/index.ts:337"
+      "line": " packages/@ember/helper/index.ts:339"
     },
     {
       "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\nimport { array } from '@ember/helper';\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\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `array` to use it (it is a built-in when\nwriting standalone `.hbs` files).\n```",
-      "line": " packages/@ember/helper/index.ts:358"
+      "line": " packages/@ember/helper/index.ts:360"
     },
     {
       "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.\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `concat` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
-      "line": " packages/@ember/helper/index.ts:381"
+      "line": " packages/@ember/helper/index.ts:383"
     },
     {
       "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.\n\n**NOTE:** this example uses the experimental `<template>` feature, which is\nthe only place you need to import `concat` to use it (it is a built-in when\nwriting standalone `.hbs` files).",
-      "line": " packages/@ember/helper/index.ts:406"
+      "line": " packages/@ember/helper/index.ts:408"
     },
     {
       "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:451"
+      "line": " packages/@ember/helper/index.ts:453"
     },
     {
       "message": "Missing item type\nThe `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": " packages/@ember/helper/index.ts:473"
+      "line": " packages/@ember/helper/index.ts:475"
     },
     {
       "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:493"
+      "line": " packages/@ember/helper/index.ts:495"
     },
     {
       "message": "Missing item type",
@@ -25819,19 +25938,19 @@
     },
     {
       "message": "Missing item type\n(helper)\n(helper arg)",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:145"
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:142"
     },
     {
       "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:195"
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:189"
     },
     {
       "message": "Missing item type\n{{component-or-helper arg}}",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:264"
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:252"
     },
     {
       "message": "Missing item type\n{{maybeHelperOrComponent}}",
-      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:360"
+      "line": " packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:342"
     },
     {
       "message": "Missing item type\nCompile arguments, pushing an Arguments object onto the stack.",
@@ -25901,6 +26020,14 @@
       "message": "Missing item type",
       "line": " packages/@glimmer/runtime/lib/component/interfaces.ts:8"
     },
+    {
+      "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\nPerforms a strict inequality comparison.\n\nleft !== right",
+      "line": " packages/@glimmer/runtime/lib/helpers/neq.ts:3"
+    },
     {
       "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:131"
@@ -26269,241 +26396,249 @@
       "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",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6840"
+    },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6849"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/syntax/dist/es/index.js:6916"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:7827"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9356"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9424"
     },
     {
       "message": "Missing item type\nAdds tokens to the tokensSet based on their node.type",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9460"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9467"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9480"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9543"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9603"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9640"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9664"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9692"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9710"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9719"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9724"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9729"
     },
     {
       "message": "Missing item type\nCorresponds to an argument passed by a component (`@x=<value>`)",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9733"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9740"
     },
     {
       "message": "Missing item type\nConvert the component argument into a named argument node",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9737"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9744"
     },
     {
       "message": "Missing item type\nAn `ElementModifier` is just a normal call node in modifier position.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9748"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9755"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9760"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9787"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9801"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9815"
     },
     {
       "message": "Missing item type\nCorresponds to a Handlebars literal.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9814"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9821"
     },
     {
       "message": "Missing item type\nReturns true if an input {@see ExpressionNode} is a literal.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9827"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9834"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9851"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9865"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9873"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9885"
     },
     {
       "message": "Missing item type\nCorresponds to an entire template.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9887"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9894"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9899"
     },
     {
       "message": "Missing item type\nCorresponds to a collection of named blocks.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9898"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9905"
     },
     {
       "message": "Missing item type\nGet the `NamedBlock` for a given name.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9902"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9909"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9917"
     },
     {
       "message": "Missing item type\nCorresponds to `this` at the head of an expression.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9924"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9931"
     },
     {
       "message": "Missing item type\nCorresponds to `@<ident>` at the beginning of an expression.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:9929"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9936"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9941"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9947"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9964"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9972"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9991"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:9998"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10010"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10028"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10075"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10626"
     },
     {
       "message": "Missing item type\nThis corresponds to append positions text curlies.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:10631"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10638"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10652"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10709"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10791"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10801"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10855"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10897"
     },
     {
       "message": "Missing item type\n`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:10941"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:10948"
     },
     {
       "message": "Missing item type\nNormalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:11019"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11026"
     },
     {
       "message": "Missing item type\nNormalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
-      "line": " packages/@glimmer/syntax/dist/es/index.js:11059"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11066"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11109"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11184"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11223"
     },
     {
       "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"
+      "line": " packages/@glimmer/syntax/dist/es/index.js:11318"
     },
     {
       "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.",
@@ -26741,9 +26876,17 @@
       "message": "Missing item type",
       "line": " packages/@glimmer/syntax/lib/source/location.ts:29"
     },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/syntax/lib/source/source.ts:15"
+    },
     {
       "message": "Missing item type\nValidate that the character offset represents a position in the source string.",
-      "line": " packages/@glimmer/syntax/lib/source/source.ts:22"
+      "line": " packages/@glimmer/syntax/lib/source/source.ts:26"
+    },
+    {
+      "message": "Missing item type",
+      "line": " packages/@glimmer/syntax/lib/source/source.ts:91"
     },
     {
       "message": "Missing item type",
@@ -27015,35 +27158,35 @@
     },
     {
       "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/lib/v2/normalize.ts:309"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:306"
     },
     {
       "message": "Missing item type\n`TemplateNormalizer` normalizes top-level ASTv1 statements to ASTv2.",
-      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:356"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:353"
     },
     {
       "message": "Missing item type\nNormalizes an ASTv1.MustacheStatement to an ASTv2.AppendStatement",
-      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:445"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:442"
     },
     {
       "message": "Missing item type\nNormalizes a ASTv1.BlockStatement to an ASTv2.BlockStatement",
-      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:493"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:490"
     },
     {
       "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/lib/v2/normalize.ts:547"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:544"
     },
     {
       "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/lib/v2/normalize.ts:632"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:629"
     },
     {
       "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/lib/v2/normalize.ts:675"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:672"
     },
     {
       "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/lib/v2/normalize.ts:783"
+      "line": " packages/@glimmer/syntax/lib/v2/normalize.ts:780"
     },
     {
       "message": "Missing item type\nGets the correct Token from the Node based on it's type",