Reason for only allowing direct references to in-scope values?

This assertion seems to allow only scopes defined as { foo } or { foo: foo }, but not { foo: bar }. I wonder why that is?

The problem I was running into:

I am using rollup-plugin-glimmer-template-tag and rollup-plugin-ts in a v2 addon, I was importing the default export of a component HeadlessFormFieldComponent under a shorter name, like this:

import FieldComponent from './field';

But during the compilation process (/dist output of v2 addon), this gets implicitly transformed to something like this:

import HeadlessFormFieldComponent from './field';

setComponentTemplate(precompileTemplate(`...`, {
  strictMode: true,
  scope: () => ({
    FieldComponent: HeadlessFormFieldComponent
  })

Idk why this is being done, but it seems perfectly valid from a pure JS standpoint. But the babel plugin then throws Scope objects for precompileTemplate may only contain direct references to in-scope values, e.g. { FieldComponent } or { FieldComponent: FieldComponent }

Similar things happen when you import by assigning an alias, like

import { EnsureSafeComponentHelper as ensureSafeComponent } from '@embroider/util';

...which gets rewritten to

import { EnsureSafeComponentHelper } from '@embroider/util';

setComponentTemplate(precompileTemplate(`...`, {
  strictMode: true,
  scope: () => ({
    ensureSafeComponent: EnsureSafeComponentHelper
  })

emberjs / babel-plugin-ember-template-compilation

Reason for only allowing direct references to in-scope values? #14