fix(deps): update dependency cosmiconfig to v9 #181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.1.0
->9.0.0
Release Notes
cosmiconfig/cosmiconfig (cosmiconfig)
v9.0.0
Compare Source
searchStrategy
option:none
value means that cosmiconfig does not traverse any directories upwards.stopDir
option, which means that cosmiconfig no longer traverses directories by default, and instead just looks in the current working directory.stopDir
, add thesearchStrategy: 'global'
option.project
value means that cosmiconfig traverses upwards until it finds apackage.json
(or.yaml
) file.global
value means that cosmiconfig traverses upwards until the passedstopDir
, or your home directory if nostopDir
is given.config.js
and similar) are not looked for in the current working directory anymore. Instead, it looks in the.config
subfolder.searchPlaces
in a meta config file, the tool-definedsearchPlaces
are merged into this. Users may specifymergeSearchPlaces: false
to disable this.$import
key which will import another configuration filesearchStrategy: 'global'
v8.3.6
Compare Source
v8.3.5
Compare Source
v8.3.4
Compare Source
v8.3.3
Compare Source
v8.3.2
Compare Source
v8.3.1
Compare Source
stopDir
was given but undefinedv8.3.0
Compare Source
v8.2.0
Compare Source
.mjs
files, or.js
files whose nearest parentpackage.json
file contains"type": "module"
.${moduleName}rc.mjs
and${moduleName}.config.mjs
are included in the defaultsearchPlaces
of the asynchronous API..mjs
files.v8.1.3
Compare Source
v8.1.2
Compare Source
v8.1.1
Compare Source
v8.1.0
Compare Source
.config.{yml,yaml,json,js,cjs}
file to configure cosmiconfig itself, and look for tool configuration in it usingpackageProp
(similar to package.json)v8.0.0
Compare Source
No major breaking changes! We dropped support for Node 10 and 12 -- which you're probably not using. And we swapped out the YAML parser -- which you probably won't notice.
Breaking change: Drop support for Node 10 and 12.
Breaking change: Use npm package js-yaml to parse YAML instead of npm package yaml.
Added: Loader errors now include the path of the file that was tried to be loaded.
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone Europe/Lisbon, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.