feat: enable importAttributes and explicitResourceManagement for extractor

[timofei-iatsenko]

Description

Enable importAttributes and explicitResourceManagement parser plugins, because they are stage3 now and should be supported out of the box by lingui extractor

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 #2003

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	Comments	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 4, 2024 9:32am

[github-actions]

size-limit report 📦

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

[timofei-iatsenko]

@andrii-bodnar rebased

[andrii-bodnar]

@timofei-iatsenko the CI has failed, please check - https://github.com/lingui/js-lingui/actions/runs/10980398987/job/30486125563?pr=2009

[vonovak]

Just wondering, is this a preparation for future use of these features or what's the reason for this? I assume this doesn't influence consumers in any way, it's just for the tooling that's included in the lingui cli?

[timofei-iatsenko]

We stated in the docs that lingui extractor should understand out of the box valid ecmascript + stage3 features. It's written there

These 2 features became stage3 recently and our extractor fail on them but should not.

[timofei-iatsenko]

@andrii-bodnar all checks are green. Could be merged and deplyed in v4. Apologize that this took so long to finish.