Closed bjacobel closed 7 years ago
Hm. The test failure I'm getting for both node 4 and 6 on Travis on this branch is reproducible locally on master on node 4.
I think the reason this is failing is that:
Encrypted variables are not available to untrusted builds such as pull requests coming from another repository
(from the Travis env vars doc)
It looks like the tests depend on an AWS_SECRET_ACCESS_KEY
and AWS_ACCESS_TOKEN_ID
being available. They're set as encrypted secrets in this project's .travis.yml
, but they're not made available to "untrusted builds", and as a result no build that's run on a PR from a fork can pass.
Can somebody from Mapbox help me get this resolved? It doesn't look like I'll be able to contribute to this repo the way things are currently configured.
Tests pass for me with env set up, and they'll pass in master. Thanks @bjacobel!
Currently Cloudfriend's package.json specifies the following:
Under this rule, Node 6 (which is due to become the current LTS Node version on 10/18/2016) is not a supported engine.
This becomes an issue when trying to install Cloudfriend on Node 6 using npm with the
engine-strict
config parameter, or with a node package manager like Yarn that checks engine versions more strictly than NPM does by default.npm with engine-strict example
yarn example
This PR adds changes the package.json engine setting to accept any Node version greater than 4.4.7, and adds Node 6 to the Travis build matrix.