Overview
Here you are coding away, when you realize you’re in desperate need of a quick shell script to get your project cleaned up. You’re standing at a fork in the road: Bash or Node? You choose the road less travelled by (for some reason) — Node. Congratulations on this decision. You’ve written it, you may have published it, and it certainly works. But what now? Is this all a command line module Node is good for: a project clean up and some data manipulation?
Let’s take it a step further. Let’s make a command line module that’s more than just your compiling script. Irina is, of course, talking about making it more interactive.
In this talk Irina wants to take you on an adventure that will require cunning, bravery, and maybe some magic. She will walk through obtaining and parsing data, using Node’s process functions, and finally improving your module’s user experience.
Objective
The objective is for the audience to walk away being able to either 1) improve their existing command line application or 2) write some amazing interactive applications of their own, or 3) both o/ !
Five Things Audience Members Will Learn
- What is a Command Line Interface?
- What makes them interactive? Or Irina’s 5 steps to interactivity™
- Ok, let’s build an user friendly, interactive CLI
- Working with yargs, inquirer, and other kick-ass CLI tools for building such application
- Ok, you already have an application — how do you improve it?
