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'm integrating this into a monorepo using NPM workspaces. In general everything works great. However I noticed that if this does encounter an error it doesn't print the name of the package or let me know what file has errors:
For example:
npm exec -w ./packages package-check
Would run @skypack/package-check on all packages under ./packages. One of those has an error but I cant tell which one failed.
By contrast the name of the package is printed at athe bottom for successful runs:
Seems as simple as adding a name param to runCheck. Alternately this could print the path to the checked package.json at the top or add this under a --verbose flag. Happy to PR the change.
The text was updated successfully, but these errors were encountered:
I'm integrating this into a monorepo using NPM workspaces. In general everything works great. However I noticed that if this does encounter an error it doesn't print the name of the package or let me know what file has errors:
For example:
Would run
@skypack/package-check
on all packages under./packages
. One of those has an error but I cant tell which one failed.By contrast the name of the package is printed at athe bottom for successful runs:
Seems as simple as adding a
name
param torunCheck
. Alternately this could print the path to the checkedpackage.json
at the top or add this under a--verbose
flag. Happy to PR the change.The text was updated successfully, but these errors were encountered: