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

@nicerice/concision

v0.0.6

Published

Linting for your code architecture.

Readme

concision

We design code architectures so that even as our code grows, the mechanism we interact with remains simple. This tool lets you define these mechanisms via templates and they'll be adhered to 100% of the time. Linting for your code architecture.

Disclaimer: Due to the experimental nature of this repo, a select few pieces are vibecoded for prototyping purposes. However, all of those will be re-made by hand once the language interface is settled on. I'm not a fan of not knowing what the machine I'm building actually does ^^

Example

Say you have useFunctions with this general shape

import { state } from "@mx/svelte"
import { latLngToVec3 } from "../domain/latLngToVec3"
import { defaultAltitude, defaultLatitude, defaultLongitude } from "../constants"

export function useTransforms() {
  let position = $state(latLngToVec3(defaultLatitude, defaultLongitude, defaultAltitude))

  return state({
    get value() {
      return position
    },
    set value(v) {
      position = v
    },
    setPositionFromWorldLocation: (latitude, longitude, altitude) => (position = latLngToVec3(latitude, longitude, altitude)),
  })
}

We would create an abstract version without implementation details at .spec/templates/component-module.ts, leaving only the general shape of our code.

---
paths: **/use*.svelte.ts
---
**[import*]

export function use_1_(*) {
  let _1_ = $state(*)

  **[3]

  return state({
    get value() {
      return _1_
    },
    set value(v) {
      _1_ = v
    },
    **
  })
}
  • Covers all use*.svelte.ts files
  • Allows optional import lines, as many as wanted (**)
  • Enforces a use_1_ signature (e.g. usePosition), with _1_ capturing the hook name for later use
  • Ensures $state() is created with the same captured name
  • Optionally allows three more variables to be used before forcing a refactor (**[3])
  • And ensures it's exported via a special accessor function

Nothing passes until it matches your specifications. No matter which LLM I used, it kept breaking this form in a hundred different ways. No more though :]

Syntax

| Operator | Description | | --- | --- | | ~ | Optional empty line | | ~[...] | Optional block | | * | Wildcard - matches any text until the next concrete symbol | | ** | Unbounded repeat - any number of matching lines (any content) | | **[content] | Unbounded repeat - any number of lines matching the given format | | **[N] | Bounded repeat - up to N variables | | _N_ | Capture group - reuse the same text with case-variant matching (kebab, snake, camel, Pascal) | | \* | Literal asterisk | | ! | Exclude - line must NOT match (definitive end) | | ![text] | Exclude - line must NOT contain text (definitive end) | | !! | Require - line MUST match (definitive end) | | !![text] | Require - line MUST contain text (definitive end) | | *![text] / *!![text] | Wildcard-scoped exclude/require | | \|[A <> B] | Alternation - match one of the listed options |

Repeat operators (**, **[N], **[content]) default to being optional if no matches are present. When **[...] or ~[...] appear on their own line, surrounding empty lines become implicitly optional (capped at one).

Install

Run it with:

bun x @nicerice/concision

or install it globally:

bun i -g @nicerice/concision && concision check