[BREAKING CHANGE]: Remove Gatsby plugins #1215
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's the purpose of this pull request?
We've been changing our base starters a lot recently. So much so that we don't use any custom Gatsby plugins anymore. Since we need to be multi-framework, we can remove all unused gatsby-* plugins and be more open to other frameworks
Also, to keep track of these plugins and not loose them entirely after this migration, I created a branch called
plugins-v1x
so we can release any hotfix on these modules.A nice side effect of this change is making the publish and development of the monorepo be much faster.
CI times before/after: