Skip to content

Storing configuration in the `scripts` field is no longer supported by npm #2

Closed
kitcambridge opened this Issue Nov 19, 2013 · 1 comment

2 participants

@kitcambridge

npm now requires that all scripts members be strings (npm/npm#4156), so it is no longer possible to store options in the travis-cov field like so.

{
    "scripts": {
        "test-cov": "mocha --require blanket -R travis-cov test/test-*.js",
        "travis-cov": {
            "threshold": 95
        }
    }
}

I can submit a pull request that moves the travis-cov configuration elsewhere—and checks scripts for backward-compatibility—but wanted to check beforehand. Where should this new field reside?

@kitcambridge kitcambridge added a commit to kitcambridge/travis-cov that referenced this issue Nov 19, 2013
@kitcambridge kitcambridge Migrate from `scripts` to `config`.
Closes #2.
a46cb19
@pghalliday

+1

@alex-seville alex-seville closed this in #3 Dec 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.