V5 Roadmap

[andrii-bodnar]

It's been a while since the latest v4 release and I'm suggesting to start gathering a list of things that might be included in the future v5 major release:

• RFC: Split macro to vanilla js + react #1361
• NextJS App Router and RSC Support path #1698
• Stable Dependency tree crawling
• Consider a better whitespace processing algorithm (Whitespace processing #1873)
• Remove the isTranslated property from TransNoContext (chore: remove the deprecated 'isTranslated' property #1907)
• Remove other deprecations
• Node 20
• Update examples
• Review the documentation docs: various chores #2078
  • Introduction docs: improve introduction #2062
  • Unify Installation instructions docs: refactor installation instructions #2060
  • Tutorials docs: Tutorials section improvements #2075
  • Guides docs: Guides section improvements #2063
  • API Reference docs: @lingui/macro article refinement #2055 docs: improve Tooling and API Reference sections #2065
  • Tooling docs: improve Tooling and API Reference sections #2065
  • Sync & Collaboration Tools docs: prettify sync & collaboration tools section #2061
  • Resources docs: Resources section improvements #2064
  • v5 Migration Guide docs: improve the v5 migration guide #2077
• Blog Post docs: v5 release blog post #2079

[EnablingLogic]

I don't know if this is the place to ask this, but would it be possible to consider taking the SWC plugin out of beta?

[timofei-iatsenko]

From our side we consider it as stable, but from the SWC itself plugins are still experimental, so we could do nothing about it.

[EnablingLogic]

Ah, that's good to know! Lingui seems to be the only library to take SWC seriously, so it'd be a shame if support for @lingui/swc-plugin would be dropped.

[timofei-iatsenko]

I'm going to support it as long as I can. No plans to drop it.

[trevcodesjs]

Are there any plans to move the experimental extractor out of the experimental phase?

[timofei-iatsenko]

We've discussed it today, and we are not plan to do it for V5 version. Because to make it properly some refactoring should be done to the lingui packages. We also didn't gather enough feedback to confidently say that this is not experimental anymore.

Pls give it a try, and let us know how it worked for you. We need that feedback from community to make it stable.

[andrii-bodnar]

Have some ideas for improving the documentation. At the same time going to review everything before the v5 release.

[andrii-bodnar]

Also, I plan to write a v5 Blog post.

[PatrickRogg]

Hey guys,

thanks for your work on the v5 release. Would it be possible to make the v5 of lingui/swc-plugin compatible with swc core v0.98.x?

I can use the v5 of the swc-plugin with next.js 15.0.0-canary.195, but in my node.js backend I'm told that the swc_core version 1.7.36 is not compatible with "@lingui/swc-plugin": "^5.0.0-next.1",

Caused by:
0: failed to invoke `@lingui/swc-plugin` as js transform plugin at @lingui/swc-plugin
1: failed to run Wasm plugin transform. Please ensure the version of `swc_core` used by the plugin is compatible with the host runtime. See the documentation for compatibility information. If you are an author of the plugin, please update `swc_core` to the compatible version.

Thanks for your help.

[andrii-bodnar]

Hello, It's probably related to this - lingui/swc-plugin#119