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 🙏

© 2025 – Pkg Stats / Ryan Hefner

data-seep

v0.3.4

Published

Reactive Data Seep

Readme

Reactive Data Seep

NPM Build Status Code Quality Coverage GitHub Project API Documentation

Code utilizing Reactive Data Seep pattern looks like this:

await withLogger({ level: LogLevel.DEBUG }, async logger => {
  logger.info('Connecting to database');

  await withDatabase(
    {
      uri: 'postgresql://dbuser:[email protected]:3211/mydb',
    },
    async db => {
      logger.info('Starting HTTP server');

      await withHttpServer(async server => {
        server.dispatch(
          {
            path: '/api/user',
            method: 'GET',
          },
          async ({ request, response }) => {
            const id = parseInt(request.url.searchParams.get('id'));
            const user = await db.query('SELECT name, email FROM user WHERE id = :id', { id });

            response.setHeader('Content-Type', 'application/json');

            await response.send(JSON.stringify(user));
          },
        );
        server.dispatch(
          {
            path: '/api/user',
            method: 'PUT',
          },
          async ({ request, response }) => {
            const user = JSON.parse(await request.read());
            const { id } = await db.query('INSERT INTO user (name, email) VALUES (:name, :email) RETURNING id', user);

            response.setHeader('Content-Type', 'application/json');

            await response.send(JSON.stringify({ id }));
          },
        );
        server.dispatchError(
          {
            type: NotFoundError,
          },
          async ({ response, error }) => {
            response.setHeader('Content-Type', 'application/json');
            response.setStatus(404);

            await response.send(JSON.stringify({ error: String(error.message) }));
          },
        );
        server.dispatchError(async ({ response, error }) => {
          response.setHeader('Content-Type', 'application/json');
          response.setStatus(500);

          await response.send(JSON.stringify({ error: String(error) }));
        });

        await Promise.any([
          withSignal(
            {
              signal: 'SIGINT',
            },
            signal => {
              logger.info('SIGINT received');

              return Promise.reject(signal);
            },
          ),
          server.listen({ post: 8080 }),
        ]);
      });

      logger.info('HTTP server stopped');
    },
  );

  logger.info('Disconnected from database');
});

The pattern relies on variable scoping rules. In particular, the data inflow into outer scope seeps through other data faucets to inner scopes.

A data faucet function implementing this pattern accepts an asynchronous sink function as its last argument. A sink function accepts an inflow value as its only argument. The inflow value exists while the sink processing it. After that, the value is no longer valid.

Implementing this pattern does not require the knowledge or use of any third-party libraries or APIs. However, in more complicated scenarios the tools provided by this package may be of help.