Software zum Installieren eines Smart-Mirror Frameworks , zum Nutzen von hochschulrelevanten Informationen, auf einem Raspberry-Pi.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

CHANGELOG.md 8.1KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201
  1. # Changelog
  2. ## 7.0.0
  3. - **Breaking change:** Add `${moduleName}rc.cjs` and `${moduleName}.config.cjs` to the default `searchPlaces`, to support users of `"type": "module"` in recent versions of Node.
  4. - **Breaking change:** Drop support for Node 8. Now requires Node 10+.
  5. ## 6.0.0
  6. - **Breaking change:** The package now has named exports. See examples below.
  7. - **Breaking change:** Separate async and sync APIs, accessible from different named exports. If you used `explorer.searchSync()` or `explorer.loadSync()`, you'll now create a sync explorer with `cosmiconfigSync()`, then use `explorerSync.search()` and `explorerSync.load()`.
  8. ```js
  9. // OLD: cosmiconfig v5
  10. import cosmiconfig from 'cosmiconfig';
  11. const explorer = cosmiconfig('example');
  12. const searchAsyncResult = await explorer.search();
  13. const loadAsyncResult = await explorer.load('./file/to/load');
  14. const searchSyncResult = explorer.searchSync();
  15. const loadSyncResult = explorer.loadSync('./file/to/load');
  16. // NEW: cosmiconfig v6
  17. import { cosmiconfig, cosmiconfigSync } from 'cosmiconfig';
  18. const explorer = cosmiconfig('example');
  19. const searchAsyncResult = await explorer.search();
  20. const loadAsyncResult = await explorer.load('./file/to/load');
  21. const explorerSync = cosmiconfigSync('example');
  22. const searchSyncResult = explorerSync.search();
  23. const loadSyncResult = explorerSync.load('./file/to/load');
  24. ```
  25. - **Breaking change:** Remove support for Node 4 and 6. Requires Node 8+.
  26. - **Breaking change:** Use npm package [yaml](https://www.npmjs.com/package/yaml) to parse YAML instead of npm package [js-yaml](https://www.npmjs.com/package/js-yaml).
  27. - **Breaking change:** Remove `cosmiconfig.loaders` and add named export `defaultLoaders` that exports the default loaders used for each extension.
  28. ```js
  29. import { defaultLoaders } from 'cosmiconfig';
  30. console.log(Object.entries(defaultLoaders))
  31. // [
  32. // [ '.js', [Function: loadJs] ],
  33. // [ '.json', [Function: loadJson] ],
  34. // [ '.yaml', [Function: loadYaml] ],
  35. // [ '.yml', [Function: loadYaml] ],
  36. // [ 'noExt', [Function: loadYaml] ]
  37. // ]
  38. ```
  39. - Migrate from Flowtype to Typescript.
  40. - Lazy load all default loaders.
  41. ## 5.2.1
  42. - Chore: Upgrade `js-yaml` to avoid npm audit warning.
  43. ## 5.2.0
  44. - Added: `packageProp` values can be arrays of strings, to allow for property names that include periods. (This was possible before, but not documented or deliberately supported.)
  45. - Chore: Replaced the `lodash.get` dependency with a locally defined function.
  46. - Chore: Upgrade `js-yaml` to avoid npm audit warning.
  47. ## 5.1.0
  48. - Added: `packageProp` values can include periods to describe paths to nested objects within `package.json`.
  49. ## 5.0.7
  50. - Fixed: JS loader bypasses Node's `require` cache, fixing a bug where updates to `.js` config files would not load even when Cosmiconfig was told not to cache.
  51. ## 5.0.6
  52. - Fixed: Better error message if the end user tries an extension Cosmiconfig is not configured to understand.
  53. ## 5.0.5
  54. - Fixed: `load` and `loadSync` work with paths relative to `process.cwd()`.
  55. ## 5.0.4
  56. - Fixed: `rc` files with `.js` extensions included in default `searchPlaces`.
  57. ## 5.0.3
  58. - Docs: Minor corrections to documentation. *Released to update package documentation on npm*.
  59. ## 5.0.2
  60. - Fixed: Allow `searchSync` and `loadSync` to load JS configuration files whose export is a Promise.
  61. ## 5.0.1
  62. The API has been completely revamped to increase clarity and enable a very wide range of new usage. **Please read the readme for all the details.**
  63. While the defaults remain just as useful as before — and you can still pass no options at all — now you can also do all kinds of wild and crazy things.
  64. - The `loaders` option allows you specify custom functions to derive config objects from files. Your loader functions could parse ES2015 modules or TypeScript, JSON5, even INI or XML. Whatever suits you.
  65. - The `searchPlaces` option allows you to specify exactly where cosmiconfig looks within each directory it searches.
  66. - The combination of `loaders` and `searchPlaces` means that you should be able to load pretty much any kind of configuration file you want, from wherever you want it to look.
  67. Additionally, the overloaded `load()` function has been split up into several clear and focused functions:
  68. - `search()` now searches up the directory tree, and `load()` loads a configuration file that you don't need to search for.
  69. - The `sync` option has been replaced with separate synchronous functions: `searchSync()` and `loadSync()`.
  70. - `clearFileCache()` and `clearDirectoryCache()` have been renamed to `clearLoadCache()` and `clearSearchPath()` respectively.
  71. More details:
  72. - The default JS loader uses `require`, instead of `require-from-string`. So you *could* use `require` hooks to control the loading of JS files (e.g. pass them through esm or Babel). In most cases it is probably preferable to use a custom loader.
  73. - The options `rc`, `js`, and `rcExtensions` have all been removed. You can accomplish the same and more with `searchPlaces`.
  74. - The default `searchPlaces` include `rc` files with extensions, e.g. `.thingrc.json`, `.thingrc.yaml`, `.thingrc.yml`. This is the equivalent of switching the default value of the old `rcExtensions` option to `true`.
  75. - The option `rcStrictJson` has been removed. To get the same effect, you can specify `noExt: cosmiconfig.loadJson` in your `loaders` object.
  76. - `packageProp` no longer accepts `false`. If you don't want to look in `package.json`, write a `searchPlaces` array that does not include it.
  77. - By default, empty files are ignored by `search()`. The new option `ignoreEmptySearchPlaces` allows you to load them, instead, in case you want to do something with empty files.
  78. - The option `configPath` has been removed. Just pass your filepaths directory to `load()`.
  79. - Removed the `format` option. Formats are now all handled via the file extensions specified in `loaders`.
  80. (If you're wondering with happened to 5.0.0 ... it was a silly publishing mistake.)
  81. ## 4.0.0
  82. - Licensing improvement: updated `parse-json` from `3.0.0` to `4.0.0`(see [sindresorhus/parse-json#12][parse-json-pr-12]).
  83. - Changed: error message format for `JSON` parse errors(see [#101][pr-101]). If you were relying on the format of JSON-parsing error messages, this will be a breaking change for you.
  84. - Changed: set default for `searchPath` as `process.cwd()` in `explorer.load`.
  85. ## 3.1.0
  86. - Added: infer format based on filePath
  87. ## 3.0.1
  88. - Fixed: memory leak due to bug in `require-from-string`.
  89. - Added: for JSON files, append position to end of error message.
  90. ## 3.0.0
  91. - Removed: support for loading config path using the `--config` flag. cosmiconfig will not parse command line arguments. Your application can parse command line arguments and pass them to cosmiconfig.
  92. - Removed: `argv` config option.
  93. - Removed: support for Node versions < 4.
  94. - Added: `sync` option.
  95. - Fixed: Throw a clear error on getting empty config file.
  96. - Fixed: when a `options.configPath` is `package.json`, return the package prop, not the entire JSON file.
  97. ## 2.2.2
  98. - Fixed: `options.configPath` and `--config` flag are respected.
  99. ## 2.2.0, 2.2.1
  100. - 2.2.0 included a number of improvements but somehow broke stylelint. The changes were reverted in 2.2.1, to be restored later.
  101. ## 2.1.3
  102. - Licensing improvement: switched from `json-parse-helpfulerror` to `parse-json`.
  103. ## 2.1.2
  104. - Fixed: bug where an `ENOENT` error would be thrown is `searchPath` referenced a non-existent file.
  105. - Fixed: JSON parsing errors in Node v7.
  106. ## 2.1.1
  107. - Fixed: swapped `graceful-fs` for regular `fs`, fixing a garbage collection problem.
  108. ## 2.1.0
  109. - Added: Node 0.12 support.
  110. ## 2.0.2
  111. - Fixed: Node version specified in `package.json`.
  112. ## 2.0.1
  113. - Fixed: no more infinite loop in Windows.
  114. ## 2.0.0
  115. - Changed: module now creates cosmiconfig instances with `load` methods (see README).
  116. - Added: caching (enabled by the change above).
  117. - Removed: support for Node versions <4.
  118. ## 1.1.0
  119. - Add `rcExtensions` option.
  120. ## 1.0.2
  121. - Fix handling of `require()`'s within JS module configs.
  122. ## 1.0.1
  123. - Switch Promise implementation to pinkie-promise.
  124. ## 1.0.0
  125. - Initial release.
  126. [parse-json-pr-12]: https://github.com/sindresorhus/parse-json/pull/12
  127. [pr-101]: https://github.com/davidtheclark/cosmiconfig/pull/101