---
title: "kleur 4.1.5: release notes, upgrades and advisories"
description: "kleur 4.1.5: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/kleur
lang: en
---

[Packages](https://inlinr.com/packages)

# kleur

4.1.5 · 26 Jun 2022 MIT 176.8M / week [Repository](https://github.com/lukeed/kleur) [Homepage](https://github.com/lukeed/kleur#readme) [npm](https://www.npmjs.com/package/kleur) [Atom feed](https://inlinr.com/packages/feed/kleur)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/kleur/upgrade)

LineNewestSecurity

- 4.x 4.1.5 No known advisory Latest line
- 3.x 3.0.3 No known advisory [To 4.1.5](https://inlinr.com/packages/kleur/upgrade/3.0.3-4.1.5)
- 2.x 2.0.2 No known advisory [To 4.1.5](https://inlinr.com/packages/kleur/upgrade/2.0.2-4.1.5)
- 1.x 1.0.2 No known advisory [To 4.1.5](https://inlinr.com/packages/kleur/upgrade/1.0.2-4.1.5)
- 0.x 0.0.0 No known advisory [To 4.1.5](https://inlinr.com/packages/kleur/upgrade/0.0.0-4.1.5)

## Latest releases

[All 21 releases](https://inlinr.com/packages/kleur/releases)

1. 4.x · latest line
2. ### [4.1.5](https://inlinr.com/packages/kleur/releases/4.1.5 "Open this release") [](https://github.com/lukeed/kleur/releases/tag/v4.1.5 "Read this release where it was published")  
26 Jun 2022

  - Add "types" export conditions for `Node16` TypeScript module resolution ([#57](https://github.com/lukeed/kleur/issues/57)): [06f28e0](https://github.com/lukeed/kleur/commit/06f28e0)  
  _Thank you [@calebeby](https://github.com/calebeby)\~!_
  - Handle undefined `process.env` with fallback ([#54](https://github.com/lukeed/kleur/issues/54)): [ec20016](https://github.com/lukeed/kleur/commit/ec20016)  
  _For browser/vite support. Thank you [@farnabaz](https://github.com/farnabaz)\~!_
3. ### [4.1.4](https://inlinr.com/packages/kleur/releases/4.1.4 "Open this release") [](https://github.com/lukeed/kleur/releases/tag/v4.1.4 "Read this release where it was published")  
22 Jan 2021  
Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.
4. ### [4.1.3](https://inlinr.com/packages/kleur/releases/4.1.3 "Open this release") [](https://github.com/lukeed/kleur/releases/tag/v4.1.3 "Read this release where it was published")  
30 Sep 2020

  - Add existence `process.stdout` check for browser-like polyfills ([#42](https://github.com/lukeed/kleur/issues/42)): [01963cc](https://github.com/lukeed/kleur/commit/01963cc)  
  _Bundlers like `parcel`, `webpack`, and `browserify` polyfill `process` but don't include a `stdout` implementation._  
  _Thank you [@tinchoz49](https://github.com/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](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/kleur/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

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](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
