Hi I am having a similar issue regarding properly finding the "resources/packages" default dir. Adding the path to that folder via --includes definitely works, but is unsavory in that there may be cases where we want to have other directories/paths as well. Is adding multiple --includes arguments permissable? Is there another method for making the default dir visible such as $PATH or something similar? (I made some attempts at adding the default dir via, $PATH, although that didn't seem to work. Is there an app-specific env variable that I can add which is respected?)
I am mainly interested because we need to create a wrapper around sbscooker based on how it's installed on site, and it would be nice to hide from most users the requirement to add --includes <default dir>, especially since the default dir path is quite long and can change at times depending on tools configurations.
thanks,
colin