AISlop

Two bug fixes. No new features, no breaking API changes. Agent-integration hooks land in 0.6.0 separately.

Fixed

complexity/file-too-large now respects config on JSX/TSX

Previous behaviour silently applied a 2x multiplier for .jsx / .tsx plus a 10% soft buffer, so maxFileLoc: 400 actually fired at 881 lines on TSX. Neither piece was documented or configurable, so big React pages sailed past 400 unflagged.

New behaviour:

• .jsx / .tsx use a 1.5x tolerance (400 → 600) with no soft buffer.
• Every other extension (.ts, .js, .py, .go, .rs, .rb, .java, .php, .mjs, .cjs) hits the exact configured value.
• This is a tightening for TSX: a .tsx file that was fine at 800 lines under 0.5.0 will now flag at 601 lines. Bump .aislop/config.yml → maxFileLoc if needed.

aislop fix -f pnpm dep-audit fix

Previously tried to run pnpm audit --fix, which pnpm has no subcommand for, so the step silently failed. Now parses pnpm audit --json and writes surgical pnpm.overrides entries keyed on <pkg>@<vulnerable_versions> into root package.json, then runs pnpm install to materialise them. npm path unchanged.

Changed

• Internal refactor. narrative-comments.ts 416 → 358 lines splits patterns into narrative-comments-patterns.ts. complexity.ts 416 → 241 lines splits function-boundary detection into function-boundaries.ts. No behaviour change.

Tests

• 3 new complexity tests (1.5x JSX tolerance). Total: 516 → 519 passing.

Install

npm i -g [email protected]
# or
npx [email protected] scan .

What's Changed

• release: v0.5.1 — JSX file-too-large config fix + pnpm audit fix by @heavykenny in https://github.com/scanaislop/aislop/pull/35

Full Changelog: https://github.com/scanaislop/aislop/compare/v0.5.0...v0.5.1