Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use as part of the test suite with Travis CI? #344

Closed
balupton opened this issue Mar 27, 2015 · 6 comments
Closed

How to use as part of the test suite with Travis CI? #344

balupton opened this issue Mar 27, 2015 · 6 comments

Comments

@balupton
Copy link
Contributor

I'd like it so my npm test that is performed on Travis CI runs my flow tests. To do this, I need to figure out:

  1. How to install flow on Travis (unfortunately it isn't a npm package)
  2. How to run the checks once it is installed and wherever it is installed to

I already have ESLint checks going with the babel-eslint parser.

@balupton
Copy link
Contributor Author

Similar thread about flow type support at eslint: eslint/eslint#2157

@samwgoldman
Copy link
Member

You can just download and unpack the latest .tar.gz file for your platform (probably Linux on Travis CI), which contains a binary. Travis CI lets you run arbitrary commands. For example, if you needed to compile a dependency from source: http://docs.travis-ci.com/user/installing-dependencies/#Installing-Projects-from-Source

@balupton
Copy link
Contributor Author

Cool, will look into it. Thanks! 👍

@balupton
Copy link
Contributor Author

Could the ocaml-to-js compiled version of flow be published to npm? That way we could just list flow as a devDependency in our npm package.json, then run it via ./node_modules/.bin/flow - which makes the process trivial

@aaronshaf
Copy link

I second @balupton's recommendation to publish to npm and give use access to node_modules/.bin/flow

@samwgoldman
Copy link
Member

So it looks like @gabelevi has been publishing binaries all over the place, from flow-bin on NPM to packages on opam, Homebrew, and of course the binaries.

I think this issue is resolved. Let me know if these sources don't work with your workflow.

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

No branches or pull requests

3 participants