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 not sure if this would be reasonable as a feature, since it does add some implied logic to what will run, but given the following package.json as an example:
Would this type of behavior be useful, even if behind a flag passed to run-script-os that could be added to the main 'ascript' command? This would make the package.json far less verbose, but still allow for "handling" all the os specific things as necessary, since in many cases the actual command invocation doesn't change between platforms. I know that you can make this work with the current implementation by adding:
But as i've stated, it'd be nice to remove the additional verbosity if it could identify the platform or combo that will run and appropriately run the pre/post scripts associated.
The text was updated successfully, but these errors were encountered:
I'm not sure if this would be reasonable as a feature, since it does add some implied logic to what will run, but given the following package.json as an example:
If you do the following, here's the actual results:
I'd sort of expected the following:
Based on the readme, i had hoped that doing this might be a workaround, but it similarly does not trigger pre/post:
Would this type of behavior be useful, even if behind a flag passed to
run-script-os
that could be added to the main 'ascript' command? This would make the package.json far less verbose, but still allow for "handling" all the os specific things as necessary, since in many cases the actual command invocation doesn't change between platforms. I know that you can make this work with the current implementation by adding:But as i've stated, it'd be nice to remove the additional verbosity if it could identify the platform or combo that will run and appropriately run the pre/post scripts associated.
The text was updated successfully, but these errors were encountered: