Packages

kleur

4.1.5 · 26 Jun 2022MIT176.8M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 4.x4.1.5No known advisoryLatest line
  • 3.x3.0.3No known advisoryTo 4.1.5
  • 2.x2.0.2No known advisoryTo 4.1.5
  • 1.x1.0.2No known advisoryTo 4.1.5
  • 0.x0.0.0No known advisoryTo 4.1.5

Latest releases

All 21 releases
  1. 4.x · latest line
  2. 4.1.5

    26 Jun 2022
    • Add "types" export conditions for Node16 TypeScript module resolution (#57): 06f28e0
      Thank you @calebeby~!

    • Handle undefined process.env with fallback (#54): ec20016
      For browser/vite support. Thank you @farnabaz~!

  3. 4.1.4

    22 Jan 2021

    Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.

  4. 4.1.3

    30 Sep 2020
    • Add existence process.stdout check for browser-like polyfills (#42): 01963cc
      Bundlers like parcel, webpack, and browserify polyfill process but don't include a stdout implementation.
      Thank you @tinchoz49~!

Dependency tracking

Know when your own dependencies move

This page watches kleur. 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 21 Nov 2026. Releases and advisories last read 21 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.