feat: allow extract to work with i18n._ calls not created from macro

[mitchjhill]

This change updates babel-plugin-extract-messages so that it will pick up usages of the i18n._ method from @lingui/core directly.

This solves the issues mentioned in #1178 and #1224 (comment) without needing the workaround listed in 1178 (prefixing the id with /*i18n*/).

The main driver for this is to allow use of Lingui without macros, so that sites running on Next.js can use the SWC compiler instead of babel.

Aware that this is effectively adding back extract behavior that was removed previously, but hopefully this isn't too big of a deal - let me know if you have any feedback.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
js-lingui	❌ Failed (Inspect)		Dec 6, 2022 at 0:17AM (UTC)

[capaj]

@mitchjhill just wanted to say

[timofei-iatsenko]

I would highly discourage you using this. Use macro whenever possible. If not possible, use https://formatjs.io/

PS Lingui already supports SWC https://github.com/lingui/swc-plugin

[capaj]

@thekip I had no idea about the SWC plugin! That looks gr8. Will try that out when I touch i18n next time.

[timofei-iatsenko]

why would you want to use lingui without a macro?

[capaj]

I want to use it on backend. Backend is plain typescript. We don't even run babel and we don't want to run babel.
We're sending quite a few push notifications from our BE. At the moment it's just maybe 70 strings, but it will be more in the future.

[capaj]

I just tried running SWC and that does not work for us, because SWC handles decorators a bit differently.

[timofei-iatsenko]

I just tried running SWC and that does not work for us, because SWC handles decorators a bit differently.

Probably related: nestjs/graphql#2568