lowlight
3.3.0 · 14 Dec 2024MIT22.1M / weekRepositoryHomepagenpmAtom feed
Upgrading lowlight From 1.10.0 to 3.3.0
31 releases in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 7
- new
- 5
- fixes
Before you upgrade
Tick each one off as you go- Breaking3.0.0
Release by release
3.3.0nothing new or fixed in the note
- New
Add declaration maps
- New
3.1.0nothing new or fixed in the note
- Breaking
Change to require Node.js 16 migrate: update too
- Breaking
2.9.0nothing new or fixed in the note
- Fixed
Fix side effects in vite by adding
index.js
- Fixed
2.7.0 – 2.8.02 releases, nothing new or fixed in the notes
- Fixed
Fix to use underscore suffixes for subscopes
- Fixed
35 other lines we could not sort, mostly version bumps
- 3.3.0
Update
Highlight.jsto~11.11 - 3.2.0
Update
Highlight.jsto~11.10 - 3.2.0
Refactor to use
@imports - 3.1.0
Update
Highlight.jsto~11.9.0 - 3.0.0
Change to use
exportsmigrate: don’t use private APIs - 3.0.0
Change API to allow different instances migrate: now,
createLowlight,all, andcommonare exported; docreateLowlight()to create a lowlight with nothing yet,createLowlight(common)for one with common languages, etc. - 3.0.0
Rename
registerLanguagetoregistermigrate: renameregisterLanguagetoregister - 3.0.0
Remove use of global highlight instance
- 2.9.0
Update
Highlight.jsto~11.8.0 - 2.8.0
Update
Highlight.jsto~11.7.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.