cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Resolved] (CB-3605) package.json bin scripts
Date Mon, 15 Jul 2013 18:28:50 GMT


Filip Maj resolved CB-3605.

    Resolution: Fixed

Updated the README.
> package.json bin scripts 
> -------------------------
>                 Key: CB-3605
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.7.0
>         Environment: Windows
>            Reporter: Angela Fowler
>            Assignee: Filip Maj
>            Priority: Minor
>             Fix For: 3.0.0
> The "Cordova Android Developer Tools" section talks about installing the dependencies
however the package.json does not contain any dependencies. It contains a "bin" which maps
command names to local file names.
> "bin":
> { "create": "./create", "bench": "./bench", "autotest": "./autotest", "BOOM": "./BOOM",
"test": "./test" }
> 1. The only command in the bin directory is create (and also update which is not in package.json
> The autotest and test exist in the cordova-cli project but only for ios.
> I could not find bench or BOOM.
> 2. The create script is a bash script. There is also a create.js and create.bat for Windows
which does not appear to require npm.
> Is there any use for npm on Windows in cordova-android?
> 3. Is this how npm looks when correctly installed for cordova-android? Could it have
failed somehow because the repository is pointing to incubator?
> c:\development\cordova-2.7.0\cordova-android\bin>npm list npm WARN package.json cordova-android-cli@0.0.1
No file found!
> cordova-android-cli@0.0.1 c:\development\cordova-2.7.0\cordova-android\bin
> └── (empty)
> Note : npm runs successfully in cordova-js which has several dependencies installed and

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message