transpile ts to js to handle ts types

[ansh21]

Thanks in advance for your contribution. Please follow the below steps in submitting a pull request, as it will help us with reviewing it quicker.

• Before marking your PR for review, please test and verify your changes by making appropriate modifications to any of the Nightwatch example tests (present in examples/tests directory of the project) and running them. ecosia.js and duckDuckGo.js are good examples to work with.
• Create a new branch from master (e.g. features/my-new-feature or issue/123-my-bugfix);
• If you're fixing a bug also create an issue if one doesn't exist yet;
• If it's a new feature explain why do you think it's necessary. Please check with the maintainers beforehand to make sure it is something that we will accept. Usually we only accept new features if we feel that they will benefit the entire community;
• Please avoid sending PRs which contain drastic or low level changes. If you are certain that the changes are needed, please discuss them beforehand and indicate what the impact will be;
• If your change is based on existing functionality please consider refactoring first. Pull requests that duplicate code will most likely be ignored;
• Do not include changes that are not related to the issue at hand;
• Follow the same coding style with regards to spaces, semicolons, variable naming etc.;
• Always add unit tests - PRs without tests are most of the times ignored.

Fixes #3688

Dev Testing Steps:
Test case 1:

• renamed nightwatch.conf.js to nightwatch.conf.ts . Tried adding few types to the ts file.
• Executed node ./bin/nightwatch examples/tests/ecosia.js --env chrome to check if the test was successful

Test case 2:

• tested with the nightwatch.conf.js itself to ensure the current functionalities are not broken.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Status

• ❌ No modified files found in the types directory.
  Please make sure to include types for any changes you have made. Thank you!.

[AutomatedTester]

The PR title and commit don't seem related. Could you update this please

[ansh21]

The PR title and commit don't seem related. Could you update this please

Addressed

[garg3133]

We would also need to make sure that in case user has a ts config files with name nightwatch-ts.conf.js (which is a non-default name) and we pass the name of the config using the --config flag while running tests, it is able to transpile this config as well.

Right now, it won't work because in case a --config flag is provided, the flow will go to the else block (which contains the code this.argv.config = path.resolve(this.argv.config);) and there we do not have any way to transpile the ts file.

[garg3133]

Instead of this, we can also put a const Module = require('module'); statement at the top of the function definition (where other requires are done).

[garg3133]

We should use const instead of var for declaring variables. Also, we should define proper variable names, module would be a better name instead of m here.

[garg3133]

We should ideally use localJsOrTsValue here as our source of truth to decide if the ts config file is our primary config for the project. This is because the logic used to find localJsOrTsValue may change later and we may give preference to some other config file even if a nightwatch.conf.ts file is present.

This could be solved by changing this statement to:
localJsOrTsValue.includes(path.basename(CliRunner.CONFIG_FILE_TS))

And for the issue you were facing with tests, that could be solved by changing the basename definition in mockery to:

    basename(a) {
        if (a === './globals.json') {
          return 'globals';
        }

        return origPath.basename(a);
      },