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, but nothing was found.

What it means

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

Source

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

        definition as object,
        expect(owner, 'BUG: expected owner when resolving component definition'),
        false,
        lexical?.at(expr[1])
      )
    );
  } else {
    let {
      symbols: { upvars },
      owner,
    } = assertResolverInvariants(meta);

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

    if (DEBUG && (typeof definition !== 'object' || definition === 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, but nothing was found.`
      );
    }

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

/**
 * (helper)
 * (helper arg)
 */
export function resolveHelper(
  resolver: Nullable<ClassicResolver>,
  constants: ProgramConstants,
  meta: BlockMetadata,
  [, expr, then]: ResolveHelperOp

View on GitHub (pinned to 26f97246a8)

When it happens

Trigger: Thrown at packages/@glimmer/opcode-compiler/lib/opcode-builder/helpers/resolution.ts:134 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/5ac78ec92eabfe2f. Report an issue: GitHub.