chore(deps): move browserslist and baseline-browser-mapping to overrides - #98
Merged
Merged
Conversation
Neither package is a direct dependency of the dashboard; both only arrive transitively through the PostCSS, autoprefixer, and Vite chain. Declare them the same way the file already handles undici, instead of listing them under devDependencies. Same versions resolve either way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the dependency patch merged earlier (browserslist, baseline-browser-mapping, vitest). That PR bumped the versions but left two of them listed under devDependencies, when neither is actually a direct dependency of the dashboard. Both only show up transitively through the PostCSS, autoprefixer, and Vite chain.
This moves browserslist and baseline-browser-mapping into the existing overrides block in web/package.json, next to undici, which is already there for exactly this case. Nothing about what resolves changes: same versions, same lockfile entries for every other package, verified with npm ls before and after.
Ran the full web suite (206 tests) and the production build, both green, and confirmed the build left src/caucus/ui/ untouched. npm audit still clears the four advisories from the earlier patch; the pre-existing nanoid high is unrelated and untouched here.