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
{{ message }}
This repository was archived by the owner on Mar 21, 2025. It is now read-only.
Idea being: by inspecting the file system of scripts/, you should be able to populate the "scripts" section of the package.json so folks don't have to manually keep package.json in sync manually.
On the other hand we could seek a more dynamic approach that'd allow scripty to intercept npm run without ever changing the package.json
For now i think the right thing to do is be explicit like we are being until we get some usage as feedback
The text was updated successfully, but these errors were encountered:
Populating the "scripts" section of the package.json def has some niceties. Mainly:
no need to know about scripty to be able to tell what a script does
you can easily check what all the scripts do via npm run.
I had thought about making a tool that populated the "scripts" section, but never got to a point where I really needed it – I guess I've only used the "scripts" field with simple configs.
I'll try using scripty and report back in case I ever feel the need for this populater feature. :)
Idea being: by inspecting the file system of
scripts/
, you should be able to populate the "scripts" section of the package.json so folks don't have to manually keep package.json in sync manually.On the other hand we could seek a more dynamic approach that'd allow scripty to intercept
npm run
without ever changing the package.jsonFor now i think the right thing to do is be explicit like we are being until we get some usage as feedback
The text was updated successfully, but these errors were encountered: