{"version":"2.1.247","anchor":"artifacts-can-be-previewed-in-a-headless-browser-before-you-","canonical_anchor":"artifacts-can-be-previewed-in-a-headless-browser-before-you-","heading":"Artifacts can be previewed in a headless browser before you publish","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifacts-can-be-previewed-in-a-headless-browser-before-you-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifacts can be previewed in a headless browser before you publish\n\nA new preview action renders a local HTML artifact in a headless browser and returns screenshots plus problems.\n\n**What**\n\nA new `preview` action on the artifact tool renders a local `.html` file in a headless browser at one or more viewport widths and in both light and dark themes, and returns screenshots plus a list of problems found by static checks. It asks permission first. Nothing is uploaded, though the page can still fetch any Google Fonts stylesheets it references.\n\n**Details**\n\n- The result carries the captures, the issue list, a count of issues that were dropped, and a render error when one occurred, so a browser that fails to start is reported instead of quietly producing nothing.\n- If the browser cannot launch, the static checks still run on their own and the first line of the result explains why rendering did not happen.\n- The `widths` and `themes` parameters only appear on the tool's inputs when the same shape check that decides which artifact actions are offered is satisfied. That check is derived from the artifact tool's action list rather than a compiled-in on\/off value, so whether preview is offered to a given account is decided by that list.\n\n**Evidence**\n\n`The browser could not start, so nothing was rendered and only the static checks ran; the first line below says why.`\n\n- Area: Artifacts\n- Names: `preview`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}