GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/325

    tooling: don't require globally installed grunt

    `grunt` is one of our dependencies, using `npm run dev` we can
    substitute `grunt dev` which requires a globally installed grunt
    which can have a completely different version than we are defining
    in our `package.json`
    
    Using `scripts` in the npm package.json file npm takes care that
    our locally installed modules which provide a `bin` file are part
    of the env of the executing context.
    
    New commands:
    
    ```
    npm run dev
    npm run nightwatch
    ```

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton npm-run

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/325.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #325
    
----
commit c028e4ad9ec044e862687d8fdc3410bca0ab45be
Author: Robert Kowalski <r...@kowalski.gd>
Date:   2015-03-22T16:01:44Z

    tooling: don't require globally installed grunt
    
    `grunt` is one of our dependencies, using `npm run dev` we can
    substitute `grunt dev` which requires a globally installed grunt
    which can have a completely different version than we are defining
    in our `package.json`
    
    Using `scripts` in the npm package.json file npm takes care that
    our locally installed modules which provide a `bin` file are part
    of the env of the executing context.
    
    New commands:
    
    ```
    npm run dev
    npm run nightwatch
    ```

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to