Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NCU does not complain about a configFileName that does not exist #1377

Open
3 tasks done
matijs opened this issue Mar 13, 2024 · 1 comment
Open
3 tasks done

NCU does not complain about a configFileName that does not exist #1377

matijs opened this issue Mar 13, 2024 · 1 comment

Comments

@matijs
Copy link

matijs commented Mar 13, 2024

  • I have searched for similar issues
  • I am using the latest version of npm-check-updates
  • I am using node >= 14.14

Steps to Reproduce

.ncurc.cjs:

module.exports = {
  install: 'always',
  upgrade: true,
};

Dependencies:

n/a

Steps:

Current Behavior

# missing the `c` in the config file name...
$ npx ncu --configFileName .ncurc.js
# 🪄 
Run ncu --configFileName .ncurc.js -u to upgrade package.json
$ 

Expected Behavior

It would be cool if ncu could tell me that .ncurc.js did not exist instead of using defaults.

@raineorshine
Copy link
Owner

Good point. Thanks!

Added a check in 2914dbe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants