feat(apollo-react): add i18n support for canvas components [MST-8210]

[david-rios-uipath]

Summary

• Add Lingui localization to the formatting toolbar tooltips with a new canvas locale catalog (13 locales)
• Migrate Lingui compiled locale output from CJS (module.exports) to ESM (export const messages) for better compatibility w/ Storybook
• Configure the Lingui Babel macro plugin for Storybook and vitest

CJS → ESM locale migration

Lingui's default compileNamespace is cjs, which outputs module.exports = {...}. This caused two problems:

1. Storybook (Vite dev server) serves .js files as ESM, so CJS locale files failed with does not provide an export named 'default'
2. locale-registry.ts used ESM import syntax with @ts-expect-error suppressions to work around the CJS/ESM mismatch

Setting compileNamespace: 'es' in lingui.config.ts fixes both issues:

• Compiled locales are now .mjs with proper export const messages = ...
• locale-registry.ts uses clean typed named imports — no @ts-expect-error needed
• Added lingui-locale.d.ts type declaration for .mjs imports
• Removed the lingui-cjs-to-esm Vite workaround plugin from Storybook
• Added **/locales/*.mjs to .gitignore (compiled output, same as the old .js files)

Storybook Lingui support

• Added @vitejs/plugin-react with @lingui/babel-plugin-lingui-macro to Storybook's Vite config (scoped to apollo-react/src/ only)
• Added root-level lingui.config.ts re-export so the Babel plugin can find the config from any workspace cwd

Test plan

• Run pnpm i18n:compile && pnpm test in packages/apollo-react — verify locale compilation and tests pass
• Run Storybook (pnpm storybook) — verify sticky note stories render without locale errors
• Verify FormattingToolbar tooltips display localized text

🤖 Generated with Claude Code

[github-actions]

Dependency License Review

• ✅ 1949 package(s) scanned
• ✅ No license issues found
• ⚠️ 4 package(s) excluded (see details below)

License distribution

License	Packages
MIT	1708
ISC	89
Apache-2.0	61
BSD-3-Clause	28
BSD-2-Clause	23
BlueOak-1.0.0	8
MPL-2.0	5
MIT OR Apache-2.0	3
MIT-0	3
CC0-1.0	3
LGPL-3.0-or-later	2
Unknown	2
(MIT OR Apache-2.0)	2
Unlicense	2
Python-2.0	1
CC-BY-4.0	1
(MPL-2.0 OR Apache-2.0)	1
Artistic-2.0	1
(WTFPL OR MIT)	1
(BSD-2-Clause OR MIT OR Apache-2.0)	1
CC-BY-3.0	1
0BSD	1
(MIT OR CC0-1.0)	1
MIT AND ISC	1

Excluded packages

Package	Version	License	Reason
@img/sharp-libvips-linux-x64	1.2.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
@img/sharp-libvips-linuxmusl-x64	1.2.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
@uipath/proteus-client	0.1.10	Unknown	UiPath internal package, Proprietary license
khroma	2.1.0	Unknown	MIT per GitHub repo, missing license field in package.json

[CalinaCristian]

Can you validate ap-chat (in web packages) still works properly? I think I chose cjs vs esm for some issues that were caused there.. if you run dev mode and switch language, does it actually switch?

[david-rios-uipath]

It seems to be working as expected when run from web-packages after some changes to the locale copy script:

Screen.Recording.2026-04-01.at.10.45.52.PM.mov

[github-actions]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (PT)
apollo-canvas	🟢 Ready	Preview, Logs	Apr 13, 2026, 03:20:31 PM
apollo-landing	🟢 Ready	Preview, Logs	Apr 13, 2026, 03:18:12 PM
apollo-ui-react	🟢 Ready	Preview, Logs	Apr 13, 2026, 03:19:28 PM
apollo-vertex	🟢 Ready	Preview, Logs	Apr 13, 2026, 03:19:29 PM
apollo-wind	🟢 Ready	Preview, Logs	Apr 13, 2026, 03:19:16 PM

[david-rios-uipath]

Not a huge fan of ancestor directory reference path -- should I create an alias for i18n?

[CalinaCristian]

I think it's fine for now, we can come back to this (I think we are using a mixed pattern)

[BenGSchulz]

Heads up: apollo-react v4 breaking change landed on main

main now contains a breaking change that bumps apollo-react to v4.x — see #482 (feat(apollo-react)!: canvas wind integration [MST-8290]). Your PR targets main, so when it merges it will ship as part of v4.

If your changes also need to ship as a v3.x patch, a maintenance branch is now available:

• Branch: support/apollo-react@3.x (cut from @uipath/apollo-react@3.71.0)
• npm channel: latest-v3

To backport:

1. Create a branch based on support/apollo-react@3.x and cherry-pick your commits onto it
2. Open a separate PR targeting support/apollo-react@3.x
3. Use conventional commit prefixes (fix:, feat:) — semantic-release will handle versioning and publish to the latest-v3 dist-tag

If your changes are only needed going forward on v4, no action required — just be aware that main now targets the v4 release line.

Questions? Ping @BenGSchulz.