rallyapps/rally-app-builder

A Node.js command line utility for building apps using the Rally App SDK

Rally App Builder

Rally App Builder is a Node.js command line utility for building apps using the Rally App SDK.

Installation

Rally App Builder is most easily used when installed globally:

npm install -g rally-app-builder

However, if that does't work (permission errors, etc.) it can be installed locally as well:

npm install rally-app-builder

API

Usage: rally-app-builder [command] [options]

Commands:

init [--name] [--sdk] [--server]
Creates a new Rally App project

build [--templates]
Builds the current App

run [--port]
Starts a local server and launches the App in the default browser

watch [--templates] [--ci]
Automatically builds the App when files are changed

test [--debug] [--spec]
Runs the App tests

Options:

-h, --help     output usage information
-v, --version  output the version number

Commands

init

rally-app-builder init --name=myNewApp Creating a new Rally App is as easy as using init. The init command creates you a After init creates your App it will automatically run the build command on it for you.

The init command takes a few parameters.

• name : The first is the name for your new App.
  • rally-app-builder init --name=myNewApp
• sdk(optional) : The version of the SDK your App will be created against.
  • rally-app-builder init --name=myNewApp --sdk=2.1
• server(optional) : The server you want the debug file to point to. The command below will create a new App using version 2.0 and pointing to the server myownRally.com
  • rally-app-builder init --name=myNewApp --sdk=2.1 --server=https://myOwnRally.com

build

Use the build command to compile your App into a single HTML page that can be copy and pasted into a Rally customer html page Run this command before you check your file into source control or whenever you make a change to your config.json file.

The build command can optionally take a templates parameter to use custom html output templates. Note this is an advanced usage and is generally not necessary unless you are trying to tweak the structure of the generated html output.

rally-app-builder build --templates=./templates

Also note this parameter can be specified in the config.json file as well.

Custom build steps

You can define pre and post build commands to be executed by adding them to your config.json. These can be used to extend and support the rally app build/concatenation steps. An example using grunt (which by default will run your tests):

{
   "scripts": {
      "prebuild": "./node_modules/.bin/grunt"
      "postbuild": "echo 'build completed'"
   }
}

run

rally-app-builder run

The run command starts a local http server and launches your App-debug.html file in the default browser for quick an easy development. By default the server listens on port 1337. This can be changed as follows:

rally-app-builder run --port=9999

watch

rally-app-builder watch [--templates] [--ci]

The watch command listens for changes to app files and automatically rebuilds the app. If the optional --ci flag is passed the tests will also be run.

test

rally-app-builder test [--debug] [--spec]

The test command runs the tests. By default all tests will be run headlessly. If the --debug flag is specified the tests will be run in the default browser instead. If the --spec flag is specified only the test(s) matching the specified file pattern will be run.

The Testing Apps guide in the App SDK help documentation is a great resource to learn how to get started writing tests for your apps.

rally-app-builder's Issues

The app builder cannot be installed.

maybe the app builder is out of date. some warnings came up.

10 packages are looking for funding
run npm fund for details

