Package Details: flow 0.50.0-1

Git Clone URL: (read-only, click to copy)
Package Base: flow
Description: A static typechecker for JavaScript
Upstream URL:
Keywords: javascript
Licenses: BSD
Conflicts: flow-bin
Provides: flow
Replaces: flow-bin
Submitter: Gordin
Maintainer: None
Last Packager: jtgoguen
Votes: 14
Popularity: 0.000916
First Submitted: 2014-11-19 15:18
Last Updated: 2017-07-13 16:16

Latest Comments

1 2 3 4 Next › Last »

lxndr commented on 2018-12-06 22:45

Could you please update this package?

jtgoguen commented on 2017-05-12 04:30

There's a build error I've been trying to track down a fix for blocking this. Output is at if anyone knows ocaml and can help out.

jtgoguen commented on 2016-11-22 16:13

This is going to take a little while, there's now a bunch of nodejs build dependencies without existing packages.

jtgoguen commented on 2016-04-22 16:25

Along with the version bump I added a FLOW_RUNTESTS_PARALLELISM limit. If the environment variable is defined it'll just run 'make test', if not defined it runs 'make test' with FLOW_RUNTESTS_PARALLELISM=4.

potatoe commented on 2016-04-20 17:05

I'm hitting out-of-memory errors during the test/check phase of the build with 0.23.0-1 (I was able to build previous versions). I only have 16GB of RAM and no swap. I can successfully build by running fewer tests in parallel than the default.

If anyone else runs into this, you'll want to set the environment variable FLOW_RUNTESTS_PARALLELISM to a lower number (it defaults to 16). I used 4, which seems to require only about 8GB of RAM (16 parallel tests would presumably require somewhere around 32GB or RAM).

Even if you are able to build, if you're hitting your swap it might be faster overall to run fewer tests in parallel to avoid swapping.

I just edited the PKGBUILD to just call 'FLOW_RUNTESTS_PARALLELISM=4 make test' instead of 'make test', but it should also be possible to pass the variable as part of the environment through to makepkg if you don't want to edit the file.

jtgoguen commented on 2016-03-12 18:59

Looks like 0.22.2 got removed, 0.22.1 is latest now.

jtgoguen commented on 2016-03-03 22:34

I'm travelling for the next week and a bit without my laptop, the update to 0.22.2 will be delayed unless someone else wants to jump on as co-maintainer. The update should be as simple as updating the version number and the shasum.

Svenstaro commented on 2015-11-19 20:44

You can just use for now.

jtgoguen commented on 2015-11-19 20:33

Yup, looks like it works. That's going to be annoying. So I guess we're stuck waiting for the next release.

jtgoguen commented on 2015-11-19 20:27

Interesting, it worked before now in a different place it doesn't. Consistently. Sounds like, I'll see if a commit after that works and if so we'll just need to wait for 0.18.2+.