Merge pull request #8 from rosen-vladimirov/vladimirov/fix-yarn-support

fix: incorrect path is returned when yarn is used

Author: rosen-vladimirov

lib/index.js

@@ -153,7 +153,7 @@ const getPathFromExecutableNameOnNonWindows = (packageName, executableName) => {
 				match = lsLResult.match(regex);
 
 			if (match && match[1]) {
-				const pathToRealExecutable = path.join(path.dirname(whichResult), match[1]);
+				const pathToRealExecutable = fs.realpathSync(path.join(path.dirname(whichResult), match[1]));
 
 				// The executable is somewhere inside node_modules/<package name>/ directory,
 				// so after we have the full path to executable, we are safe to match the path to node_modules/<package name>/ from it - that's where our module is.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "global-modules-path",
-  "version": "2.3.0",
+  "version": "2.3.1",
   "description": "Returns path to globally installed package",
   "main": "./lib/index.js",
   "scripts": {

test/index.js

@@ -475,6 +475,10 @@ describe("getPath", () => {
 							return "";
 						};
 
+						fs.realpathSync = (filePath) => {
+							return filePath;
+						};
+
 						childProcess.execSync = (command) => {
 
 							if (command.indexOf("ls -l") !== -1) {
@@ -614,4 +618,4 @@ describe("getPath", () => {
 		assert.throws(() => index.getPath("test1", "test1"), "OS '1' is not supported");
 	});
 
-});
+});