You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 thepackage.json
Steps to repro:
wsrun -p nonexistent -c build
Expected Behavior:
--allow-empty-package-list
?, names are hard 🙃 )Actual Behavior:
The text was updated successfully, but these errors were encountered: