cosmiconfig
10.0.1 · 30 Aug 2026MIT172.2M / weekRepositoryHomepagenpmAtom feed
Upgrading cosmiconfig From 8.3.6 to 10.0.1
5 releases in betweenevery note read
Reading releases, release notes and advisories…
- 6
- changes to make
- 0
- advisories fixed
- 6
- new
- 6
- fixes
Before you upgrade
Tick each one off as you go- breaking10.0.0
- breaking10.0.0
- breaking10.0.0
- breaking9.0.0
- breaking9.0.0
- breaking9.0.0
Release by release
10.0.1nothing new or fixed in the note
- breaking
The required version range is now
^22.18 || >=24. - breaking
Remove
typescriptin favor of Node's own type stripping. This means that TypeScript 7 projects are supported, but non-erasable type syntax likenamespaceorenumis unsupported. - breaking
JSON parsing uses the
JSON.parsefunction directly.parse-jsonis no longer used for better error messages, since Node has improved theirs. - new
Added support for UTF-16 config files
- breaking
- fixed
Fixed a prototype chain issue that may happen when merging different config objects.
- fixed
Fixed the
projectsearch strategy not correctly stopping at the package boundary.
- fixed
- fixed
Fixed a race condition where multiple instances existing simultaneously could cause cosmiconfig to fail to load TypeScript config files.
- fixed
Fixed an issue on Windows where CWD being a short path (e.g.
C:\Users\USERNA~1) would cause cosmiconfig to fail to load ESM config files.
- fixed
- breaking
Breaking change: This is the default value if you don't pass a
stopDiroption, which means that cosmiconfig no longer traverses directories by default, and instead just looks in the current working directory. - breaking
Meta config files (i.e.
config.jsand similar) are not looked for in the current working directory anymore. Instead, it looks in the.configsubfolder. - breaking
When defining
searchPlacesin a meta config file, the tool-definedsearchPlacesare merged into this. Users may specifymergeSearchPlaces: falseto disable this. - new
The
nonevalue means that cosmiconfig does not traverse any directories upwards.
- breaking
1 other line we could not sort, mostly version bumps
- 10.0.0
Remove
import-freshdependency in favor of directly clearing the cache.