-
Notifications
You must be signed in to change notification settings - Fork 28
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
🐛 Bug: Error: could not determine executable to run #100
Comments
Logs:
|
Ran into the same thing just now. I see a PR for this is up. Could you take a look into merging it @JoshuaKGoldberg, pretty please? |
To other folks finding this issue: awaiting the PR getting merged, you can run @rgant’s fork with fix directly using the following command:
|
@all-contributors please add @rgant for bug.
|
I've put up a pull request to add @rgant! 🎉 |
🎉 This is included in version v0.7.1 🎉 The release is available on: Cheers! 📦🚀 |
Adds @rgant as a contributor for bug. This was requested by JoshuaKGoldberg [in this comment](#100 (comment)) --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
Bug Report Checklist
main
branch of the repository.Expected
When running
npx package-json-validator --warnings --recommendations
I expect to install temporarily this package and then run the validator.Actual
I get the following error:
Additional Info
I believe that this is caused by the removal of the
bin
key in the package.json by #89.Can we restore this key and see if that works?
The text was updated successfully, but these errors were encountered: