Skip to content

Conversation

@Krinkle
Copy link
Member

@Krinkle Krinkle commented May 27, 2014

No description provided.

Travis is failing on two accounts: * "Error: No compatible version found: minimatch@'^0.3.0'" (because the version of npm that shipped with 0.8 doesn't support ^ * npm WARN engine stringify-object@0.1.8: wanted: {"node":">=0.10.0"} (current: {"node":"v0.8.26","npm":"1.2.30"}) npm WARN engine has-color@0.1.7: wanted: {"node":">=0.10.0"} (current: {"node":"v0.8.26","npm":"1.2.30"}) npm WARN engine configstore@0.2.3: wanted: {"node":">=0.10.0"} (current: {"node":"v0.8.26","npm":"1.2.30"}) npm WARN engine object-assign@0.1.2: wanted: {"node":">=0.10.0"} (current: {"node":"v0.8.26","npm":"1.2.30"})
@Krinkle
Copy link
Member Author

Krinkle commented May 27, 2014

Took over an hour for a worker to be available, but I finally present a passing Travis CI build!

@jzaefferer
Copy link
Member

@scottgonzalez do we have a place to document what node version we expect to be installed?

@scottgonzalez
Copy link
Member

engines in package.json?

@jzaefferer
Copy link
Member

That will have the same problem as our "common" dependencies, we'd have to update it in every project with a package.json. Anyway, I'm going to land this.

@Krinkle Krinkle deleted the travis-fix branch May 31, 2014 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants