Packages

lowlight

3.3.0 · 14 Dec 2024MIT22.1M / weekRepositoryHomepagenpmAtom feed

Upgrading lowlight From 1.6.0 to 3.3.0

37 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 1.6.0Newest 1.x1.20.0
  1. 1.6.0yours
  2. 18 releases
  3. 2.0.0major
  4. 14 releases
  5. 3.0.0major
  6. 2 releases
  7. 3.3.0target

Before you upgrade

Tick each one off as you go
  • Breaking3.0.0

Release by release

  1. 3.3.0nothing new or fixed in the note

  2. 3.2.0

    26 Nov 20241 new
    • New

      Add declaration maps

  3. 3.1.0nothing new or fixed in the note

  4. 3.0.0

    Migration needed4 Sep 2023
    • Breaking

      Change to require Node.js 16 migrate: update too

  5. 2.9.0nothing new or fixed in the note

  6. 2.8.1

    1 Feb 20231 fix
    • Fixed

      Fix side effects in vite by adding index.js

  7. 2.7.0 – 2.8.02 releases, nothing new or fixed in the notes

  8. 2.6.1

    28 Mar 20221 fix
    • Fixed

      Fix to use underscore suffixes for subscopes

43 other lines we could not sort, mostly version bumps
  • Update Highlight.js to ~11.11

    3.3.0
  • Update Highlight.js to ~11.10

    3.2.0
  • Refactor to use @imports

    3.2.0
  • Update Highlight.js to ~11.9.0

    3.1.0
  • Change to use exports migrate: don’t use private APIs

    3.0.0
  • Change API to allow different instances migrate: now, createLowlight, all, and common are exported; do createLowlight() to create a lowlight with nothing yet, createLowlight(common) for one with common languages, etc.

    3.0.0
  • Rename registerLanguage to register migrate: rename registerLanguage to register

    3.0.0
  • Remove use of global highlight instance

    3.0.0
  • Update Highlight.js to ~11.8.0

    2.9.0
  • Update Highlight.js to ~11.7.0

    2.8.0

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.