update plop to use latest node-plop

README.md

@@ -11,7 +11,7 @@ Micro-generator framework that makes it easy for an entire team to create files
  
 [![npm](https://img.shields.io/npm/v/plop.svg)](https://www.npmjs.com/package/plop)
  
-[![plop on slack](https://plopjs-slack-rjjmojauhb.now.sh/badge.svg)](https://plopjs-slack-rjjmojauhb.now.sh/)
+[![plop on slack](https://plopjs-slack-vbeawnrrtk.now.sh/badge.svg)](https://plopjs-slack-vbeawnrrtk.now.sh/)
 
 ## What is Plop?
 Plop is what I like to call a "micro-generator framework." Now, I call it that because it is a small tool that gives you a simple way to generate code or any other type of flat text files in a consistent way. You see, we all create structures and patterns in our code (routes, controllers, components, helpers, etc). These patterns change and improve over time so when you need to create a NEW *insert-name-of-pattern-here*, it's not always easy to locate the files in your codebase that represent the current "best practice." That's where plop saves you. With plop, you have your "best practice" method of creating any given pattern in CODE. Code that can easily be run from the terminal by typing `plop`. Not only does this save you from hunting around in your codebase for the right files to copy, but it also turns "the right way" into "the easiest way" to make new files.

package.json

@@ -32,7 +32,7 @@
     "interpret": "^1.0.0",
     "liftoff": "^2.2.0",
     "minimist": "^1.2.0",
-    "node-plop": "=0.9.0",
+    "node-plop": "=0.13.0",
     "v8flags": "^2.0.10"
   },
   "engines": {