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

@breuleux/engage

v0.0.0

Published

Incremental task runner

Downloads

1

Readme

engage

Incremental build tool with automatic dependency tracking. Very alpha.

Principles

  • Incremental: engage knows what has been done, so it doesn't need to do it again. You change one file, it recompiles one file.

  • Fast: see above.

  • Easy: engage's API is simple and doesn't really require any new concepts or boilerplate.

  • No frivolous plugins: any function that operates a source to source transform can just be used directly, there is no need for a specific plugin to, say, transform Markdown files with engage.

Examples

You may run this example with node directly.

engage = require("engage");
marked = require("marked");

task = engage.task;
Write = engage.Write;
Renamer = engage.Renamer;

// This task concatenates all files that end in `.cat` (in an unspecified order)
// into the file ./out/whole
tCat = task(function(root) {
    var accum = "";
    root.find("**/*.cat").map(function (file) {
        accum += file.text;
    });
    return Write("./out/whole", accum);
});

tMain = task(function () {

    // We resolve the directory in which we will get the contents
    var contentRoot = this.get(this.rootPath);

    // This compiles all our markdown files. Note that we use the
    // marked function directly, there's no need for a plugin.
    // this.rename refers to the rename object we build in the options below,
    // so e.g. content/index.md will be compiled into out/index.html
    var compiledMarkdown =
        contentRoot.find("**/*.md").map(function (file) {
            return Write(this.rename(file, {extension: ".html"}), marked(file.text));
        });

    // This is shorthand for the above.
    var compiledMarkdown =
        contentRoot.find("**/*.md").mapFile({extension: ".html"}, marked);

    // It is necessary to return the array of Write/etc. instructions to execute.
    // The instructions can be nested.
    return [
        compiledMarkdown,
        tCat(contentRoot)
    ];
});

// The task will receive these options into `this`.
opts = {
   debounce: 100,
   rename: Renamer({from: "./content", to: "./out"}),
   readOnly: ["./content"],
   rootPath: "./content"
};

engage(tMain, opts).run();

The Earl Grey language has some macro bindings for engage that makes it more pleasant to use. Here's the above example in Earl Grey:

require-macros:
   engage -> task

require:
   marked
   engage -> (Write, Renamer)

task t-cat(root) =
   var accum = ""
   root.find("**/*.cat").map with file ->
      accum += file.text
   Write("./out/whole", accum)

task t-main() =
   content-root = @get(this.root-path)
   compiled-markdown = content-root.find("**/*.md").map with file ->
      Write(@rename(file, extension = ".html"), marked(file.text))
   compiled-markdown-2 =
      content-root.find("**/*.md").map-file(extension = ".html", marked)
   {compiled-markdown, t-cat(content-root)}

engage(t-main, opts).run() where opts = {
   debounce = 100
   rename = Renamer(from = "./content", to = "./out")
   read-only: {"./content"}
   root-path: "./content"
}