Sudden "Attempted to call a translation function without setting a locale." errors after upgrading from 5.1.2 to 5.2

[tobimori]

Describe the bug
After upgrading the Lingui version, I suddenly get the following error:

Error: Lingui: Attempted to call a translation function without setting a locale.
Make sure to call `i18n.activate(locale)` before using Lingui functions.
This issue may also occur due to a race condition in your initialization logic.

To Reproduce
In entry.server.tsx and entry.client.tsx, I do call:

	const { messages } = await import(`../locales/${locale}.po`)
    i18n.loadAndActivate({ locale, messages })

In my routes I have several "top level" variables (not defined in loader/action or the react component) that use macros, like:

const columns = [
	{ name: t`Name`, width: 25, id: 'name', icon: 'rename', isRowHeader: true, allowsSorting: true },
] as const satisfies Columns

They might be the cause of this. I have 100s of those in the app and they worked fine with a previous lingui version.

In case you're clueless about this, I'm happy to tinker together a reproducible example.

Expected behavior
Same behaviour in 5.2 as in 5.1.2.

Additional context
React Router 7 + Vite app with vite-plugin-babel-macros & @lingui/vite-plugin

[tobimori]

Right, I should've looked in the release notes... The error was purposefully introduced in #2131.
This is a huge breaking change for me, I have not noticed any issues with my usage of Lingui.

Maybe they could be a way to disable it using a compiler flag?

[tobimori]

Nevermind, I'm stupid. The solution is to use msg.