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

@nasa-jpl/plandev-actions

v1.3.0

Published

Library of JS helpers used by PlanDev/SeqDev Actions

Readme

plandev-actions

Javascript package for use with PlanDev/SeqDev actions.

PlanDev/SeqDev Rebrand

This product was formerly known as Aerie Actions and is now named PlanDev/SeqDev Actions. What to know:

  • The planning product, including modeling, simulation, scheduling and constraint-checking, is now named PlanDev
  • The sequencing product, including the sequence editor, workspaces, and actions, is now named PlanDev/SeqDev
  • All features and functionality remain the same

For the latest documentation, visit: PlanDev Documentation

Example

See PlanDev/SeqDev Actions docs for more information - full API reference coming soon.

Action results: data vs report

An action returns an ActionResult:

type ActionResult = {
  status: 'FAILED' | 'SUCCESS';
  data: any; // machine-readable output (rendered as raw JSON in the "Results" block)
  report?: string; // optional human-facing Markdown summary (rendered in the "Report" block)
};
  • data is the structured, machine-readable output. The UI shows it as pretty-printed JSON in the Results block.
  • report is an optional Markdown string for the things a person needs to read and click. The UI renders it in a Report block shown above Results — so you no longer need to stuff human-readable output into logs.

Example

export async function main(parameters, settings, actionsAPI) {
  // ... do work ...
  return {
    status: 'SUCCESS',
    data: { violations: 2, checked: 148 },
    report: [
      '## Constraint check complete',
      '',
      'Checked **148** constraints — <span style="color: #c00">2 violations</span> found.',
      '',
      '| Constraint | Result |',
      '| --- | --- |',
      '| Power margin | <span style="color: green">OK</span> |',
      '| Thermal window | <span style="color: #c00">**Violated** at 04:12Z</span> |',
      '',
      'See the [full report](https://example.com/runs/123) for details.',
    ].join('\n'),
  };
}

Supported Markdown

The Report block accepts a curated, GitHub-flavored Markdown subset:

  • Headings, paragraphs, line breaks, horizontal rules
  • Bold, italic, ~~strikethrough~~, inline code and fenced code blocks
  • Ordered/unordered lists, blockquotes
  • Tables
  • Hyperlinks (open in a new tab)
  • Inline text color via <span style="color: ...">color and background-color only, with validated color values (named, #hex, rgb()/hsl()). Works in text and inside table cells.

Not supported (stripped for safety)

The UI sanitizes report content because it is rendered in other users' browsers. The following are removed: <script> and event handlers, javascript:/data: links, images and video (<img>/<video>), <iframe>/embeds, other raw HTML, and any CSS other than color/background-color (so a style can't carry url(...), position, etc.). Treat report as untrusted display content — only the supported subset above is rendered.