[CB-10239] Installing platforms from scoped npm packages

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5.0
• Component/s: cordova-lib
• Labels: cordova-8.0.0 triaged
• Assignee: Unassigned
• Reporter: Darryl Pogue
• Created: 21/Dec/15 23:58
• Updated: 03/May/17 07:20

Description

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:

<engine name="@dpogue/cordova-android" spec="~4.1.1" />

results in a warning being printed about a null or unrecognized platform.

Attempt #2:

<engine name="android" spec="@dpogue/cordova-android~4.1.1" />

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:

<plugin name="@dpogue/cordova-plugin-crosswalk-webview" spec="~1.4.0" />

works as intended.