Reduce peerDependency warnings from installing dev environment #3400
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.
This really only affects the dev environment, and most of these are not real problems probably, but it can help to make the package manager happy and reduce error message overload. Most of these are fixed by adding some deps to root devDeps.
Before, 185 warnings
After, 8 warnings
most of the errors were fixed by adding these to the root package.json devDependencies. this is appropriate in some circumstances, in others, it is better for it to somehow get converted to a true dependency, but i think we do ok by adding these. the reason we did not have them historically is a little bit related to e.g. the create-react-app roots of the repo, which tries to provide these dependencies like eslint, webpack, etc in a somewhat covert way
We could go a bit further to fix the remaining warnings, or figure out alternative methods.