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
You removed builtIn scripts in 17520b5. It'd be useful in my project to expose base scripts that dependent packages can override (I'll summarize better when it's not so late). It would only require changing 1) builtIn scripts to be resolved relative to node_modules and 2) add an option named something like preset.
The text was updated successfully, but these errors were encountered:
I'm open to this so long as it can be accomplished in a way that absolutely does not cause anyone's existing scripty use to accidentally invoke a shared script or for some bad actor to cleverly trigger a script by a scripty user. Arbitrary script execution of stuff in your node_modules (e.g. postinstall security fiascos) is appropriately scary enough as it is.
I'll PR today. It's as safe as configuring path. The idea is to run default scripts from a specified "preset" package but still create your own locally. Kind of the way create-react-app works.
You removed
builtIn
scripts in 17520b5. It'd be useful in my project to expose base scripts that dependent packages can override (I'll summarize better when it's not so late). It would only require changing 1)builtIn
scripts to be resolved relative tonode_modules
and 2) add an option named something likepreset
.The text was updated successfully, but these errors were encountered: