You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Darryl Pogue (JIRA)" <ji...@apache.org> on 2015/12/22 00:58:46 UTC
[jira] [Created] (CB-10239) Installing platforms from scoped npm
packages
Darryl Pogue created CB-10239:
---------------------------------
Summary: 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
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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org