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-sencha-cmd

v0.1.6

Published

Custom plugin created to automate single sencha cmd commands our team executes days in and days out during development time

Downloads

5

Readme

grunt-sencha-cmd

Custom plugin created to automate single sencha cmd commands our team executes days in and days out during development time. Under the hood it is a very simple wrapper which calls sencha cmd with parameters corresponding to the options of your grunt task

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-sencha-cmd --save-dev

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

grunt.loadNpmTasks('grunt-sencha-cmd');

Please note that grunt file should be placed in the root of your sencha workspace/application folder.

The "sencha_cmd" task

Overview

In your project's Gruntfile, add a section named sencha_cmd to the data object passed into grunt.initConfig().

sencha app build

For the most common scenario when all you need is to build your app no options or configuration required

grunt.initConfig({
  sencha_cmd: {    
  }
});

if environment needs to be defined (production, testing, native or package) it can be done by

grunt.initConfig({
  sencha_cmd: {
      environment: 'testing'
  }
});

if more than one environment should be built by one task environment should be array

grunt.initConfig({
  sencha_cmd: {
      environment: ['testing', 'production']
  }
});

sencha package build

if only package needs to be built task can be configured with scope and packageName

grunt.initConfig({
    sencha_cmd: {
        myPackage: {
            scope: 'package',
            packageName: 'myPackage'
        }
    }
});

sometimes, especially for unit testing purposes, in order to speed build up you may want to build only javascript for the package. In that case jsOnly option should be used:

grunt.initConfig({
    sencha_cmd: {
        myPackage: {
            scope: 'package',
            packageName: 'myPackage',
            jsOnly: true
        }
    }
});