lib: clarify the usage of 'else'

The keyword 'else' is unnecessary after 'throw' statements.

PR-URL: #11148
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Sakthipriyan Vairamani <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Franziska Hinkelmann <[email protected]>

Author: JacksonTian

lib/child_process.js

@@ -30,9 +30,9 @@ exports.fork = function(modulePath /*, args, options*/) {
   if (pos < arguments.length && arguments[pos] != null) {
     if (typeof arguments[pos] !== 'object') {
       throw new TypeError('Incorrect value of args option');
-    } else {
-      options = util._extend({}, arguments[pos++]);
     }
+
+    options = util._extend({}, arguments[pos++]);
   }
 
   // Prepare arguments for fork:
@@ -502,8 +502,8 @@ function execFileSync(/*command, args, options*/) {
 
   if (err)
     throw err;
-  else
-    return ret.stdout;
+
+  return ret.stdout;
 }
 exports.execFileSync = execFileSync;
 
@@ -522,7 +522,7 @@ function execSync(command /*, options*/) {
 
   if (err)
     throw err;
-  else
-    return ret.stdout;
+
+  return ret.stdout;
 }
 exports.execSync = execSync;