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

Warning for command matching no packages? #110

Open
AlabasterAxe opened this issue Dec 29, 2021 · 0 comments
Open

Warning for command matching no packages? #110

AlabasterAxe opened this issue Dec 29, 2021 · 0 comments

Comments

@AlabasterAxe
Copy link

AlabasterAxe commented Dec 29, 2021

I think it might be useful to issue a warning or fail if a command specifies a package spec that matches no packages in the workspace. In my case, the directory of the package didn't match the name field in the package.json

Steps to repro:

  • attempt to run a command specifying a package that doesn't exist in the workspace e.g. wsrun -p nonexistent -c build

Expected Behavior:

  • this command doesn't map to any packages in the workspace so should error (potentially in a supressable way --allow-empty-package-list?, names are hard 🙃 )

Actual Behavior:

  • the command immediately completes, reporting success
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant