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

@fe-essential/linear-cli

v0.1.5

Published

A Bun-based CLI for Linear.

Downloads

409

Readme

@fe-essential/linear-cli

A Bun-based CLI for Linear.

Install CLI

Install globally with Bun:

bun add -g @fe-essential/linear-cli
linear --help

If linear is not found, make sure Bun's global bin directory is in your PATH:

export PATH="$HOME/.bun/bin:$PATH"

You can also install with npm, but Bun must still be available in your PATH because the CLI is a Bun executable:

npm install -g @fe-essential/linear-cli
linear --help

Install dependencies

bun install

Run locally

bun run index.ts --help

Link as a global command

bun link
linear --help

Configure

Create a project-local config in the current directory:

linear init

Create a user-global config:

linear init --global

init prompts for:

  • api_key
  • workspace
  • project

Local config is written to:

./linear.config.yaml

Global config is written to:

~/.config/linear/linear.config.yaml

Config resolution order:

  1. LINEAR_API_KEY for api_key only
  2. ./linear.config.yaml
  3. ~/.config/linear/linear.config.yaml

Commands

Every subcommand supports -h and --help.

Issue commands:

linear issue --help

List all issues in the configured project:

linear issue list

List issues by status:

linear issue list -s Todo
linear issue list --status completed

Add an issue to the configured project. The default status is Backlog:

linear issue add "Fix login bug"
linear issue add "Fix login bug" -d "Reproduce and patch auth flow"
linear issue add "Fix login bug" --image ./screenshot.png
linear issue add "Fix login bug" -d "See screenshots" --image ./before.png --image ./after.png

Image uploads support gif, jpeg, jpg, png, and webp. Uploaded images are embedded in the issue description.

Read one issue by Linear issue id or identifier:

linear issue read LIN-123

Update issue title, description, images, or status:

linear issue update LIN-123 -t "Better title"
linear issue update LIN-123 -d "Replace the issue description"
linear issue update LIN-123 --append-description "Additional notes" --image ./screenshot.png
linear issue update LIN-123 -s Done

Delete an issue by Linear issue id:

linear issue delete <issue-id>

Delete issues created on a UTC date in the configured project:

linear issue delete --date 2026-06-11 --yes

Count all non-deleted workspace issues across all statuses:

linear workspace count-issue

Show the authenticated user:

linear viewer

Development

bun run typecheck

Release

The GitHub Actions release workflow publishes to npm and creates a GitHub Release when a version tag is pushed.

First configure the repository secret NPM_TOKEN with npm publish permissions.

Then run one of the release scripts from a clean working tree:

bun run release:patch  # 0.1.0 -> 0.1.1
bun run release:minor  # 0.1.0 -> 0.2.0
bun run release:major  # 0.1.0 -> 1.0.0

The script automatically:

  1. bumps package.json version;
  2. runs typecheck;
  3. commits chore: release v${version};
  4. creates the matching git tag;
  5. pushes the branch and tag to trigger publishing.

The tag must match the package version exactly (v${version}).