@MurzNN myCommand is usually the same as the file name of the command, is it not happening in your case? Or do you want the complete path of the file from the this.fileName?

Yeah, I want to see the complete path, because in some projects we have the same named commands in dependencies, and sometimes - symlinks to the same Nigtwatch directory from different places, which leads to this error, with no idea about what exact directories lead to this problem.

@garg3133 @MurzNN

To address this issue we can modify the validateMethod function in Nightwatch's command loader to track and display the file paths where duplicate commands are defined. We can add a command registry and maintain a global registry to keep track of commands and their file paths during loading. This registry can map each command to the file path where it was first defined and then check if a command already exists in the registry. If a duplicate is found, we can throw an error that includes the file paths of both the first definition and the duplicate.
We can Include the file paths in the error message to clearly show where the duplication occurred.

I think this is the solution to this .... Is the implementation to this correct?

Hey @garg3133 ,
I have implemented the displaying of file names and also written a unit test.
Can you can take a look into the PR