Upgrade to Node.js 10.x and fix security vulnerabilities #14
Conversation
This file contains 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
nicklaw5
force-pushed
the
fix-eslint-security-issues
branch
4 times, most recently
from
9496fd6
to
dd80c71
Compare
nicklaw5
changed the title
- Update Eslint to v6.x - Use default Eslint rules rather than third-party ruleset - Update mocha to v6.x - Include package-lock.json file to avoid regressions - Use babel as Eslint parser
Node.js 6.10 is now deprecated and no longer supported by AWS.
nicklaw5
force-pushed
the
fix-eslint-security-issues
branch
from
2be2a03
to
4a44829
Compare
hlmartin
approved these changes
Jul 16, 2019
KleeUT
approved these changes
Jul 16, 2019
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.
Fixing this:
Also: