npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-wirecloud

v0.9.9

Published

WireCloud utilities for grunt.

Downloads

11

Readme

grunt-wirecloud

Coverage Status Tests

WireCloud utilities for grunt.

Getting Started

This plugin requires Grunt ~0.4.5

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-wirecloud --save-dev

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

grunt.loadNpmTasks('grunt-wirecloud');

The "wirecloud" task

Run this task with the grunt wirecloud command.

Task targets and options may be specified according to the grunt Configuring tasks guide.

Options

options.instance

Type: String Default value: 'fiwarelab'

Name of the WireCloud instance where the components are going to be uploaded.

options.overwrite

Type: Boolean Default value: false

If the same version of the Mashable Application Component is currently uploaded to the instance, delete it and upload it again.

NOTE: If this option is set to false and the component already exists, nothing will be done.

options.public

Type: Boolean | null Default value: null

Configure public visibility of the uploaded Mashable Application Component. If this value is true the uploaded MAC will be configure to be available to all the users. If false the MAC will be available only to the configured users and groups.

If null, the server will chose the default value for this parameter. This means that uploaded MACS will be public when uploading it into a wirecloud catalogue instance and private when uploading into a WireCloud platform instance.

This parameter may require permissions on the target server.

Flags

Some options are also available as flags in case you want to change them when executing the grunt command. There are two flags available:

  • target: used to choose the instance to which the component will be uploaded.
  • public: used to make the component available to all users.

Example

To upload a widget available to all users to localhost instance using flags you can use the this Gruntfile.js configuration:

grunt.initConfig({
    wirecloud: {
        default: {
            file: 'build/component.wgt'
        }
    },
});

And the following command:

grunt wirecloud --target localhost --public

Usage Examples

Default Options

In this example, the default options are used to upload 'build/component.wgt'. So the 'build/component.wgt' file will be uploaded to the 'fiwarelab' instance.

grunt.initConfig({
    wirecloud: {
        default: {
            file: 'build/component.wgt'
        }
    },
});

Overwriting existing component

In this example, the options are set to upload a component that already exist in the platform overwriting it.

grunt.initConfig({
    wirecloud: {
        options: {
            instance: 'some_instance',
            overwrite: true
        },
        publish: {
            file: 'path/to/component/file'
        }
    }
});

Upload a public component

This configuration uploads a component avilable to all users.

grunt.initConfig({
    wirecloud: {
        options: {
            instance: 'some_instance',
            public: true
        },
        publish: {
            file: 'path/to/component/file'
        }
    }
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)