chore(deps): Upgrade to latest Capsize packages #319
Merged
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.
π Linked issue
First step relating to this discussion.
Closes #317 and #318 (auto-generated PRs)
β Type of change
Open to discussing this one, selecting
chore
for now.π Description
Upgrading to the latest Capsize packages. This upgrade provides a few key benefits to the Fontaine π€ Capsize relationship:
moduleResolution
strategy that understands the package.jsonexports
key, e.g.Bundler
.xWidthAvg
metric, now calculated from more extendable dataset (rather than hard coded English character frequencies) in preparation for supporting other unicode subsets, e.g. Thai.This is a move away from the original character frequencies collaborated on with the Google Aurora team, and seem to perform same or better, while also having the benefit of no longer being hard coded. As a result the snapshots of metrics and CSS have changed, but here is a visual example of the change to IBM Plex Mono (used in one of the snapshots):
No Capsize:
With Capsize v1:
With Capsize v2:
Note also upgrading to Node 18 in CI due to missing
fetch
API. Hopefully thats ok given Node 16s move to EOLπ Checklist