v0.19.3

• Upgrade vile-ncu plugin to v0.4.0.

v0.19.2

• Use the -e option to exit with non-zero code if issues are found
• Speed up vile init even more by removing initial friendly message & confirm
• Added table of contents to docs page
• Flushed out README even more (and added new demo)

v0.19.1

• Updated the README to be more descriptive, include usage, etc

v0.19.0 "Super Ape"

• Make Vile more usable out of the box by shipping core plugins stat,comment,coverage and ncu (can disable with -w)
• Vile's coverage plugin now auto detects lcov data in coverage if it exists, which was an annoying manual hurdle when getting started
• Make Vile more usable out of the box by auto ignoring a boat load of more directories and paths by default, and have vile init only add extra directories that a user can choose
• Streamlined vile init to ask less questions and presume more (and not install plugins for you)
• Also rewrote the docs to be more helpful and streamlined, especially with getting started and caveats for certain languages/frameworks
• Attempt to make logging more clean when spinner is still running (ex: plugin logs to stderr)

v0.18.3

Notable Changes

• Auto ignore node_modules and .git so the UX is much more pleasant and output is manageable when you have no initial config

v0.18.2

Notable Changes

• Ship a fixed type change that should of been included in initial 0.18.0 release.

v0.18.1

Notable Changes

• Update chalk to newest major version (2.x.x)

v0.18.0

Notable Changes

• Merged vile.LANG into vile.STAT

v0.17.1

Notable Changes

• vile punish is now vile analyze
• CLI options are now properly dashed (ex: --no-decorations)
• vile.exec now only takes plugins through its options arg (vs via the first arg)
• -l sets the process output (not issue severity) logging level, i.e stdout (info) and stderr (warn,error)
• -i is a new option to specify issue type values to log (ex: -i security,coverage)
• Expose logger module via require("vile") so lib users can disable logging
• Optionally show highlighted code snippets in the terminal using -t
• Use a more lightweight functionally composed logging implementation (switched to loglevel + chalk vs minilog)
• Ensure color setting works in vile.spawn sub procs
• Nicer logging UX for running plugins and progress (using ora now vs cli-spinner)
• Log to stderr wherever possible
• Start using proper error control (ex: plugin/* modules don't touch process.exit)

v0.16.3

• Fix a complex spawn issue with a hack to ensure win/nix compatibility with PATH modifications (weird behaviour seen on Win 10 CMD - see #45)