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

@amykit/plugin-file-store

v0.4.0

Published

Work records kept as one file per item.

Readme

@amykit/plugin-file-store

Work records kept as one file per item.

A plugin for amy. It provides the brief port and the store port.

Install

npm install -g @amykit/plugin-file-store

Then name it in ~/.amy/config.yaml:

workflows:
  your-profile:
    plugins:
      - "@amykit/plugin-file-store"

Configuration

plugins:
  "@amykit/plugin-file-store":
    briefsDirectory: "briefs"
    directory: "tickets"

| Setting | Type | Required | Default | What it is | | :-- | :-- | :-- | :-- | :-- | | briefsDirectory | string | no | briefs | where the briefs are kept, relative to the state directory. One per workflow, for the same reason the records are | | directory | string | no | tickets | where the records are kept, relative to the state directory. One per workflow, so two profiles under one .amy do not read each other's work |

Every field is checked at boot against the schema this package declares. A key that is not one of the above is a refusal naming the plugin and the key, not a setting that silently never applied.

Where the reasoning is

Licence

MIT