fix(gatsby-plugin-netlify-cms): use friendly-errors-webpack-plugin package that satisfies webpack@5 peerDependency #31446
Conversation
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
…ckage that satisfies webpack@5 peerDependency
gatsbot
bot
added
the
status: triage needed
LekoArts
added
topic: netlify
and removed
status: triage needed
LekoArts
approved these changes
May 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
My changes to
friendly-errors-webpack-pluginwere merged quite a bit ago so there's no reason to use my fork anymore. Howeverfriendly-errors-webpack-plugindoesn't "support" webpack@5 ( geowarin/friendly-errors-webpack-plugin#123 ) so opting to yet another fork that has webpack@5 "support" (well peerDep really, as it seems things work correctly either way)Related Issues
#31441