Expose macros config in babel

[NullVoxPopuli]

@embroider/macros were not configurable in main/vite before this change.

Proposed way of configuring macros is similar to how we've been doing so in ember-cli-build.js

removed from this PR

If we do end up needing this in the future,

we should have compat-macros output their combined options to compat-app-builder -> addBabelCompat

rather than the output,

and then have the babel plugin from compat read that in and it could then merge the options.

---

For example, in the babel config:

const {
  babelCompatSupport,
  templateCompatSupport,
} = require("@embroider/compat/babel");

module.exports = {
  plugins: [
   // ... 
    ...babelCompatSupport({
      '@embroider/macros': {
        setOwnConfig: {},
        setConfig: {
          'library-name': {}
        },
      }
    }),
  ],
  // ...
};

However, this doesn't solve the problem of configuring macros for the minimal app over in #2205

For the minimal app blueprint, we'd have folks do this in their babel config:

const {
  babelCompatSupport,
  templateCompatSupport,
} = require("@embroider/compat/babel");

const { MacrosConfig } = require('@embroider/macros/src/macros-config');

let root = process.cwd();
let macros = MacrosConfig.for({}, root);
let { plugins: templateMacros, setConfig } = MacrosConfig.transforms();

setConfig(macros);

macros.setOwnConfig(root, { /* ... */ });
macros.setConfig(root, 'library-a', { /* ... */ });
macros.setConfig(root, 'library-b', { /* ... */ });

if (process.env.NODE_ENV === 'development') {
  macros.enablePackageDevelopment(process.cwd());
  macros.enableRuntimeMode();
}

macros.finalize();


module.exports = {
  plugins: [
    [
      "babel-plugin-ember-template-compilation",
      {
        compilerPath: "ember-source/dist/ember-template-compiler.js",
        transforms: [...templateMacros],
      },
    ],

   // ... 
   macros.babelPluginConfig();
  ],
  // ...
};

which.... could be better...

So.... I've done added to macros to allow for:

const { buildMacros } = require('@embroider/macros/babel'); 

const macros = buildMacros({
  // this is how you configure your own package
  setOwnConfig: {
    // your config goes here
  },
  // this is how you can optionally send configuration into your
  // dependencies, if those dependencies choose to use
  // @embroider/macros configs.
  setConfig: {
    'some-dependency': {
      // config for some-dependency
    },
  },
});

module.exports = {
  plugins: [
   // ... 
    [
      "babel-plugin-ember-template-compilation",
      {
        compilerPath: "ember-source/dist/ember-template-compiler.js",
        transforms: [...macros.templateMacros],
      },
    ],
    ...macros.babelMacros,
  ],
  // ...
};

Which should be nice for the minimal blueprint in #2205

[ef4]

Notes from discussion at office hours:

• we should make the argument to babelCompatSupport work even if you're using a prebuild, and we think that doesn't work now because when there's a prebuild the entire macros config gets built into babel_compat.js ahead of time and your options are ignored.

[NullVoxPopuli]

I think in order to do that we need to have the classic macros config, in ember-cli-build.js, load the babel config.

It's too intense to re-apply the options post-macros-creation.

[NullVoxPopuli]

err no, it'd just be the same problem, but in reverse

[NullVoxPopuli]

Update: I removed the changes to babelCompatSupport(), and updated the description with notes from our meeting today for if/when we want to add in the merging

[simonihmig]

Do we want people to import everything from src? Or is this for backwards compatibility, because people were doing so before?