Update metalsmith dependencies and use core plugins #2263
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.
What
This replaces some of our metalsmith dependencies with their new "core" versions, which are maintained by the metalsmith team and more up to date. It also updates plugins which are still maintained. It does not address any dependencies that don't have a direct, switchable successor:
It also doesn't address the update of packages which have been blocked by metalsmith issues in the past (#1663)
Changelogs are in the commit messages. After each package update, I ran
npm build
andnpm test
before moving to the next, and didn't encounter any obvious issues.Why
Metalsmith has recently stepped up active development, and this allows us to keep these dependencies up to date. It's an interim step before we revisit the use of metalsmith as our static site generator (#2023)