Uploaded image for project: 'Apache Cordova'
  1. Apache Cordova
  2. CB-10239

Installing platforms from scoped npm packages

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.5.0
    • Fix Version/s: None
    • Component/s: cordova-lib

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              dpogue Darryl Pogue
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: