Skip to content

v1.2.1 — Full Scan Fix

Choose a tag to compare

View all tags
@dotcomico dotcomico released this 04 Jun 00:27
· 80 commits to main since this release
v1.2.1
cb9f36f

What's New in v1.2.1

🔧 Fixed

Full Scan Works After Global Install

allycat scan --full now works correctly out of the box after a global install — no extra steps, no silent failures.

  • Root cause: playwright and @axe-core/playwright were listed under devDependencies, which npm skips entirely during a global install (npm install -g allycat). Users who followed the README and ran npx playwright install chromium were downloading the browser correctly, but the playwright npm package itself was never present, causing --full to fail.
  • Fix: Both packages are now listed under dependencies and always ship with Allycat (~5MB). The Chromium browser (~300MB) remains a separate, optional step — only needed if you use --full.
# Install Allycat (Playwright ships with it automatically)
npm install -g allycat

# Only if you want a full scan with contrast checking:
npx playwright install chromium

# Full scan
allycat scan ./src --full

CI: Production Install Smoke Test

Added a new CI step that simulates the exact user install path — packs the tarball without devDependencies, installs it into a clean directory, and runs a full scan. This catches any future dependency miscategorisation before it reaches users.

📦 Install / Upgrade

npm i -g allycat

📖 Full Changelog

See CHANGELOG.md for the complete historical breakdown.

Assets 2
Loading