Locale rollout diff check

A localization owner runs this when translations are updated. The cards are the same cards you already export per locale. What you need is two PNG sets at identical dimensions: one from the old locale files, one from the new ones.

This is review work after a translation pass. You want to see which cards actually changed. You do not want two screenshots taken on different machines. Framing, fonts, and size have to stay put so the diff is about the strings.

The job is a before set and an after set. The component does not change. The data files do. You export the old locale files to one --out, then the new locale files to another --out. An image diff between the two folders is the review.

Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same artboards, two data sets, two output folders. There is no batch product, no queue, no orchestrator.

The component is unchanged. Use the artboards you already have for the campaign or the set you are rolling out. This case does not add a new file. The point is that both runs use the same artboards and the same renderer.

The data is the old locale files and the new locale files, each exported to its own --out. Same keys, new strings. That is two passes of bulk pattern 1: re-run export with a different --data file, and a different --out, each time. --data is never written back into .lerret/.

The images are two PNG sets at identical dimensions.

Both runs use the same artboards and renderer, so an image diff shows exactly which cards changed. The only pixels that should move are the ones the new translation moved.

Point --out at one folder for the old locale files, then at a second folder for the new ones. Keep the artboards the same on both runs. --data is never written back into .lerret/. The two PNG sets stay at identical dimensions so an image diff is about the strings.

npx @lerret/cli@latest export --out

Start a project with npx create-lerret@latest. More in the use cases index.