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

@starci/eslint-grammar-offset-pop

v0.17.0

Published

Offset Pop Grammar lint: the inherited Common component contract over its own visual family.

Readme

@starci/eslint-grammar-offset-pop

Offset Pop composes the Common renderers and types. This package inherits their checks from the exact matching @starci/eslint-grammar-core release; the rule implementations and shared infrastructure have one owner. Offset Pop has no additional component API rules yet. Its visual choices belong to its DNA and packaged stylesheet.

Rule ownership follows FE-RULE-OWNERSHIP in contexts/code/fe/README.md of the StarCi harness. The family's inheritance is declared in contexts/grammars/offset-pop.md; the app-shell law is contexts/ui/composition.md.

The managed fe/eslint.config.mjs consumes the universal canon and the selected family:

import { loadHfs, starciFeConfig } from "@starci/eslint-canon-fe"
import { offsetPopGrammarConfig } from "@starci/eslint-grammar-offset-pop"

const hfs = loadHfs(import.meta.url)
export default [...starciFeConfig({ hfs }), ...offsetPopGrammarConfig({ hfs })]

The inherited rule IDs use the starci-grammar prefix. rules, recommended, ruleOwners, lawOwners, ruleDeclarations, why and the default plugin expose the same authoritative objects as the matching Common contract. The package has its own canon pin and generated runtime copy and follows the Grammar version.

Migrating from @starci/eslint-canon-fe 8.x

The pinned canon-fe release moved the twenty Grammar component rules (listed in the @starci/eslint-grammar-core README and the pinned canon-fe changelog) out of the universal canon. An Offset Pop app receives them through this package under the starci-grammar/ namespace with unchanged IDs, codes and severity.

  1. Set sides.fe.grammar to offset-pop in hfs.json; no family is inferred.
  2. Install this package at its canon-pins version beside @starci/eslint-canon-fe 9 in the app root devDependencies; it brings the matching @starci/eslint-grammar-core. starci app check refuses canon-fe 9 without it (FE_STACK_FAMILY_LINT_MISSING).
  3. Compose starciFeConfig({ hfs }) first and offsetPopGrammarConfig({ hfs }) second (the block above); starci app sync renders that managed fe/eslint.config.mjs.
  4. Rename references to the moved rules from starci-fe/ to starci-grammar/.

Consuming apps migrate in their own release.

npm test runs package regression specs. Grammar and application front ends carry no specs.

The source is TypeScript in src/; npm run build emits dist/, which the package ships beside runtime/. The spec resolves @starci/eslint-grammar-core through its built dist/, so build that package first (npm run build in packages/eslint-grammar-core), then npm install here.