Travis Builds are failing

[rickhuizinga]

I'm not sure why our Travis builds are failing, only under NodeJS 0.8. See: https://travis-ci.org/nlaplante/angular-google-maps/builds/26974519

It's been happening inconsistently for some time. See: https://travis-ci.org/nlaplante/angular-google-maps/builds

[cthrax]

It really looks to me like an NPM issue. It fails fetching something the first time, then the retry says it's an invalid version. Do we need to continue supporting npm 0.8?

[rickhuizinga]

Hmmm...

I think its related to this: npm/npm#4587 (comment)

We used npm >= 0.10.16 to add the lodash devDependency to our package.json. It specified the dependency as ^2.4.1 which breaks installations using npm versions <= 0.10.15.

We should be able to avoid the failure messages by changing the lodash dependency to ~2.4.1. I'll give that a try now...

[rickhuizinga]

Our lodash dependency notation was not the specific problem.

However I think the ^ vs ~ dependency notation is the cause of the failures. It is highly likely that any one module in our dependencies uses the ^ notation for a dependency notation in its package.json. This will result in the Travis build failure we are seeing.

Is it possible to configure our Travis builds not to use NodeJS 0.8???

[cthrax]

I think that just entails editing the .travis.yml to be - "0.10" instead of - "0.8".

[rickhuizinga]

P.S. Our NodeJS build error was due to a package dependency with a ^ notation:

npm ERR! Error: No compatible version found: chalk@'^0.4.0'

It looks like we'll just have to drop NodeJS 0.8 from our Travis builds. I've pushed a commit with a modified .travis.yml file, and the builds are now reporting a successful status.