Packages

@capsizecss/core

4.1.3 · 12 Nov 2025MIT205.9k / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 4.x4.1.3No known advisoryLatest line
  • 3.x3.1.1No known advisoryTo 4.1.3

Latest releases

  1. 4.x · latest line
  2. 4.1.3

    12 Nov 2025
    • Bundle Capsize packages with tsdown instead of Crackle. This is an internal change only and does not affect the public API.

  3. 4.1.2

    8 May 2024
    • createFontStack: Prefer postscriptName or fullName for fallback source

      The @font-face declaration aliases generated by createFontStack now favour postscriptName and fullName over familyName from the provided metrics when selecting a local font face as a fallback.

      MDN recommends using either fullName and postscriptName when accessing local fonts to ensure the best matching across platforms, while also enabling selection of a single font face within a larger family, e.g. Arial Bold or Arial-BoldMT within Arial.
      For details see MDN.

      ⚠️ Note: Falling back to familyName (original behaviour) makes this work backwards compatible with older versions of font metrics.

  4. 4.1.1

    5 May 2024
    • createFontStack: Apply line-gap-override with no lineGap in preferred font

      Ensure that the line-gap-override property is applied correctly when overriding a fallback font with a web font that has no lineGap.
      Previously if the override was zero it would be omitted from the declaration, rather than the correct behaviour of overriding the fallback metric to zero.

    • createFontStack: Ensure provided `size-adjust` is factored into metric overrides

      Ensures a custom size-adjust value provided via the fontFaceProperties option is factored into the calculations for the metric overrides.

Dependency tracking

Know when your own dependencies move

This page watches @capsizecss/core. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 19 Nov 2026. Releases and advisories last read 19 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.