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 would be nice if we maintained the script that is being executed by Alfred through package.json.
I don't want to specify a new property. That's why my suggestion is that we look at the main or bin property of package.json. If that property is set AND alfy is a dependency, I think we can assume the script should be
run-node {main} $1
If you are doing something differently and don't want that, you can safely remove the main (or bin) property from package.json.
Not sure which property I prefer, main or bin.
The text was updated successfully, but these errors were encountered:
Actually, one problem with using bin is that npm will add it as a global binary when the user install the workflow, so while bin is more correct semantically, main might be a better choice. Or we could just add a custom field.
I think it would be nice if we maintained the script that is being executed by Alfred through
package.json
.I don't want to specify a new property. That's why my suggestion is that we look at the
main
orbin
property ofpackage.json
. If that property is set ANDalfy
is a dependency, I think we can assume the script should beIf you are doing something differently and don't want that, you can safely remove the
main
(orbin
) property frompackage.json
.Not sure which property I prefer,
main
orbin
.The text was updated successfully, but these errors were encountered: