ember-standard-modules.ts

// I'm doing this as a json import because even though that's not standard JS,
// it's relaively easy to consume into builds for the web. As opposed to doing
// something like fs.readFile, which is harder.
//
// @ts-ignore
import mappings from 'ember-rfc176-data/mappings.json';

// these are packages that available to import in standard ember code that don't
// exist as real packages. If a build system encounters them in stage 3, it
// should convert them to runtime AMD require.
//
// Some of them (like @embroider/macros) won't ever be seen in stage 3, because
// earlier plugins should take care of them.
export const emberVirtualPackages = new Set<string>(mappings.map((m: any) => m.module));

// these are *real* packages that every ember addon is allowed to resolve *as if
// they were peerDepenedencies, because the host application promises to have
// these packages. In principle, we could force every addon to declare these as
// real peerDeps all the way down the dependency graph, but in practice that
// makes the migration from v1 to v2 addons more painful than necessary, because
// a v1 addon in between the app and a v2 addon might not declare the peerDep,
// breaking the deeper v2 addon.
export const emberVirtualPeerDeps = new Set<string>(['@glimmer/component', '@glimmer/tracking']);

// this is a real package, even though it's still listed in rfc176
emberVirtualPackages.delete('@ember/string');
emberVirtualPeerDeps.add('@ember/string');

// these can also appear in ember code and should get compiled away by babel,
// but we may need to tell a build tool that is inspecting pre-transpiled code
// (like snowpack) not to worry about these packages.
emberVirtualPackages.add('@glimmer/env');
emberVirtualPackages.add('ember');
emberVirtualPackages.add('ember-testing');

// this is a real package and even though most of its primary API is implemented
// as transforms, it does include some runtime code.
emberVirtualPeerDeps.add('@embroider/macros');

// while people don't manually import from ember-source, our v1-to-v2 conversion
// of ember-source can send requests to here, and therefore any addon might need
// to see it as a peer.
emberVirtualPeerDeps.add('ember-source');

// rfc176-data only covers things up to the point where Ember stopped needing
// the modules-api-polyfill. Newer APIs need to be added here.
emberVirtualPackages.add('@ember/owner');

// Added in ember-source 4.5.0-beta.1
emberVirtualPackages.add('@ember/renderer');

// Not provided by rfc176-data, but is needed for special librarys
// that know the dangers of importing private APIs
emberVirtualPackages.add('@ember/-internals');

// these are not public API but they're included in ember-source, so for
// correctness we still want to understand that they come from there.
emberVirtualPackages.add('@glimmer/validator');
emberVirtualPackages.add('@glimmer/reference');
emberVirtualPackages.add('@glimmer/manager');

// ember-data pre 4.12 failed to declare this as a peer dependency of @ember-data/debug
emberVirtualPeerDeps.add('@ember-data/store');

// These are the known names that people use to import template precomiplation
// macros from.
export const templateCompilationModules = Object.freeze([
  { module: 'htmlbars-inline-precompile', exportedName: 'default' },
  { module: 'ember-cli-htmlbars-inline-precompile', exportedName: 'default' },
  { module: 'ember-cli-htmlbars', exportedName: 'hbs' },
  { module: '@ember/template-precompilation', exportedName: 'precompileTemplate' },
]);