56 vulnerabilities (4 low, 14 moderate, 28 high, 10 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.

C:\Users\503254506> npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit fix [email protected] node_modules/request/node_modules/mime
npm WARN audit fix [email protected] is a bundled dependency of
npm WARN audit fix [email protected] [email protected] at node_modules/request
npm WARN audit fix [email protected] It cannot be fixed automatically.
npm WARN audit fix [email protected] Check for updates to the request package.
npm WARN audit fix [email protected] node_modules/request/node_modules/form-data
npm WARN audit fix [email protected] is a bundled dependency of
npm WARN audit fix [email protected] [email protected] at node_modules/request
npm WARN audit fix [email protected] It cannot be fixed automatically.
npm WARN audit fix [email protected] Check for updates to the request package.
npm WARN audit Updating rally-app-builder to 0.9.7,which is a SemVer major change.
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "from" argument must be of type string. Received undefined

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\503254506\AppData\Local\npm-cache_logs\2022-03-14T21_58_20_424Z-debug-0.log

v2.0.0 doesn't work on mac

can't npm install with iojs 2.2.1

I dont' know if this is due to using iojs, but npm install -g rally-app-builder fails unless I manually install the following packages first:

npm install -g brace-expansion
npm install -g wrappy
npm install -g concat-map
npm install -g balanced-match
npm install -g core-util-is

Only after i install those 5 dependencies globally can I install and rab build

Debug file does not add App.js

rab run unable to serve files above root

This makes it impossible to work on apps like custom board from rallyapps/app-catalog.

The current workaround is to just copy any files from above the config.json directory down and modify config.json to point to the local copies.

npm-debug.log

npm-debug.log

compilation fails when using async functions

Promises are ugly. Async functions are so much more readable. When I try to use them however, I'm unable to compile my app. Any chance we can get the compiler to work with them?

Thanks!
Dustin

Add Travis Support

Unable to install rally-app-builder

Hi,
I am trying to install the rally-app-builder, and it is throwing an error for phantomjs.
my node version is : 8.9.4
npm version : 5.8.0

Error : Failed at the [email protected] install script

is there a way to get around this in case phantom is not mandatory.

not working on node version 5.10

rab does nothing on node version 5.10, and doesn't produce even an error message.

Command line flag for run command to not open browser tab

My development process requires me to use an API key (?apiKey=) to log into the app in localhost. Every time I execute rally-app-builder run it opens up in a new tab without the API. I close that tab and refresh my page with the API key.
This can be very tedious and slows down development.

appName in package.json cannot contain spaces

Build is not replacing the url specified in the debug file

Default template source file points to a resource location that does not exist.

I created a new app with rally-app-builder.

C:\Users\cfinan\Desktop\SecondApp>rally-app-builder init secondApp
Creating a new App named secondApp
Creating App-debug.html
Creating App.html
Creating App-external.html
Creating App-uncompressed.html
Success

Then, did rally-app-builder run command.

The page opens in the browser and tries to load a script that does not exist. From the console , the error reads:
Failed to load resource: the server responded with a status of 404 (Not Found) https://rally1.rallydev.com/apps/World/sdk-debug.js

I haven't modified anything else in the project. This is the default link.

Mishandling of missing js file

If you have an incorrect js file in your config.json the build step reports success even though it totally bails on putting any of the js files in the built html files.

Expose/Allow alteration of template for html generation (request)

It would be cool if we could provide an alternate template file while building for saving into source control with our project. It'd be nice to be able to put something into the HTML or the basic setup of the page in a template so we don't have to do it by hand after the build. The current use case (but there are others) is an instance where the developer wants to put extra html into the header like this:

<![if !IE]>

<script type="text/javascript" src="/apps/2.0rc3/sdk.js"></script>

<![endif]>

before the rally script tag. (I can think of other instances where we might want to muck with the definition of the launch js or do something in the body.) An alternate template would be awesome because we could version control it and we wouldn't have to keep remembering to add the stuff by hand on every build.

Sometimes Config files are deleted

I think it's due to errors occurring during the reformatting portion of getting the config.

Cannot install rally app builder on windows 64 bit

after using npm install -g rally-app-builder
or the local install

get error Visual Studio 2005 and .net framework required..

after installing the above two s/w, get error no file found named:winsock2.h

watch does not seem to be working at all on osx yosemite

should also be updated to watch the app directory and also any files listed in config.json.

Problem setting apiversion

{
   "name": "Exercise 4",
   "className": "CustomApp",
   "server": "http://10.132.66.146",
   "sdk": "2.0p5",
   "javascript": [
      "App.js"
   ],
   "wsapiVersion": 1.43,
   "css": [
      "app.css"
   ]
}

No wsapiVersion in App-debug.html, I must set it in src manully:

<script type="text/javascript" src="/apps/2.0p5/sdk-debug.js?wsapiVersion=1.43"></script>

Default take should be build

No valid gruntfile

Implement init command

Have the init command take the templates from the templates directory and replace them with things passed in the args.

Copy functionality of the App template as below
rake new[app_name,sdk_version,server]

Doesn't npm install on mac os x

npm install rally-app-builder

fails on Mac OS X 1.9.5 with following error:

No compatible version found: iced-coffee-script@'>=1.3.0 <1.4.0'

Node 0.10.32
Npm 2.0.2

not able to install on windows

Hi, I am not able to npm install rally-app-builder in Windows. Error as below:
Refusing to install rally-app-builder as a dependency of itself.

Please advises......

Unable to include fully qualified css files

Watch for when files are changes and rebuild

Node 8 `rab run` doesn't start a web server

Could not install [email protected]

10758 verbose linkMans [email protected]
10759 verbose rebuildBundles [email protected]
10760 verbose rebuildBundles [ '.bin',
10760 verbose rebuildBundles 'async',
10760 verbose rebuildBundles 'coffee-script',
10760 verbose rebuildBundles 'commander',
10760 verbose rebuildBundles 'fetch-github-repo',
10760 verbose rebuildBundles 'grunt',
10760 verbose rebuildBundles 'grunt-cli',
10760 verbose rebuildBundles 'grunt-contrib-clean',
10760 verbose rebuildBundles 'grunt-contrib-concat',
10760 verbose rebuildBundles 'grunt-contrib-jasmine',
10760 verbose rebuildBundles 'grunt-contrib-watch',
10760 verbose rebuildBundles 'handlebars',
10760 verbose rebuildBundles 'jshint',
10760 verbose rebuildBundles 'lodash',
10760 verbose rebuildBundles 'mustache',
10760 verbose rebuildBundles 'request',
10760 verbose rebuildBundles 'uglify-js' ]
10761 info install [email protected]
10762 info postinstall [email protected]
10763 verbose exit [ 0, true ]
10764 error Error: write EIO
10764 error at errnoException (net.js:901:11)
10764 error at Object.afterWrite (net.js:718:19)
10765 error If you need help, you may report this entire log,
10765 error including the npm and node versions, at:
10765 error http://github.com/isaacs/npm/issues
10766 error System Windows_NT 6.1.7601
10767 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "rally-app-builder"
10768 error cwd C:\Users\liulu4
10769 error node -v v0.10.23
10770 error npm -v 1.3.17
10771 error syscall write
10772 error code EIO
10773 error errno EIO
10774 verbose exit [ 1, true ]

Unable to serve shared files above app's root directory

Certain apps in the catalog which share common files do not work correctly when served from rally-app-builder run because the server's root path is the app's directory.

JSHint is running twice

JSHINT for Rallly App Builder looks like it is running twice... This is after creating a new app using init...

rally-app-builder build
Compiling the App.
Error in ucomp/ObjContainer.js on line 300: ['Accepted'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 302: ['Completed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 306: ['Defined'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 308: ['Missed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 320: ['Missed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 701: Don't make functions within a loop.
Error in ucomp/ObjContainer.js on line 706: Don't make functions within a loop.
Error in ucomp/OthContainer.js on line 80: ['Accepted'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 82: ['Completed'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 85: ['Defined'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 87: ['Missed'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 99: ['Missed'] is better written in dot notation.
Error in ucomp/SummaryContainer.js on line 507: Don't make functions within a loop.
Error in ucomp/DependencyContainer.js on line 513: Don't make functions within a loop.
Error in ucomp/DependencyContainer.js on line 518: Don't make functions within a loop.
Error in rmodel/DataLoader.js on line 1028: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1031: ['STRETCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1034: ['ARCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1037: ['REFA'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1040: ['INNOV'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1043: ['PROG'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1046: ['SPIKE'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1049: ['PRODUCER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1052: ['CONSUMER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1055: ['DEPENDENCY'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1060: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1420: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1422: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1425: ['FoundExtParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1427: ['FoundExtParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1429: ['FoundExtParentPSI'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1434: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1436: ['FoundExtParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1438: ['FoundExtParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1440: ['FoundExtParentPSI'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1445: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1447: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1449: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1503: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1601: ['Objective'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1803: Don't make functions within a loop.
Error in rmodel/DataLoader.js on line 2182: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2184: ['STRETCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2186: ['ARCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2188: ['REFA'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2190: ['INNOV'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2192: ['PROG'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2194: ['SPIKE'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2196: ['PRODUCER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2198: ['CONSUMER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2200: ['DEPENDENCY'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 300: ['Accepted'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 302: ['Completed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 306: ['Defined'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 308: ['Missed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 320: ['Missed'] is better written in dot notation.
Error in ucomp/ObjContainer.js on line 701: Don't make functions within a loop.
Error in ucomp/ObjContainer.js on line 706: Don't make functions within a loop.
Error in ucomp/OthContainer.js on line 80: ['Accepted'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 82: ['Completed'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 85: ['Defined'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 87: ['Missed'] is better written in dot notation.
Error in ucomp/OthContainer.js on line 99: ['Missed'] is better written in dot notation.
Error in ucomp/SummaryContainer.js on line 507: Don't make functions within a loop.
Error in ucomp/DependencyContainer.js on line 513: Don't make functions within a loop.
Error in ucomp/DependencyContainer.js on line 518: Don't make functions within a loop.
Error in rmodel/DataLoader.js on line 1028: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1031: ['STRETCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1034: ['ARCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1037: ['REFA'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1040: ['INNOV'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1043: ['PROG'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1046: ['SPIKE'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1049: ['PRODUCER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1052: ['CONSUMER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1055: ['DEPENDENCY'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1060: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1420: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1422: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1425: ['FoundExtParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1427: ['FoundExtParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1429: ['FoundExtParentPSI'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1434: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1436: ['FoundExtParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1438: ['FoundExtParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1440: ['FoundExtParentPSI'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1445: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1447: ['FoundParent'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1449: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1503: ['FoundParentID'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1601: ['Objective'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 1803: Don't make functions within a loop.
Error in rmodel/DataLoader.js on line 2182: ['EPIC'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2184: ['STRETCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2186: ['ARCH'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2188: ['REFA'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2190: ['INNOV'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2192: ['PROG'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2194: ['SPIKE'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2196: ['PRODUCER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2198: ['CONSUMER'] is better written in dot notation.
Error in rmodel/DataLoader.js on line 2200: ['DEPENDENCY'] is better written in dot notation.
Creating App-debug.html
Creating App.html
Creating App-external.html
Creating App-uncompressed.html
Success
usxxkingc5m4:TestApp kingc5$

When I run grunt - it doesn't throw any JSHint errors and ignores what I tell it to ignore in the options below:

// The grunt file.
var module = module;
//this keeps the module file from doing anything inside the jasmine tests.
//We could avoid this by making all the source be in a specific directory, but that would break backwards compatibility.
if (module) {
module.exports = function (grunt) {
'use strict';

    var config, debug, environment, spec;
    grunt.loadNpmTasks('grunt-contrib-jasmine');
    grunt.loadNpmTasks('grunt-contrib-jshint');

    grunt.registerTask('test', ['jshint','jasmine']);
    grunt.registerTask('default', ['test']);

    spec = grunt.option('spec') || '*';
    config = grunt.file.readJSON('config.json');
    return grunt.initConfig({

        pkg: grunt.file.readJSON('package.json'),

        jasmine: {
            dev: {
                src: "./*.js",
                options: {
                    vendor:["https://rally1.rallydev.com/apps/"+config.sdk+"/sdk-debug.js"],
                    template: 'test/specs.tmpl',
                    specs: "test/**/" + spec + "Spec.js",
                    helpers: []
                }
            }
        },
        jshint:{
            options: {
                bitwise: true,
                curly: true,
                eqeqeq: true,
                forin: true,
                immed: true,
                latedef: true,
                noarg: true,
                noempty: true,
                nonew: true,
                trailing: true,
                browser: true,
                unused: 'vars',
                es3: true,
                laxbreak: true,
                '-W069': true,
                '-W083': true
            },
            apps: {
                files: {
                    src: [
                        'store/**/*.js',
                        'overrides/**/*.js',
                        'rmodel/**/*.js',
                        'test/**/*.js',
                        'ucomp/**/*.js'
                    ]
                }
            }
        }
    });

}
}

When I run grunt or npm test, I get

usxxkingc5m4:ObjectivesDashboard kingc5$ grunt
Running "jshint:apps" (jshint) task

11 files lint free.

Running "jasmine:dev" (jasmine) task
Testing jasmine specs via phantom
.
1 spec in 0.002s.

0 failures

Done, without errors.
usxxkingc5m4:ObjectivesDashboard kingc5$

[email protected] test /c4_working/TestApp
grunt

Running "jshint:apps" (jshint) task

11 files lint free.

Running "jasmine:dev" (jasmine) task
Testing jasmine specs via phantom
.
1 spec in 0.001s.

0 failures

Done, without errors.
usxxkingc5m4:TestApp kingc5$

build fails in apps without config.css

It appears the app builder assumes config.css, however this is NOT set in many of the apps currently in the app-catalog

Trying to build app-catalog/src/apps/releaseplanning fails with the following error:

Compiling the App.
/Users/johty01/Development/RallyApps/app-catalog/node_modules/rally-app-builder/node_modules/async/lib/async.js:81
        if (!arr.length) {

TypeError: Cannot read property 'length' of undefined
    at Object.async.forEach (/Users/johty01/Development/RallyApps/app-catalog/node_modules/rally-app-builder/node_modules/async/lib/async.js:81:17)
[ snip ]

Building app-catalog/src/apps/releasesummary has no issues.

Adding the following to the releaseplanning config.json file fixes the problem

"css": []

[QUESTION] Does app builder/test sdk provide coverage support?

Tried to do some local experiments using vanilla istanbul and grunt integration.

Haven't been really successful.

Please suggest if there are better means, until then I will try my best and share the findings.

Thanks.

Would be awesome to pass along the app version metadata

either from package.json, or the current git sha

Would be great to enable es6 support, transpilation

When cloning store the sha of the cloned version

rab run doesn't work on windows

can NOT install on Windows 10

Hi could someone please help?
@krmorse

It can NOT install on Windows 10.
Details please refer to the attached npm-debug.log

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN enoent ENOENT: no such file or directory, open 'c:\package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "rally-app-builder"
npm ERR! node v6.9.4
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs phantomjs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! c:\npm-debug.log