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
One issue that I have seen by all of the 'better npm scripts' setups is new folks not grokking what exactly the abstraction is doing or what it is running.
A.k.a the "p-s... what in the..." reaction from people unaware of this package
Has a proposal to potentially help folks looking at the package.json
before:
{
"scripts": {
"start": "p-s"
}
}
after:
{
"scripts": {
"start": "p-s && echo 'Look in package-scripts.js for script information'"
}
}
Just my 2 cents!
The text was updated successfully, but these errors were encountered:
Kent love this idea!
One issue that I have seen by all of the 'better npm scripts' setups is new folks not grokking what exactly the abstraction is doing or what it is running.
A.k.a the "p-s... what in the..." reaction from people unaware of this package
Has a proposal to potentially help folks looking at the package.json
before:
after:
Just my 2 cents!
The text was updated successfully, but these errors were encountered: