Github user vladimir-kotikov commented on the issue:
https://github.com/apache/cordova-lib/pull/498
Looks good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user brodybits commented on the issue:
https://github.com/apache/cordova-lib/pull/498
Thanks @TimBarham for the explanation
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user TimBarham commented on the issue:
https://github.com/apache/cordova-lib/pull/498
@brodybits - that hasn't changed. At the point where we're looking for a
cached version, we have already determined the latest version that matches the
requested range (for both platforms and
Github user brodybits commented on the issue:
https://github.com/apache/cordova-lib/pull/498
I would personally favor this change to be "opt-in". I like the idea that
npm checks for a newer release before using the cached version of a package.
---
If your project is set up for it,
Github user codecov-io commented on the issue:
https://github.com/apache/cordova-lib/pull/498
## [Current
coverage](https://codecov.io/gh/apache/cordova-lib/pull/498?src=pr) is 80.57%
(diff: 100%)
> Merging [#498](https://codecov.io/gh/apache/cordova-lib/pull/498?src=pr)
into
