npmpackage.info

Gathering detailed insights and metrics for flow-ignore-dev-deps

flow-ignore-dev-deps - 0.2.2 | npmpackage.info

flow-ignore-dev-deps

Generate [ignore] section for .flowconfig to make flow-bin faster

0.2.2

MIT

JavaScript

7.96 kB

2.3

Installations

npm install flow-ignore-dev-deps

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.11.1

NPM Version

5.6.0 Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

NumminorihSF

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

1 Stars

16 Commits

2 Watchers

1 Branches

1 Contributors

Updated on Apr 08, 2022

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

0.2.2

Package Id

flow-ignore-dev-deps@0.2.2

Unpacked Size

7.96 kB

Size

3.39 kB

File Count

NPM Version

5.6.0

Node Version

8.11.1

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

chai mocha

flow-ignore-dev-deps

This package update .flowconfig's ignore section with actual development dependencies. It allows to start flow server a bit faster and ignore flow issues in dev deps (incompatible flow's version for example).

To use it, you need .flowconfig and package-lock.json files to be exist in your project.

If these files already presents, run next:

1npx flow-ignore-dev-deps

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

4

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

2.3

/10

Last Scanned on 2025-07-14

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More