net: export isIPv4, isIPv6 directly from cares

The function objects encapsulating `isIPv4` and `isIPv6` are not necessary. They can be directly exposed from `cares`. PR-URL: #7481 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
nodejs · Oct 26, 2016 · b630be2309823679cbb01db2331da684fa7d0f31 · b630be2
1 parent 0e52861
commit b630be2309823679cbb01db2331da684fa7d0f31
Showing with 2 additions and 6 deletions.

+2 −6 lib/net.js
diff --git a/lib/net.js b/lib/net.js
@@ -1569,14 +1569,10 @@ Server.prototype.unref = function() {
 exports.isIP = cares.isIP;


-exports.isIPv4 = function(input) {
-  return cares.isIPv4(input);
-};
+exports.isIPv4 = cares.isIPv4;


-exports.isIPv6 = function(input) {
-  return cares.isIPv6(input);
-};
+exports.isIPv6 = cares.isIPv6;


 if (process.platform === 'win32') {