[ 
https://issues.apache.org/jira/browse/CB-10770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233106#comment-15233106
 ] 

Nikhil Khandelwal commented on CB-10770:
----------------------------------------

{code}
<engine name="ios" spec="~4.1.0" />
{code}

The above tag is semver allows patch version updates. That's the default policy 
for cordova plugin add --save as we think that's the correct behavior for most 
projects. You  can always change it to "4.1.0" to lock to that version. Is 
there a reason why you do *not* want 4.1.1?

> cordova cli not adding platform via npm specifying new version before 24 
> hours of release
> -----------------------------------------------------------------------------------------
>
>                 Key: CB-10770
>                 URL: https://issues.apache.org/jira/browse/CB-10770
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 6.0.0
>         Environment: Mac
>            Reporter: Carlos Santana
>            Priority: Minor
>              Labels: CLI, triaged
>
> A new release of platform ios [email protected] is published to NPM
> User tries to install with $ cordova platform [email protected]
> At the time of this command the npm cache information for the pacakge 
> cordova-ios in 
> ~/.cordova/lib/npm_cache/registry.npmjs.org/cordova-ios/.cache.json doesn't 
> have the information about 4.1.0 and the file is not older than 24 hours.
> cordova cli is configured with npm cache-min = 3600*24 (24 hours)
> If the file in the cache is not older than 24 hours npm will not check the 
> registry. and requested package [email protected] is not added to the cache.
> There is no err catch for this case in the cordova-lib [1]
> [1]: 
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/lazy_load.js#L158



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to