Skip to content
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.

improve circle ci tests #161

Closed

Conversation

DominikGuzei
Copy link
Contributor

No description provided.

@apollo-cla
Copy link

@DominikGuzei: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

@tmeasday
Copy link
Contributor

Interesting. Can you explain the rationale in moving the chimp command out of package.json into it's own script?

@DominikGuzei
Copy link
Contributor Author

DominikGuzei commented Jul 11, 2016

@tmeasday that was done because i ran into several issues with chimp and Node.js 0.10.x that Meteor is using. So the problem is that if you run Node via meteor npm run you are forced to the Meteor node version. if you run it from outside you can have Node.js 5+ installed globally and basically run Meteor and chimp with different versions.

Here are the related Github issues and discussions:
xolvio/chimp#204
xolvio/chimp#201

Bottom line: Meteor really has to upgrade to use up-to-date Node.js versions soon. Until then, we cannot use the package.json with chimp.

tmeasday and others added 18 commits July 12, 2016 10:59
… its package.json. We have Node 0.10.45. So, we have to specify using <1.10.1 for now.
Used the NPM "denodeify" package to supply an equivalent. This package has no other dependencies and uses the global Promise definition, so hopefully it won't run into problems with Fibers.
…able ESLint to tolerate conditional imports and exports.
in imports/startup/client/routes.app-test.js:

  35:22  error  Unexpected block statement surrounding arrow body  arrow-body-style
[email protected] incorporates import-js/eslint-plugin-import#415 to fix a clash between eslint-plugin-import and eslint-plugin-meteor that was only occurring when running under the NPM/Node combination used by the Meteor 1.3.4.x series of releases.
Use `meteor npm install`
@tmeasday
Copy link
Contributor

Makes sense @DominikGuzei.

We just updated the master branch to 1.3.4.4, can you please rebase/merge?

PS we now have a 1.4-beta.10 release; if you'd prefer to write this PR against that, and we can merge this in at the same time as updating to 1.4?

@DominikGuzei
Copy link
Contributor Author

DominikGuzei commented Jul 13, 2016

damn … that's why you should never use rebase. Just screwed up the whole PR 😢
Reopened at #164

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants