Removed some webpack libraries that were no longer used, to clear some npm warnings#4862
Merged
Merged
Conversation
…e npm warnings Started upgrading eslint to the new V10 architecture, but one of the eslint add on libs was still incompatible.
…e npm warnings Started upgrading eslint to the new V10 architecture, but one of the eslint add on libs was still incompatible.
Uncomment CMD for running the development server and comment out the SSL command.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tried to also clear all the eslint related npm warnings, by upgrading eslint to the new V10 architecture, but some of the eslint add on libs are still incompatible. This also would force an update to babel and it's plugins, that are not fully updated to the latest, so we need to wait a few months.