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

@systemfsoftware/oxlint-plugin-effect-workflow

v4.0.0

Published

Oxlint rules enforcing the purity and exhaustiveness obligations of a Workflow.make decision body.

Downloads

2,358

Readme

@systemfsoftware/oxlint-plugin-effect-workflow

npm license

An oxlint plugin for Effect-TS teams who want decision bodies that stay pure.

x @systemfsoftware/effect-workflow(workflow-match-exhaustive): Match.orElse is forbidden.
  Expected: Match.value(...).pipe(Match.tag(...), Match.exhaustive).
  Actual: a fallback arm over a closed union.
  Fix: dispatch exhaustively over a closed tagged union so a new variant fails to compile.
pnpm add -D @systemfsoftware/oxlint-plugin-effect-workflow

The Problem

A business decision is meant to be a pure core — typed command in, tagged decision out. Add a Date.now(), an if, a throw, or a database import and it still compiles, still passes a standard lint config, and still passes its tests. The impurity is only wrong relative to a convention no tool knows about, and it surfaces months later as a test that cannot be written without mocking a clock.

These three rules make that convention executable at the boundary that constructs the decision — the body of a Workflow.make(...) call — and at the file that holds it.

Shape is not policed here. What a decision must declare is decided by the mechanism that builds the workflow and the compiler it runs under, not by a walker reading the finished file. Channel inhabitation is refused by Workflow.make: its Inhabited constraint resolves a never decision or error channel, or an error channel carrying no _tag, to a marker whose member name is the diagnostic — __WORKFLOW_DECISION_CHANNEL_IS_NEVER__, __WORKFLOW_ERROR_CHANNEL_IS_NEVER__, __WORKFLOW_ERROR_CHANNEL_CARRIES_NO_TAG__ — so a decision that cannot succeed, or whose failure carries nothing a consumer can dispatch on, does not compile. async and ambient impurity are refused by the Effect language-service policy every package inherits from this repo's shared config.

Quick Start

// oxlint.config.ts
import effectWorkflow from '@systemfsoftware/oxlint-plugin-effect-workflow'
import { defineConfig } from 'oxlint'

export default defineConfig({
  jsPlugins: ['@systemfsoftware/oxlint-plugin-effect-workflow'],
  rules: { ...effectWorkflow.configs.recommended.rules },
})
pnpm oxlint src

On a clean codebase: Found 0 warnings and 0 errors.

To adopt gradually, drop the spread and name rules individually as '@systemfsoftware/oxlint-plugin-effect-workflow/<rule>': 'warn'. Entries placed after the spread override it.

Rules

| Rule | Reports | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | make-file-location | A Workflow.make call in a file that is not a single-segment <stem>.workflow.ts, or a second Workflow.make call in the same file | | workflow-match-exhaustive | Match.orElse in a Match.tag pipe; Match.orElse as the fallback of a predicate or literal dispatch over an open type (close the variant type first); or a Match.tag dispatch with no Match.exhaustive — all scoped to a Workflow.make argument body | | make-body-purity | A reference inside a Workflow.make argument body that resolves to I/O — an impure import, a module-level mutable, a mutable local, or an ambient global; and control-flow keywords past the one converging first-statement guard |

FAQ

Q: Failed to parse config … Unknown plugin: '@systemfsoftware/oxlint-plugin-effect-workflow'. A: The name was placed in oxlint's plugins field, which takes built-in namespaces only. JavaScript plugins load through jsPlugins; their rules go in rules.

Q: Installed, but nothing is reported. A: make-body-purity and workflow-match-exhaustive are boundary-scoped — only Workflow.make argument bodies are examined. make-file-location keys on the filename: it reports a Workflow.make call in a file that is not a single-segment <stem>.workflow.ts, or a second call in the same file.

Requirements

effect and TypeScript 5.0+ as peers. Rules read syntax only; no type information or tsconfig wiring needed.

Contributing

AGENTS.md

License

Apache 2.0