Packages

cosmiconfig

10.0.1 · 30 Aug 2026MIT172.2M / weekRepositoryHomepagenpmAtom feed

Upgrading cosmiconfig From 7.0.0 to 10.0.1

20 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 7.0.0Newest 7.x7.1.0
  1. 7.0.0yours
  2. 2 releases
  3. 8.0.0major
  4. 12 releases
  5. 9.0.0major
  6. 2 releases
  7. 10.0.0major
  8. 10.0.1target
8
changes to make
0
advisories fixed
9
new
12
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
  • breaking8.0.0
  • breaking8.0.0

Release by release

  1. 10.0.1nothing new or fixed in the note

  2. 10.0.0

    Migration needed2 Aug 20261 new
    • breaking

      The required version range is now ^22.18 || >=24.

    • breaking

      Remove typescript in favor of Node's own type stripping. This means that TypeScript 7 projects are supported, but non-erasable type syntax like namespace or enum is unsupported.

    • breaking

      JSON parsing uses the JSON.parse function directly. parse-json is no longer used for better error messages, since Node has improved theirs.

    • new

      Added support for UTF-16 config files

  3. 9.0.2

    7 Jun 20262 fixes
    • fixed

      Fixed a prototype chain issue that may happen when merging different config objects.

    • fixed

      Fixed the project search strategy not correctly stopping at the package boundary.

  4. 9.0.1

    2 Mar 20262 fixes
    • 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.

  5. 9.0.0

    Migration needed26 Nov 20235 new · 2 fixes
    • breaking

      Breaking change: This is the default value if you don't pass a stopDir option, 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.js and similar) are not looked for in the current working directory anymore. Instead, it looks in the .config subfolder.

    • breaking

      When defining searchPlaces in a meta config file, the tool-defined searchPlaces are merged into this. Users may specify mergeSearchPlaces: false to disable this.

    • new

      The none value means that cosmiconfig does not traverse any directories upwards.

  6. 8.3.6

    13 Sep 20231 fix
    • fixed

      Ignore search place if accessing it causes ENOTDIR (i.e. if access of a subpath of a file is attempted)

  7. 8.3.5

    8 Sep 20231 fix
    • fixed

      Pass null to transform function for backwards compat

  8. 8.3.4

    4 Sep 20231 fix
    • fixed

      Remove node: prefix from imports (f76484a), closes #323

8 other lines we could not sort, mostly version bumps

  • Remove import-fresh dependency in favor of directly clearing the cache.

    10.0.0

  • Fixed: existence of meta config breaking default loaders

    8.1.3

  • Fixed: generation of TypeScript types going to the wrong output path

    8.1.2

  • Fixed: meta config overriding original options completely (now merges correctly)

    8.1.1

  • Added: always look at .config.{yml,yaml,json,js,cjs} file to configure cosmiconfig itself, and look for tool configuration in it using packageProp (similar to package.json)

    8.1.0

  • Added: Loader errors now include the path of the file that was tried to be loaded.

    8.0.0

  • Added: Additional default searchPlaces within a .config subdirectory (without leading dot in the file name)

    7.1.0

  • Fixed: If there was a directory that had the same name as a search place (e.g. "package.json"), we would try to read it as a file, which would cause an exception.

    7.0.1