@emotion/babel-plugin 11.11.x causes error: "Unexpected falsy value: undefined"

[Nantris]

Current behavior:

Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Unexpected falsy value: undefined

To reproduce:

Unknown, but upgrading to @emotion/[email protected] is a prerequisite, as is using babel-loader in Webpack.

Expected behavior:

Upgrading from 11.10.x to 11.11.x should not cause errors.
Environment information:

• react version: 18.2.0
• @emotion/react version: 11.11.4

[Nantris]

Same issue with 11.12.0 - I can only get the project to work if I explicitly install 11.10.8, even though simultaneously @emotion/[email protected] is installing 11.12.0 alongside it. I have no idea why this works and I'm sure it's not optimal, but this issue prevents us from upgrading to 11.12/11.13 and then #3300 prevents us from upgrading to a version where this issue seems to be resolved.

@Andarist I wonder if you have any thoughts? The problems we're seeing with Emotion are starting to compound.

[Nantris]

Works fine also with Yarn resolutions setting @emotion/babel-plugin to 11.10.8 - fully excluding any later versions of @emotion/babel-plugin.

[Nantris]

One last note; our config of the Babel plugin:

   const IS_DEV = api.env() === 'development';
   // ....
      [
        '@emotion',
        { sourceMap: !!IS_DEV, autoLabel: IS_DEV ? 'always' : 'never' },
      ], // MUST come first (as per Emotion docs)

I confirmed