Can't transpile a babel macro project

Run next info (available from version 12.0.8 and up)

next info is still not available, but I run npx envinfo --binaries --system:

  System:
    OS: macOS 12.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 76.88 MB / 32.00 GB
    Shell: 3.3.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 16.13.1 - ~/.local/share/nvm/v16.13.1/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.1.2 - ~/.local/share/nvm/v16.13.1/bin/npm

What version of Next.js are you using?

12.0.8-canary.16

What version of Node.js are you using?

v16.13.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

For some reason, Next.js can’t transpile .macro files.

The terminal is reporting something related to an uid, looks like an internal thing:

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Disabled SWC as replacement for Babel because of custom Babel configuration ".babelrc" https://nextjs.org/docs/messages/swc-disabled
event - compiled client and server successfully in 152 ms (144 modules)
wait  - compiling / (client and server)...
info  - Using external babel configuration from /Users/kikobeats/Downloads/with-babel-macros-app/.babelrc
error - ./pages/index.js
TypeError: Cannot read properties of undefined (reading 'uid')
(node:13611) [DEP_WEBPACK_MODULE_ISSUER] DeprecationWarning: Module.issuer: Use new ModuleGraph API
(Use `node --trace-deprecation ...` to show where the warning was created)
wait  - compiling /_error (client and server)...
error - ./pages/index.js
TypeError: Cannot read properties of undefined (reading 'uid')

I think what is happening is since the macro file is called *.macro.js, Next.js is wrongly interpreting it instead of leveraging to babel-plugin-macros for doing the job.

Expected Behavior

The macro should be interpreted by the babel plugin, not being interfered with by the Next.js internal compiler.

To Reproduce

just clone with-babel-macros

[benbender]

@styfle yes, I can confirm that the error is absent in canary 💯

[styfle]

Please try the latest release v12.0.8-canary.19 using yarn add next@canary or npm install next@canary to confirm that the issue is fixed, thanks!