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 🙏

© 2026 – Pkg Stats / Ryan Hefner

flekk

v0.10.5

Published

YAML API testing library

Readme

Flekk

Low code testing library. Test your APIs using only YAML.

Install

npm i -g flekk

Files

All test and setup files live in the $APP_ROOT/test directory, and written with weblang.

Test files must en with .test.yml, for example project.test.yml. Setup files, which can be included in test files, must end with .setup.yml, like in login.setup.yml.

Config

Config files must end in .config.yml, like in app.config.yml.

The default config file should be added in $APP_ROOT/test/flekk.config.yml:

# The URL and port of the app you are testing
url: http://localhost
port: 5061

# Database setup for the db command, requires mongodb
db:
  name: flekk-test

The default config file is always loaded, and then other config files are merged on top of that.

Commands

There are 6 basic commands:

  • config - load config files
  • setup - run setup files
  • api - query an action endpoint
  • db - access the database
  • test - test a value
  • log - log a value to console

This is how to use them:

# Load config file
@config: app

# Load multiple config files, will be merged
@config:
  - app
  - remote

# Run setup file
@setup: login

# Run multiple setup files
@setup:
  - create-user
  - login

# Test the site/create API
@api$result:
  action: site/create
  values:
    name: hello
  auth: $auth
@test$result:
  id:
    is: id

# Test database values
@db$site:
  action: site/get
  query:
    id: $result.id
@test$site:
  id:
    required: true

# Print value to terminal
$hello: world
log: $hello

Setup

Run the tests with:

# Run all tests
flekk

# Run matching tests
flekk names

# With nodemon
nodemon -e js,mjs,json,yml,css,md --exec flekk

Add this to you package.json file to run with npm:

"scripts": {
  "test": "nodemon -q -e js,mjs,json,yml,css,md --exec flekk"
}

Then run with npm run test in your application.

MIT Licensed. Enjoy!