emberjs/ember.js · error · Error

Attempted to resolve `${name}`, which was expected to be a c

Error message

Attempted to resolve `${name}`, which was expected to be a component or helper, but nothing was found.

What it means

Error "Attempted to resolve `${name}`, which was expected to be a component or helper, but nothing was found." thrown in emberjs/ember.js.

Source

Thrown at packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:333

    );
  } else {
    let {
      symbols: { upvars },
      owner,
    } = assertResolverInvariants(meta);

    let name = unwrap(upvars[expr[1]]);
    let definition = resolver?.lookupComponent?.(name, owner) ?? null;

    if (definition !== null) {
      ifComponent(constants.resolvedComponent(definition, name));
    } else {
      let helper = resolver?.lookupHelper?.(name, owner) ?? null;

      if (DEBUG && helper === null) {
        assert(!meta.isStrictMode, 'Strict mode errors should already be handled at compile time');

        throw new Error(
          `Attempted to resolve \`${name}\`, which was expected to be a component or helper, but nothing was found.`
        );
      }

      // eslint-disable-next-line @typescript-eslint/no-non-null-assertion -- @fixme
      ifHelper(constants.helper(helper!, name));
    }
  }
}

/**
 * {{maybeHelperOrComponent}}
 */
export function resolveOptionalComponentOrHelper(
  resolver: Nullable<ClassicResolver>,
  constants: ProgramConstants,
  meta: BlockMetadata,
  [, expr, { ifComponent, ifHelper, ifValue }]: ResolveOptionalComponentOrHelperOp

View on GitHub (pinned to 26f97246a8)

When it happens

Trigger: Thrown at packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:333 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of emberjs/ember.js@26f97246a8 (2026-09-01). Data as JSON: /api/errors/39cd694f29444798. Report an issue: GitHub.