0.1.0 • Published 9 years ago

grunt-cordova-plugins v0.1.0

Weekly downloads
2
License
MIT
Repository
github
Last release
9 years ago

grunt-cordova-plugins Build Status

Grunt task to automatically install all your cordova plugins at once

Getting Started

This plugin requires Grunt >=0.4.0

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-cordova-plugins --save

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks("grunt-cordova-plugins");

cordova_plugins task

Run this task with the grunt cordova_plugins command.

Usage example

cordova_plugins: {
    options: {
        cwd: "cordova/my_app",
        build: true,
        remove: true
    },
    dist: {
        plugins: [
            "cordova-plugin-splashscreen",
            {
                name: "https://github.com/jbavari/cordova-facebook-connect.git"
                variables:
                    APP_ID: "123456789"
                    APP_NAME: "Hello"
            }
        ]
    }
}

Options

cwd

  • Type : String
  • Default : .

Current working directory, e.g. your cordova app folder root.

build

  • Type : boolean
  • Default : false

If set to true, cordova build will be called after all plugins installation.

remove

  • Type : boolean
  • Default : false

If set to true, plugins will be removed before being re-installed.

Contributing

  1. Fork the repository :)
  2. Create your feature branch: git checkout -b feature/awesome-feature
  3. Run: npm i to install dependencies
  4. Run: grunt build to build the project
  5. Do changes
  6. ADD TESTS ! and launch them with grunt test
  7. Commit your changes: git commit -m 'Adds awesome feature'
  8. Push your commits: git push origin feature/awesome-feature
  9. Submit a pull request !

Your build/test has to pass travis builds. You also have to respect the coding styles we used in this project, otherwise your pull request might be rejected.

Release History

See CHANGELOG.md