feat(macro): deprecate custom i18n instance on t macro

[timofei-iatsenko]

Description

As stated in the migration doc. There few ways to achieve the same result, it's better to stick with the one for consistency. As a benefit we can remove significant layer of complexity from SWC / babel / Eslint integrations.

I've created a GritQL migration and test in the studio only. I don't know how to correctly run this migration in the users codebase, once i figure it out i will update gist or the doc.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Examples update

Fixes # (issue)

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

[vercel]

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

Name	Status	Preview	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	Nov 6, 2024 3:02pm

[github-actions]

size-limit report 📦

Path	Size
./packages/core/dist/index.mjs	3.09 KB (0%)
./packages/detect-locale/dist/index.mjs	723 B (0%)
./packages/react/dist/index.mjs	1.65 KB (0%)
./packages/remote-loader/dist/index.mjs	7.26 KB (0%)

[morgante]

I've created a GritQL migration and test in the studio only. I don't know how to correctly run this migration in the users codebase, once i figure it out i will update gist or the doc.

If you make a markdown file in this repo .grit/patterns/migrate_t.md then users will just be able to apply it like this:

grit apply github.com/lingui/js-lingui#migrate_t

Thanks for trying Grit!