-
-
Notifications
You must be signed in to change notification settings - Fork 75
Conversation
npm exploration - no CLI part - will put that later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like this but... I've somewhat cannibalised the ideas for CodeYourFuture/syllabus#324. I'd be happy to switch my PR to another library if we can find a suitable one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
|
||
```js | ||
"scripts": { | ||
"cowsay": "cowsay Mooooo" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be tempted to give this a different name, like "sayit"
, to emphasise that these things don't all need to be named the same - I see our trainees often assume things need to be named the same (or not understanding the differences) because we happen to do so in our examples...
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
handling all the feedback from CodeYourFuture/syllabus#189
this is an npm exploration, which is now suitable as they npm Jest from JS-1
this project has no CLI part -have put that in JS3!
View rendered challenge-cowsay-one/readme.md