🐛 Bug Report
The lint and lint:fix scripts in fast-element and fast-html are missing the --changed and --no-errors-on-unmatched flags that the equivalent root-level scripts use.
💻 Repro or Code Sample
The root package.json runs lint with:
"lint": "biome lint --changed --no-errors-on-unmatched .",
"lint:fix": "biome lint --changed --no-errors-on-unmatched --fix ."
But packages/fast-element/package.json and packages/fast-html/package.json both have:
"lint": "biome lint .",
"lint:fix": "biome lint --fix ."
🤔 Expected Behavior
The package-level lint and lint:fix scripts should include the same --changed --no-errors-on-unmatched flags as the root, so running lint at the package level behaves consistently with the root.
😯 Current Behavior
Running npm run lint -w @microsoft/fast-element lints all files instead of only changed files, and fails on unmatched globs — different behavior than npm run lint from the root.
💁 Possible Solution
Update the existing scripts in both packages to match the root flags:
"lint": "biome lint --changed --no-errors-on-unmatched .",
"lint:fix": "biome lint --changed --no-errors-on-unmatched --fix ."
🔦 Context
The inconsistency means developers working within a single package get different lint behavior than CI or root-level runs. This can surface false positives on unchanged files locally, or cause CI failures that don't reproduce at the package level.
🌍 Your Environment
- OS & Device: macOS on Apple Silicon
@biomejs/biome: 2.4.8@microsoft/fast-element: v2 (current main)@microsoft/fast-html: alpha (current main)
🐛 Bug Report
The
lintandlint:fixscripts infast-elementandfast-htmlare missing the--changedand--no-errors-on-unmatchedflags that the equivalent root-level scripts use.💻 Repro or Code Sample
The root
package.jsonruns lint with:But
packages/fast-element/package.jsonandpackages/fast-html/package.jsonboth have:🤔 Expected Behavior
The package-level
lintandlint:fixscripts should include the same--changed --no-errors-on-unmatchedflags as the root, so running lint at the package level behaves consistently with the root.😯 Current Behavior
Running
npm run lint -w @microsoft/fast-elementlints all files instead of only changed files, and fails on unmatched globs — different behavior thannpm run lintfrom the root.💁 Possible Solution
Update the existing scripts in both packages to match the root flags:
🔦 Context
The inconsistency means developers working within a single package get different lint behavior than CI or root-level runs. This can surface false positives on unchanged files locally, or cause CI failures that don't reproduce at the package level.
🌍 Your Environment
@biomejs/biome: 2.4.8@microsoft/fast-element: v2 (current main)@microsoft/fast-html: alpha (current main)