Local dry run before a launch

Anyone can do this, the day before a launch. You have a launch page or group in .lerret/ and a real launch data file. Tomorrow you’ll export for real. Tonight you want to see the set before anyone else does.

This is a rehearsal of the launch-day command. Same path, same data, scratch --out. You’re not inventing a second workflow. You want every broken artboard in one pass, not one failure per attempt.

The job is to run export on just that folder path, with the real launch data, into a scratch --out. You review the images by eye. If something is wrong, you want to see all of it now.

Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same component, data swapped, many images. There is no batch product, no queue, no orchestrator.

The component is the launch page or group only. Leave the rest of the project out of the path. That’s how you keep the dry run scoped: one folder, the same folder you’ll export tomorrow. The artboards inside are whatever the launch already uses. This case doesn’t add a new component.

Data is the real launch data file. Don’t swap in placeholder copy for the rehearsal. The point of a dry run is that the values are the values you’ll ship. Pass that file the same way the launch-day command will.

The image is the full launch set, written into a scratch --out, reviewed by eye. Sizes and formats are whatever those launch artboards already declare. The scratch directory is the whole deliverable. You look at every file, then you throw the folder away or keep it as a record of the rehearsal.

You use Lerret because export on one folder path rehearses the launch-day command. If one artboard is broken, the run still produces the rest, so you find every problem in that one pass rather than one per attempt. The rest of the project is untouched because it was never on the path. A design file the night before, or one-off screenshots of a staging page, will not give you that.

npx @lerret/cli@latest export --out

Point the path at the launch page or group, and --out at a scratch directory. Start a project with npx create-lerret@latest. More in the use cases index.