Skip to main content
Run lettercamp check after changing components, styles, or articles to find problems before deploying to Lettercamp Cloud. It checks imports and source files, then builds a temporary deployment copy without signing in, uploading, or changing your publication.
A successful full check prints:
The command exits with code 0 on success and 1 when it finds a problem. It groups import problems by cause, gives file and line locations, and explains how to fix them. Fix the reported problems and rerun the command; the build runs after the import checks pass.

Options

New publications include an npm run check script. Existing publications can use npx lettercamp check directly. If the command is missing, update the CLI.

Fix an unsupported import

For example, a footer might import its stylesheet through a project alias:
Cloud does not use your publication’s package.json import aliases. Sass is supported, so keep the stylesheet and import it relative to the component:
See supported imports for the complete component guidance, including alternatives to icon packages.

Use with an agent

If the change needs hosted images or fonts, the agent can first upload them with the signed-in CLI and write the returned URLs into the source. check validates the resulting publication; it does not upload files. Ask your agent to run this after changing custom components:
The result contains ok, build (passed, failed, or skipped), and an issues array. Each issue has a code and message. When available, it includes file, line, column, import, fix, and a suggested replacement import. For example:
An agent should fix the reported files and rerun the full check until ok is true and build is passed. Use local preview to inspect appearance and browser interactions too. The check renders the site; it is not a TypeScript type checker or a browser interaction test.

Check, build, and deploy

  • check tests compatibility with Cloud using your installed CLI. It removes its temporary output when finished. Account and plan-specific limits are checked during deployment.
  • build writes a static site for another host and can use locally installed packages. Passing this build alone does not establish Cloud compatibility.
  • deploy runs the same import and temporary build checks before a new upload, then publishes. An interrupted deployment resumes its saved snapshot; new edits belong to the next deployment.