@typestyles/eslint-plugin

0.3.1

Patch Changes

• #141 35e02a7 Thanks @dbanksdesign! - Breaking: semantic component class names now use block, block--dimension-option, and block__slot forms instead of hyphen semantic names. Compound variants now emit chained modifier selectors instead of *-compound-N classes. Attribute mode now kebab-cases data-* names and supports slots, returning per-slot { className, attrs, props } results.

  Upgrade notes: regenerate public-classname snapshots; update hand-written CSS / tests that targeted *-base or *-compound-N. Prefer distinct namespaces for styles.class and styles.component when they would share a base class string — dev builds warn on that collision. See docs migration guide (0.10 semantic naming).

• Updated dependencies [35e02a7]:

  • @typestyles/cli@0.2.1

0.3.0

Minor Changes

• #119 10edb85 Thanks @dbanksdesign! - Add styles.scope() for proximity-correct nested theme overrides via CSS @scope (P5.3).

  Introduce @typestyles/cli, a new package with the typestyles binary and subcommands. The first command is typestyles snapshot, which scans semantic styles.class / styles.component class names and writes .typestyles-public-classnames.json for semver guarding. Snapshot logic and heavy deps (typescript, fast-glob) live in this package so the core typestyles runtime stays lean.

  Also ships the opt-in @typestyles/no-removed-public-classname ESLint rule (consumes @typestyles/cli programmatically).

Patch Changes

• Updated dependencies [10edb85]:
  • @typestyles/cli@0.2.0

0.2.0

Minor Changes

• #96 9f3f9a0 Thanks @dbanksdesign! - Ship ESLint plugin MVP (P2.11) with rules for shorthand/longhand conflicts, invalid unitless CSS values, and duplicate TypeStyles namespace literals.

• #108 3e03d35 Thanks @dbanksdesign! - Add no-default-scope-in-package ESLint rule and package config preset for library authors. Add "Publishing Packages" docs guide covering scoped factories, naming mode selection, and ESLint enforcement.

Patch Changes

• #98 e17b8a0 Thanks @dbanksdesign! - Add npm landing-page READMEs for every published package, an examples index with contributor guidance, and doc-to-example cross-links (P2.13).