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

require-satisfied

v1.0.1

Published

Search for "REQUIRE" in comments and report if no matching "SATISFIED" found

Downloads

125

Readme

require-satisfied

A package that helps developers to track assumptions that are manually managed or cannot be verified with static or runtime assertion.

Usages and Examples

Same-File Require-Satisfied

// ...
function doHighComplexityWork() {
  // ...
  return {
    // REQUIRE: when `status` is 1, the caller must do something
    status: 1
    // ...
  }
}

function main() {
  // ...
  const { status } = doHighComplexityWork()
  if (status === 1) {
    // SATISFIED: when `status` is 1, the caller must do something
    // ...
  }
}

Require-Satisfied in Block Comment

// ...
function doHighComplexityWork() {
  // ...
  return {
    /*
    REQUIRE: when `status` is 2,
    the caller must do something

    Multiline is only supported in block comments
    Use a blank line to indicate the end of the REQUIRE/SATISFIED
    */
    status: 2
    // ...
  }
}

function main() {
  // ...
  const { status } = doHighComplexityWork()
  if (status === 2) {
    // SATISFIED: when `status` is 2, the caller must do something
    // ...
  }
}

Cross-File Require-Satisfied

// File: a.ts
// ...
function doHighComplexityWork() {
  // ...
  return {
    /*
    REQUIRE(extern): when `status` is 3,
    the caller must do something
    */
    status: 3
    // ...
  }
}
# File: b.py
def main():
  '''
  REQUIRE: block comment also supported

  SATISFIED: block comment also supported
  '''
  # ...
  status = grpc.doHighComplexityWork().status
  if status == 3:
    # SATISFIED(extern): when `status` is 3, the caller must do something
    # ...

CLI Usage

Script: check

npm run check -- \
  --include "some/glob/**/*" \
  --include "another/glob/**/*" \
  --exclude "**/*.bad" \
  --exclude "**/*.so.bad"

If no warning or error is found, the script exits with code 0, and the console output looks like:

16 file(s) scanned
0 warnings
0 errors

If there is any warning or error found, the console output looks like:

ERROR: Missing corresponding SATISFIED for REQUIRE(extern): id 100 at
  /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:6:20

ERROR: Missing corresponding REQUIRE for SATISFIED(extern): id 101 at
  /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:7:22

WARN: Duplicated SATISFIED: id 001 at
  /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:9:34
  First defined at /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:5:37

WARN: Duplicated REQUIRE(extern): id 100 at
  /home/foo/nodejs/require-satisfied/samples/project/sample.js:6:20
  First defined at /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:6:20

WARN: Duplicated SATISFIED(extern): id 101 at
  /home/foo/nodejs/require-satisfied/samples/project/sample.js:7:22
  First defined at /home/foo/nodejs/require-satisfied/samples/project/sample.dup.js:7:22

ERROR: Missing corresponding SATISFIED for REQUIRE(extern): qwerty at
  /home/foo/nodejs/require-satisfied/samples/sample.js:15:22

3 file(s) scanned
3 warning(s)
3 error(s)

The exit status, however, will only be 1 if there is at least one error.

Try playing with README and samples:

  • npm run check -- -i README.md
  • npm run check -- -i "src/**/*"
  • npm run check -- -i "samples/project/**/*"
  • npm run check -- -i "samples/project/**/*" -x "**/*.dup.js"
  • npm run check -- -i "samples/**/*" -x "**/*.py" (the one produced the output above)

Bin: require-satisfied-check, rs-check

Alias of script check.