Change option flag to custom-name to avoid namespace clash

README.md

@@ -208,10 +208,10 @@ speculate --release=7
 
 ### Custom Name
 
-By default speculate will set the name from `package.json`, if you want to override this you can do so by using the `--name` flag:
+By default speculate will set the name from `package.json`, if you want to override this you can do so by using the `--custom-name` flag:
 
 ```sh
-speculate --name=my-cool-api
+speculate --custom-name=my-cool-api
 ```
 
 This is useful if you are using private NPM packages which start with an `@`.

bin/speculate.js

@@ -17,16 +17,17 @@ if (!isValid) {
 }
 
 var projectPkg = require(path.resolve(cwd, './package.json'));
-var name = projectPkg.name;
 
 program
   .version(commandPkg.version)
   .option('-r --release <release>', 'Specify release number of package')
-  .option('-n --name <name>', 'Specify custom name for package')
+  .option('-c --custom-name <custom-name>', 'Specify custom name for package')
   .parse(process.argv);
 
+var name = program.customName || projectPkg.name;
+
 clean(cwd, projectPkg);
-generate(cwd, projectPkg, program.release, program.name, function (err) {
+generate(cwd, projectPkg, program.release, program.customName, function (err) {
   if (err) {
     console.error('Error:', err.message);
     process.exit(1);

lib/generate.js

@@ -29,7 +29,6 @@ function addCustomFieldsToPackage(pkg, customName) {
 }
 
 module.exports = function (root, pkg, release, customName, cb) {
-
   var customPackage = addCustomFieldsToPackage(pkg, customName);
   var specsDirectory = files.specsDirectory(root);
   var sourcesDirectory = files.sourcesDirectory(root);