v1.11.4

• Really ignore tests when packaging (#162)

Maintenance

• Convert from greenkeeper to dependabot
• Update dependency versions to remove most dependabot alerts.

Minimum version supported is still nodejs 8, but upgrading to 10 is recommended.

v1.11.2

Maintenance

Updates to @babel packages (v6 to v7)
Updates some dependency versions to remove most security alerts.

v1.11.0

Likely to cause new failures:

Guard against @flow annotations that are after a code statement.

• Previously files with some javascript above the first @flow comment were incorrectly marked as having flow coverage when the flow interpreter would actually consider that file untyped. This release correctly identifies those as untyped.
  It is possible that this will cause new failures in existing projects that had incorrectly typed files.

Maintenance:

• Bump glob to dependency v7.1.4
• Bump flow-bin dependency to v0.98.1
• improve internal flow type coverage

v1.10.1

Speedup AST generation at runtime by parsing file content in-process.

This is faster than shelling out with flow ast and doing a JSON.parse() call.

• Our unit tests run about 8 seconds (20%) faster with this change.
• On a large codebase of about 8,300 files runtime was reduced from ~10.5minutes to ~2minutes.

v1.10.0

Adds the json output format available to the cli. You can output a report to stdout with -o json or --output json or put the json data directly in a file by using --json-file /path/to/file.json.

Also adds the --level flag which supercedes the existing --allow-weak flag. Using --level you can specify what type of strictness is allowed in your repo. For example using --level=flowstrict requires that all files declare @flow strict; any files with @flow or @flow strict-local would cause the program to exit with an error code.

The default value is --level=flow, now --allow-weak is an alias for --level=flowweak. If you never want to exit with an error code then set --level=any and all @flow or no-flow files will be allowed.

You can read more about these flags in the updated README or by running npx flow-annotation-check --help to see the detailed cli flags & help.

v1.9.1

Include all the lib/ folders when pushing to npm.

v1.9.0

Adds a --summary-file output option. This prints a text-format summary of your project to a file, in this format:

@flow 35 (92.11%)
@flow strict 2 (5.26%)
@flow strict-local 1 (2.63%)
@flow weak 0 (0%)
no flow 0 (0%)
Total Files 38

The summary ignores any filters that are normally applied to the list output. The summary is also included in other output files such as --csv-file or --html-file when combined with --show-summary option.

Also updates dependencies.

v1.8.0

Improve annotation detection to match flow internals. Now allows for other content to be on the same line such as // @flow @preventMunge.

v1.7.0

Adds support for detecting @flow strict annotations and including them in the reports. See #44

• The --list-files flag now allows the flowstrict option to only select the strict files. The --allow-weak flag is always ignored with this option.
• Setting --list-files to flow will also include all strict files.

See the cli help, or parser-test.js.snap for the full arguments.

Also bumps all dependencies to the latest versions.