[
https://issues.apache.org/jira/browse/CB-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Gill updated CB-10239:
----------------------------
Labels: cordova-6.0.0 cordova-fetch triaged (was: cordova-6.0.0 triaged)
> Installing platforms from scoped npm packages
> ---------------------------------------------
>
> Key: CB-10239
> URL: https://issues.apache.org/jira/browse/CB-10239
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CordovaLib
> Affects Versions: 3.5.0
> Reporter: Darryl Pogue
> Labels: cordova-6.0.0, cordova-fetch, triaged
>
> I have a bugfix branch for a platform, and while waiting for it to be merged
> and released, I published my fork of that platform to a scoped package on npm
> (i.e., @dpogue/cordova-android).
> In config.xml, there does not appear to be a way to specify that {{cordova
> prepare}} should restore that scoped package instead of the canonical Apache
> one.
> \\
> Attempt #1:
> {code:xml}
> <engine name="@dpogue/cordova-android" spec="~4.1.1" />
> {code}
> results in a warning being printed about a null or unrecognized platform.
> \\
> Attempt #2:
> {code:xml}
> <engine name="android" spec="@dpogue/cordova-android~4.1.1" />
> {code}
> results in pulling the Apache version from npm, ignoring my scoped package.
> A workaround for now is to use a git URL, but the advantage of npm is that it
> can download a tarball without the network cost of doing a full git clone.
> \\
> Also worth noting that scoped npm packages are supported with plugins:
> {code:xml}
> <plugin name="@dpogue/cordova-plugin-crosswalk-webview" spec="~1.4.0" />
> {code}
> works as intended.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
