Suppress 100+ baseline-browser-mapping warnings in CI#26544
Suppress 100+ baseline-browser-mapping warnings in CI#26544frankmueller-msft wants to merge 1 commit intomicrosoft:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the shared Azure Pipelines lint/build template to reduce CI log noise from baseline-browser-mapping warnings emitted via browserslist during ESLint runs.
Changes:
- Adds
BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA=1to thenpm run ci:build(templatetaskBuild) step environment ininclude-build-lint.yml.
| # Suppress "data is over two months old" warnings from baseline-browser-mapping, | ||
| # a transitive dependency of browserslist. Without this, the warning fires once | ||
| # per package during ESLint, producing 100+ identical warnings in build logs. | ||
| BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA: 1 |
There was a problem hiding this comment.
BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA is only being set for the npm run ${{ parameters.taskBuild }} step. When parameters.taskLint is true (many pipelines still run a separate npm run lint), the lint task will continue to emit the baseline-browser-mapping warning. Consider also setting this env var on the lint Npm@1 task (or moving it to a higher scope variable/env shared by both tasks) so the log suppression is consistent.
There was a problem hiding this comment.
Addressed — the env var is now set on both the build and lint steps.
frankmueller-msft
force-pushed
the
fix/suppress-baseline-browser-mapping-warnings
branch
from
d4989a0 to
75d899d
Compare
Add BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA=1 to both the build and lint steps in include-build-lint.yml. This eliminates ~128 identical "data is over two months old" warnings from baseline-browser-mapping, a transitive dependency of browserslist that fires once per package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
frankmueller-msft
force-pushed
the
fix/suppress-baseline-browser-mapping-warnings
branch
from
75d899d to
52bba8b
Compare
Summary
BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA=1to both the build and lint steps ininclude-build-lint.ymlbaseline-browser-mapping, a transitive dependency ofbrowserslistthat fires once per package during buildsNote
This suppresses the warning in CI only — local builds still surface it so developers know the data is stale. A follow-up should add a Renovate rule or periodic
npx update-browserslist-dbto keep the data current rather than permanently silencing the staleness signal.Test plan
Build - client packagespipeline, which only runs when client code is changed)🤖 Generated with Claude Code