Packages

kleur

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

Upgrading kleur From 3.0.1 to 4.1.5

12 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.0.1Newest 3.x3.0.3
The note of 4.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 3.0.1yours
  2. 2 releases
  3. 4.0.0major
  4. 8 releases
  5. 4.1.5target
?
changes to make
0
advisories fixed
7
new
10
fixes

Release by release

  1. 4.1.5

    26 Jun 20221 new · 1 fix
    • New

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

    • Fixed

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

  2. 4.1.4nothing new or fixed in the note

  3. 4.1.3

    30 Sep 20201 new
    • New

      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~!

  4. 4.1.2

    26 Sep 20201 fix
    • Fixed

      Ensure NO_COLOR disables colorization if any value is received (#38, #39, #40, #41): ef5d4a8, b329629 Now properly adheres to the NO_COLOR spec. Thank you @stramel and @chocolateboy~!

  5. 4.1.1

    19 Aug 20201 fix
    • Fixed

      (types): Ensure kleur/colors type definitions can be resolved: 06923d0, cc66a6f

  6. 4.1.0

    13 Aug 20201 new
  7. 4.0.3

    31 Jul 20201 fix
    • Fixed

      Ensure process is defined before setting process-based values (#36): 303e502 This allows for kleur to be imported into browsers without any bundle-shimming.

  8. 4.0.2

    24 Jun 20201 fix
    • Fixed

      Disable colorization if inside a TTY context (#33): 5c7353f Thank you @ai~!

19 internal lines (docs, tests, tooling) left out.

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.