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

friclog

v0.1.0

Published

Seamless CLI for capturing daily frictions, ideas, problems, and wins — with weekly review and Obsidian support

Readme

friclog

A minimal CLI for capturing daily frictions, ideas, problems, and wins — then reviewing them weekly to continuously improve your workflow.

Built for developers who live in the terminal. Notes are plain markdown, compatible with Obsidian out of the box.

Install

npm install -g friclog
fric init

The idea

Small frictions compound. A deploy with one too many steps, a CI pipeline that's too slow, a process that creates confusion — individually forgettable, collectively significant. fric gives you a one-second way to capture them as they happen, and a weekly review to turn the patterns into action.

The methodology combines:

  • Friction Logging (Stripe) — stream-of-consciousness capture with category and severity
  • GTD capture phase — zero friction at capture time, no processing required
  • Sprint retro structure — weekly review produces concrete Start/Stop/Continue actions

Quick start

# Log a friction
fric f "CI takes 12 minutes on every PR"

# Tag with a category using #hashtag
fric f "CI takes 12 minutes #tooling"

# Both shorthand and full words work
fric friction "deploy has too many manual steps"
fric i "could cache node_modules in CI #tooling"
fric idea "write a one-command deploy script #process"
fric p "auth tokens expiring unexpectedly"
fric w "refactored auth module, tests all green"

# No args opens your $EDITOR
fric

Commands

Capture

| Command | Type | Description | |---|---|---| | fric f "text" / fric friction "text" | friction | Something that slowed you down | | fric i "text" / fric idea "text" | idea | A potential fix or improvement | | fric p "text" / fric problem "text" | problem | An unsolved blocker | | fric w "text" / fric win "text" | win | Something that went well | | fric "text" | friction | Bare capture defaults to friction | | fric | friction | Opens $EDITOR with a template |

Add #category anywhere in the text to tag it: #tooling, #process, #cognitive, #communication, #environment. Any other #tags are stored as freeform tags.

Review

fric list                   # today's entries
fric list --week            # this week
fric list -t friction       # filter by type

fric review                 # weekly review (current week)
fric review --last-week     # previous week
fric review --open          # generate + open in Obsidian

Search

fric search "CI"            # regex search across all entries
fric search "tooling"       # matches body text, type, category, and tags

Setup

fric init                   # create vault at ~/friclog
fric init --completion      # also install shell auto-complete
fric config                 # show current config
fric completion             # print completion script (bash/zsh)

Shell auto-complete

# Install (detects your shell automatically)
fric init --completion
source ~/.zshrc   # or ~/.bashrc

# Then tab-complete subcommands and flags
fric <TAB>
fric list --<TAB>

Obsidian

Your vault lives at ~/friclog/. Open it in Obsidian as a vault.

~/friclog/
  entries/    ← one .md file per entry, YAML frontmatter
  reviews/    ← weekly review reports

Each entry has structured frontmatter (date, type, category, severity, tags) queryable with the Dataview plugin:

TABLE type, category, severity, file.mtime AS "Updated"
FROM "entries"
WHERE type = "friction"
SORT date DESC

Weekly reviews are formatted with Obsidian callouts and [[wiki-links]] back to source entries:

> [!danger] CI takes 12 minutes
> `tooling` · `medium` · [[entries/2026-04-18-0915-friction|↗]]

The review also includes a Reflection section and Start · Stop · Continue table ready to fill in, plus interactive task checkboxes for action items.

Open reviews from the terminal

fric review --open          # generates review and jumps to it in Obsidian

Entry format

---
date: 2026-04-18T09:15:32.000Z
type: friction
category: tooling
severity: medium
tags: []
---

CI pipeline takes 12 minutes on every PR. The TypeScript
incremental build doesn't seem to be caching correctly.

Weekly review format

---
week: 2026-W16
generated: 2026-04-18
entries: 9
tags: [weekly-review]
---

# Weekly Review — Week 16, 2026

> [!abstract] At a Glance · Apr 14–Apr 18, 2026
> friction: **4** · idea: **3** · problem: **1** · win: **1**
> Top categories: tooling (3) · process (3) · general (2)

## Frictions

> [!danger] CI takes 12 minutes on every PR
> `tooling` · `medium` · [[entries/2026-04-18-0915-friction|↗]]

...

## Reflection

> [!question] What patterns do I notice this week?

> [!question] What is the single most important thing to fix or pursue?

### Start · Stop · Continue
- **Start:**
- **Stop:**
- **Continue:**

## Action Items
- [ ]

License

MIT