npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

check-flow-annotation

v1.0.4

Published

A basic flow type annotation checker

Downloads

590

Readme

Build Status

npm License Downloads/month

check-flow-annotation

This is a very fast and simple package to check your flow annotation coverage over your project.

It basically test if your files all starts with a // @flow or // @flow strict.

It's made to be included in your CI to prevent to forget some type annotations. It's very fast, and allow some customisations.

# install with yarn
yarn add check-flow-annotation -D
# install with npm
npm install check-flow-annotation --save-dev

# usages in your CI config
check-flow-annotation ./my/path ./my/other/path

# with options
check-flow-annotation ./my/path --strict
check-flow-annotation --strict ./my/path # same

# exclude some paths
check-flow-annotation ./my/path --exclude='build*','.src/static/*'
check-flow-annotation ./my/path -x 'build*','.src/static/*' #same, small version
check-flow-annotation ./my/path -x 'build*' -x '.src/static/*' #same

# exclude jsx files
check-flow-annotation ./my/path --exclude='*.jsx'

# check another anotation on first line
check-flow-annotation ./my/path --check='@flow weak'
# help
check-flow-annotation -h

Usage: check-flow-annotation.js [options] path1 path2 path3 etc

  By default it checks every ".js", ".jsx" and ".mjs" in your project,
  but you can filter it with exclude option

  Note that options are written "--option=value"
  but short versions are written "-o value"

  --help, -h
    Displays help information about this script
    'index.js -h' or 'index.js --help'

  --version
    Displays version info
    index.js --version

  --strict, -s
    Force to check "@flow strict"

  --exclude, -x
    Allow to exclude certain paths or extensions,
                  it‘s a comma separated value
    example: 'build*','.src/static/*'
                  will be merged with default array:
                  ['node_modules*', '.git*', 'flow-typed*', '.*', '!*.+(js|jsx|mjs)']

  --check, -c
    Set a custom check
    '@flow weak' or '@no flow'