-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP - update dev deps (with additional TODO list) #382
Conversation
baacc0b
to
2531ba0
Compare
2531ba0
to
3ed0398
Compare
Codecov Report
@@ Coverage Diff @@
## master #382 +/- ##
=======================================
Coverage 63.86% 63.86%
=======================================
Files 14 14
Lines 1702 1702
Branches 286 286
=======================================
Hits 1087 1087
Misses 615 615 Continue to review full report at Codecov.
|
@brodybits I just noticed that this PR and some of the PRs I submitted over a month ago are somewhat inline. I am not sure if you had taken a look at all of them. #375 Remove Node 4 Support #377 Increase Code Code coverage
Since #377 also contains increased coverage, #376 will be needed because of a minor bug I found and happen to have written the test in PR #377. |
Thanks @erisu. I did already reference #375 as GH-375, did not realize that #377 already included nyc. I think you can see that I already reviewed and merged #376. I would kinda like to include the tests next, also hold off on dropping deprecated Node.js 4 until we take care of a couple items:
I will very likely push a few changes to this WIP PR to check CI while checking GH-377 (#377) |
This PR includes extra items that I will be moving out:
|
Is this still WIP? There are conflicts that need to be resolved. |
I will probably need 1-2 weeks to go through this. I wouldn't mind if someone else gets a chance to apply the changes on |
Closing in favor #496 which is now merged. |
Platforms affected
iOS
What does this PR do?
Update devDependencies in
master
branch:nodeunit
jasmine
,rewire
, andtmp
to be moved into a separate PR:
eslint
devDependencies, using eslint-config-standard@next (^12.0.0-alpha.0) to resolve[ESLINT_LEGACY_OBJECT_REST_SPREAD]
DeprecationWarning (Release 12.0.0 standard/eslint-config-standard#123 (comment))(includes fix to simplify AppVeyor CI install, which was already integrated to
master
branch and will drop out of this PR next time I do a rebase)This can be considered a continuation of the devDep cleanup merged from GH-368.
TO BE MOVED OUT OF THIS PR:
eslint
devDependencies - breaks on deprecated Node.js 4 version; suffers from[ESLINT_LEGACY_OBJECT_REST_SPREAD]
DeprecationWarning (Release 12.0.0 standard/eslint-config-standard#123 (comment))devDep TODO
Extra TODO items outside this PR:
node_modules
, dropbundledDependencies
, and mark next major versiondependencies
, which should resolve existingnpm audit
issues as was already done in CB-14217 cordova-ios 4.5.5 patch release (July 2018) #381 for patch releaseWhat testing has been done on this change?
npm run unit-tests
succeeds on mac "desktop"npm test
items succeed on Travis CI (skipping deprecated Node.js 4 version due to eslint update)eslint
&npm run unit-tests
items succeed on AppVeyor CI(now passes on all covered Node.js versions including deprecated Node.js version 4 if fix proposed in Simplify installation on AppVeyor CI #383 is included)(skipping deprecated Node.js 4 version due to eslint update)Checklist
Reported an issue in the JIRA databaseCommit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.Added automated test coverage as appropriate for this change.