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

anathema

v0.2.1

Published

A task runner/orchestrator for people who aren't a fan of plugins.

Downloads

23

Readme

Anathema

Yet another task runner. So if you're reading this, the package is published but not considered stable, or something I would hitch your wagon to just yet.

I don't want to hastily commit to supporting a task runner before I've tried to use it myself for a while, but if you're still curious about why one would write a task runner, here's a quick rundown:

I don't like the plugin ecosystem

That's basically it, nearly all task runners have a plethora of dependency plugins required to make them usable. All I want is a task runner that fulfils these requirements:

  • doesn't require technology specific plugins to make it usable
  • doesn't force you to couple the build process for technologies together to make it usable (ala bundlers like Webpack and Fusebox)
  • makes the actual process of running the tasks reliable and easy to debug

So with those concepts in mind, my goal is not syntax reduction, blazing red hot performance, or a reduction in the need to configure tools. This is a build tool for people who want it to do what they told it to do, when they told it to do it, without relying on hundreds of extra dependencies in order to make it happen.

In short:

no plugins

no forced coupling

nice development experience

If you got this far, and you want to try it out despite its unfinished nature:

yarn add -D anathema

Add the following to your package.json:

{
  "scripts": {
    "anathema": "anathema --config/anathema.js"
  }
}

And run it with:

yarn anathema <taskname>

It'll default to running default if you don't provide one.