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
When using pnpm there is an expectation that any content after the name of the script, both position arguments and options, will be passed to the underlying script. This has proven useful, however, it has also set a precedent that causes problems with scripts that use wireit. It would be great if there was some way to tell wireit that you want it to pass anything given to it after a double-dash to the underlying script instead of consuming it.
Solution
One way to do this would be to add a new option to the configuration. Something like argumentPassthrough that would treat all arguments given to wireit as if they were passed using a double dash. This would allow us to support commands like pnpm test tests/file.spec.js --verbose without forcing a distinction between another command like pnpm lint that does not use wireit and does not require the double dash.
The text was updated successfully, but these errors were encountered:
Problem
When using
pnpm
there is an expectation that any content after the name of the script, both position arguments and options, will be passed to the underlying script. This has proven useful, however, it has also set a precedent that causes problems with scripts that usewireit
. It would be great if there was some way to tellwireit
that you want it to pass anything given to it after a double-dash to the underlying script instead of consuming it.Solution
One way to do this would be to add a new option to the configuration. Something like
argumentPassthrough
that would treat all arguments given towireit
as if they were passed using a double dash. This would allow us to support commands likepnpm test tests/file.spec.js --verbose
without forcing a distinction between another command likepnpm lint
that does not usewireit
and does not require the double dash.The text was updated successfully, but these errors were encountered: