parse-errorsunchanged
Asserts — The parse-error report, scoped to a repo of nothing but an unparseable file so the block is not buried (#13).
Ran hermex scan --config configs/parse-errors.config.ts in fixtures/ → exit 0, as asserted
Config fixtures/configs/parse-errors.config.ts · Fixture fixtures (overview) · Case parse-errors (dossier)
Reproduce locally: pnpm run test:output -- --filter parse-errors
fixtures/configs/parse-errors.config.ts
import type { HermexConfigInput } from '../../src/config/types.ts';
import base from '../hermex.config.ts';
/**
* Scopes the scan to `fixtures/broken/` so the parse-error report is the
* whole output instead of three lines buried above the packages table
* (#13). Everything else is off for the same reason.
*/
export default {
...base,
includes: ['broken/**/*.{tsx,jsx,ts,js}'],
output: {
summary: 'log',
packages: false,
components: false,
patterns: false,
details: false,
versus: false,
rules: false,
},
} satisfies HermexConfigInput;
stdout.txthermex v<version>
- Parsing lockfile...
✔ Found pnpm lockfile (supports: v5, v6, v9) - 5 packages
✔ Found 1 files
✔ Analysis complete! Analyzed 0/1 files
⚠ 1 file(s) failed to parse:
broken/unparseable.tsx
x Expression expected
,----
1 | export const Broken = ( : : :;
: ^
`----
Caused by:
Syntax Error
📊 Summary
┌─────────────────────┬───────┐
│ Metric │ Count │
├─────────────────────┼───────┤
│ Files Analyzed │ 0 │
├─────────────────────┼───────┤
│ Packages │ 5 │
├─────────────────────┼───────┤
│ External Components │ 0 │
├─────────────────────┼───────┤
│ Total Usages │ 0 │
└─────────────────────┴───────┘
stderr.txt