mateodelnorte / find-file-recursively-up Goto Github PK

"debug" is defined as a "devDependencies", yet it is required in the main file without any condition.

I seems like this module was developed for modules meant to be installed globally (which would include the dev dependencies), but if it is ever installed as a local dependency, an error will be triggered.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency debug to v4.3.5
• chore(deps): update dependency commitizen to v4.3.0
• chore(deps): update dependency prettier to v2.8.8
• chore(deps): update dependency pretty-quick to v3.3.1
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency husky to v9
• chore(deps): update dependency jest to v29
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency pretty-quick to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

npm

package.json

• debug 4.3.2
• @commitlint/cli 12.1.4
• @commitlint/config-conventional 12.1.4
• commitizen 4.2.4
• cz-conventional-changelog 3.3.0
• husky 6.0.0
• jest 26.6.3
• prettier 2.3.1
• pretty-quick 3.1.0

travis

.travis.yml

• node 10
• node 12

---

• Check this box to trigger a request for Renovate to run again on this repository

hi Matt, guys,

First, thanks for coding this up. This library does work (I just tapped it), so let's bump the version to 1.0.0. As you know, you get penalties when it's less than 1.0.0, every release is considered breaking, even patch. Also, it will look more serious. I'm using BitHound and it does scan every dep.

What do you think?