CLI Framework #12
CLI Framework #12
Conversation
| @@ -0,0 +1,35 @@ | |||
| #! /usr/bin/env ./node_modules/.bin/babel-node | |||
There was a problem hiding this comment.
This is a nice trick to run CLI-scripts with babel-node
| @@ -0,0 +1,32 @@ | |||
| # Created by .ignore support plugin (hsz.mobi) | |||
There was a problem hiding this comment.
If you've made general improvements to this file that would be useful to prod-module-boilerplate, could you make sure they're reflected there, too? I haven't looked myself...
There was a problem hiding this comment.
This one is quite common. Created if you make a new Github project and choose Node as default .gitignore.
There was a problem hiding this comment.
|
I don't see any unit tests. Did I miss something? |
|
Over-all, great work. 👏 |
|
I wasn't sure about tests, since they require additional libs pulled into a project. As well as eslint. Was thinking of doing it in a separate PR to keep focus on CLI frameworks itself in this one. |
|
Consider testing a requirement for all substantial code commits. Since we don't have the supporting stuff added here yet, feel free to add them with this initial PR. =) |
|
And thanks for being a rockstar on this project lately. 🎸 🔥 |
|
Thanks, it's a pleasure. Always fun to do some meaningful and interesting
work.
|
| "max-statements": [0, 10], | ||
| "new-parens": [2], | ||
| "new-cap": [0], | ||
| "newline-after-var": [2], |
There was a problem hiding this comment.
also in prod-module-boilerplate? =)
There was a problem hiding this comment.
Yeah, need that update there too. It actually gets bit annoying to propagate changes. I've got the same issues with my own modules. Not sure what is the best solution. Maybe some "defaults" repo with stuff and couple of scripts like npm install && cp -f ./node_modules/defaults/.eslintrc ./?
What do you reckon?
|
Blue-tape does not have CLI support (the one Until it is fixed, I have to add some automation to our tests. |
|
It does now. =) |
|
Seen it. Will remove |
I reckon it is a part of #7
This is how it works:
So now we have 3 "binaries":
cloverfieldcf- convenient alias forcloverfieldcf-package- stub for apackagescaffold (will be implemented according to Use prod module boilerplate #10)cfhas only one command available for now:buildwith a single option<scaffold>. See code comments for details.cf build packageis equivalent tocf-packageand starts step-by-step "wizard".Regarding libs choice. I checked different commands, args and prompt libs and the most friendly seems to be
nomnomfor commands and options andpromptfor, hm.., prompt. I used other libs before (like commander.js) and found them quite syntax-heavy and not fun.If we are ok with tooling, I can actually implement
scaffold/package#10 now. Should be pretty straightforward.PS: CLI colors and messages can be customized