<commit_before>_**NOTE:** The [`flow-typed` CLI](https://www.npmjs.com/package/flow-typed) is currently in beta. Please try it out and report any issues you encounter. Thanks!_

<img 
  alt="Flow Logo" 
  src="https://raw.githubusercontent.com/flowtype/flow-typed/master/flow-typed-logo.png"
  width="400"
/>

`flow-typed` is a [repository](https://github.com/flowtype/flow-typed/tree/master/definitions) of third-party 
[library interface definitions](http://flowtype.org/docs/third-party.html) 
for use with [Flow](http://flowtype.org/).

You can grab definitions directly from this GitHub repo, or you can use the CLI (currently in beta) to install a libdef for a given library:
```bash
$ npm install -g flow-typed

$ cd /path/to/my/project
$ flow-typed install -f 0.27 rxjs@5.0.0 # `-f 0.27` specifies the Flow version we're using for this project
'rxjs_v5.0.x.js' installed at /path/to/my/project/flow-typed/npm/rxjs_v5.0.xjs
```

## Huh?

When you start a project with Flow, **you might want to use some third-party 
libraries that were *not* written with Flow**. Flow is usually able to work it's 
way around this, but at the unfortunate cost of typing those third-party modules 
as `any`. As a result, Flow can't give errors if you accidentally mis-use the 
library (nor will it be able to auto-complete the library).

To address this, **Flow supports 
[library definitions](http://flowtype.org/docs/third-party.html)** which allow 
you to describe the interface of a module or library separate from the <commit_msg>typo (#215)<commit_after>_**NOTE:** The [`flow-typed` CLI](https://www.npmjs.com/package/flow-typed) is currently in beta. Please try it out and report any issues you encounter. Thanks!_

<img 
  alt="Flow Logo" 
  src="https://raw.githubusercontent.com/flowtype/flow-typed/master/flow-typed-logo.png"
  width="400"
/>

`flow-typed` is a [repository](https://github.com/flowtype/flow-typed/tree/master/definitions) of third-party 
[library interface definitions](http://flowtype.org/docs/third-party.html) 
for use with [Flow](http://flowtype.org/).

You can grab definitions directly from this GitHub repo, or you can use the CLI (currently in beta) to install a libdef for a given library:
```bash
$ npm install -g flow-typed

$ cd /path/to/my/project
$ flow-typed install -f 0.27 rxjs@5.0.0 # `-f 0.27` specifies the Flow version we're using for this project
'rxjs_v5.0.x.js' installed at /path/to/my/project/flow-typed/npm/rxjs_v5.0.xjs
```

## Huh?

When you start a project with Flow, **you might want to use some third-party 
libraries that were *not* written with Flow**. Flow is usually able to work its 
way around this, but at the unfortunate cost of typing those third-party modules 
as `any`. As a result, Flow can't give errors if you accidentally mis-use the 
library (nor will it be able to auto-complete the library).

To address this, **Flow supports 
[library definitions](http://flowtype.org/docs/third-party.html)** which allow 
you to describe the interface of a module or library separate from the 
{'fraction_non_alphanumeric': 0.11822660098522167, 'fraction_numerical': 0.011494252873563218, 'mean_word_length': 4.16271186440678, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 6, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6657294', 'n_tokens_mistral': 999, 'n_tokens_neox': 945, 'n_words': 357}