babel-loader
10.1.1 · 9 Mar 2026MIT28.2M / weekRepositorynpmAtom feed
Upgrading babel-loader From 8.4.0 to 10.1.1
12 releases in betweennotes for 11
Reading releases, release notes and advisories…
- 3+
- changes to make
- 0
- advisories fixed
- 4+
- new
- 4+
- fixes
Counted from 11 of 12 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking10.0.0
- Breaking10.0.0
- Breaking10.0.0
Security
- 9.1.2
GitHub Workflows security hardening
Release by release
10.1.1nothing new or fixed in the note
- New
Enable type checking and support Babel 8
- Fixed
Mark webpack as optional peer dependency
- New
- Breaking
Bump node requirement to
^18.20.0 || ^20.10.0 || >=22.0.0and webpack requirement to>= 5.61.0 - Breaking
Use output.hashFunction as loader cache hasher
- Breaking
Remove caller option check
- New
Add babel-loader logger
- New
Support cache with external dependencies
- Fixed
Ensure stability of filename cache-keys
- Breaking
- Fixed
Avoid error on missing getLogger
- Fixed
9.1.3 – 9.2.02 releases, nothing new or fixed in the notes
- Security
GitHub Workflows security hardening
- Security
9.1.1no release note
- New
Pass external dependencies from Babel to Webpack
- New
6 other lines we could not sort, mostly version bumps
- 10.1.1
Revert #1055 ("use
module.findPackageJSONAPI") - 10.1.0
Pin Node.js on CI
- 9.2.0
Update deps
- 9.0.0
Update hash method mechanism so it doesn't fail on a fips enabled machine
- 9.0.0
Require babel ^7.12.0 and Node.js >= 14.15.0 versions
- 9.0.0
Remove dependency on loader-utils and drop webpack 4 support
30 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.