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

@ianwremmel/tracks-interactor

v4.0.0

Published

<!-- (optional) Put banner here -->

Downloads

14

Readme

tracks-interactor (@ianwremmel/tracks-interactor)

license standard-readme compliant npm (scoped) npm

Dependabot badge semantic-release

CircleCI

Codify your business logic

Inspired by the Interactor gem, this library provides a pattern for encapselating business logic into small, testable units.

Table of Contents

Install

npm install @ianwremmel/tracks-interactor

Define your interactor. You'll need to tell it about the shapes of the data it will accept and produce. Then, you'll need to define call, which does the interactor's work. call accepts a Context<T> and returns a Context<R>. (In the following example, T is AuthToken and R is Model<User>).

import {Interactor} from 'interactor';

type AuthToken = string;
type User = Model<User>;

class Authorize extends Interactor<AuthToken, User> {
    call() {
        const user = await User.findByToken(this.context.data);
        if (!user) {
            this.context.fail('could not find user for specified token');
        }
        return user;
    }
}

Then, use interact to invoke your Interactor (e.g., in an express route).

import {Authorize} from './interactors/authorize';
import {interact} from 'interactor';
import express from 'express';

const router = express.Router();

router.use(async (req, res, next) => {
    const context = await interact(
        Authorize,
        new Context(req.headers.authorization)
    );

    if (context.failure) {
        next(401);
    }
});

router.get('/account', (req, res) => {
    res.render('account');
});

Differences from the Interactor Gem

  • The gem invokes a given Interactor via its static call method. TypeScript doesn't make type arguments visible to static methods, so we use the bare method interact as a stand-in for Interactor.call().
  • after, before, and around don't exist. A previous version of this library included them, but having not used that portion of the library for over a year, they're continued maintencance didn't seem worth it.Î
  • Organizers don't exist. A previous version of this library included them, but having not used that portion of the library for over a year, they're continued maintencance didn't seem worth it.

Breaking Changes

  • A previous version of this package expected a services object to be passed to interact. You should just put your services on the context.

    Instead of

    interact(services, MyInteractor, {...args});

    do

    interact(MyInteractor, {services, ...args});

Maintainer

Ian Remmel

Contribute

PRs Welcome

License

MIT © Ian Remmel 2019 until at least now