@yunsii whenever non-react macro (t, plural, select, etc) is used in react component, useLingui() hook should be added as well. OR just use JSX macro instead.

That caused a translation mismatch you noticed in the issue.

Here i've just changed it to JSX macro, because it's more appropriate usage.

It means if i don't use i18n, should still call useLingui hook like below?

import { useLingui } from "@lingui/react"
import { plural } from '@lingui/macro'

function App() {
  useLingui()
  //...

  return (
    <p>
      {plural(selected, {
        one: 'Developer',
        other: `Developers`
      })}
    </p>
  )
}

yes. plural / t / select / selectOrdinal macro is simply a syntax sugar over i18n, it is expanded to the i18n._ call during build.

I recommend to use react-related macros whenever possible, because it auto subscribe for a changes and less error-prone.

Theaks for your detail explanation 👌

@yunsii for explicit custom ids lingui@4 requires #. js-lingui-explicit-id comment to be added. This was a root cause why this section was not translated.

The release version of @lingui/swc-plugin was built with a newer version of the swc-core, which is not compatible with next@13.2.3" this caused a "panic" during build. I put a compatible version and added a compatibility notice into readme.