Comments (2)
Hey, this is something I honestly waffled on, and decided not to support it right out the gate.
The reasons I held back:
- I figured it was easier to add this later than to take it away later
- The
:
's are there as namespaces, so for instance if I havetest:unit
andtest:cover:unit
, conceptually that is just how I want it (the latter running code coverage instrumentation), but I wouldn't want to runtest
and have it also repetitively pick up the coverage stuff; when I reviewed my huge cache of npm scripts, I saw a lot of cases like this that made me want to be less aggressive) - The more scripts you have the more ordering is likely to matter, and right now the implicit batching just relies on unspecified glob-order, so before considering this I think I'd really want #2 to be included
from scripty.
I'll PR today.
I wouldn't want to run test and have it also repetitively pick up the coverage stuff
I think test:cover
should have an index
like my example in #59.
I saw a lot of cases like this that made me want to be less aggressive)
💯 breaking change (2.x
).
right now the implicit batching just relies on unspecified glob-order
Glob order is guaranteed lexicographic so build:step-0
, build:step-1
, etc but I should write tests against it.
I'd really want #2 to be included
I envision these kinds of scripts running in parallel like lint:css
and lint:js
. Otherwise it feels like reinventing Grunt.
from scripty.
Related Issues (20)
- The scripty.path config is not work. HOT 2
- Bug while sharing scripts via node modules HOT 3
- Update dependency to remove vulnerability. HOT 2
- Scripts Path Not Read With Yarn 3
- PNPM Support HOT 3
- monorepo single config HOT 2
- In MAC, may be unenforceable directory, how can do before running scripts, automatically run chmod + x scripts/path/to/my/script HOT 7
- scripty ERR! It seems you may be running scripty from the command-line directly HOT 1
- pnpm build error, unknown options: 'commitizen_path', 'scripty_path', 'scripty_windowsPath' #
- Scripts fail with Node.js v >=18 HOT 3
- Revive builtIn scripts resolver HOT 2
- Batch scripts skip directories HOT 1
- Sharable scripts via a npm package HOT 3
- Default to silent mode; allow verbose option HOT 1
- multiple script locations HOT 6
- Allow directly running using "scripty <target>" HOT 8
- npm proposal for proxying "npm run"
- Script name and content is always printed HOT 3
- Issue while running scripty on windows10 HOT 7
- Options won't work with npm >= 7 HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scripty.