kick-init - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

git.js

@@ -14,3 +14,3 @@ 'use strict';
 //pull token out of json object
-const token = JSON.parse(fs.readFileSync(configPath));
+const token = (fs.readFileSync(configPath)) ? JSON.parse(fs.readFileSync(configPath)) : null;
 
@@ -17,0 +17,0 @@ module.exports = (info) => {

index.js

@@ -13,5 +13,5 @@ 'use strict';
   let info = argsParser(args);
-  // if (info) {
-	// 	git(info);
-	// }
+  if (info) {
+		git(info);
+	}
 };

package.json

 {
   "name": "kick-init",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "cli tool for getting your new project a kick start!",
@@ -5,0 +5,0 @@ "main": "index.js",

readme.md

@@ -76,3 +76,3 @@
 
-In order to get the full benefits of kick-init add a .kickconfig.json file to your root directory. There are two sections of the config. The **repos** property will list out all repos available to clone. The second property is **github**. Here you will list your username and personal access token. Check out how to get a personal access token [here](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/)
+In order to get the full benefits of kick-init add a .kickconfig.json file to your root directory. There are two sections of the config. The **repos** property will list out all repos available to clone. The second property is **github**. Here you will list your username and personal access token. Check out how to get a personal access token [here](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/). Without the config file you will not be able to create a remote repo but can still start a local project. Get ta kickin!
 
@@ -79,0 +79,0 @@ ## License

No alert changes

Improved metrics

Total package byte prevSize

9804

increased by1.57%

No dependency changes