fix: use correct loader for journey files

[vigneshshanmugam]

• fix [Project monitors] Push command unable to parse TypeScript #625

• When journey files are pushed, We treat these files differently when bundling

  1. Entry paths - Journey files
  2. Imported paths - Other deps / local files imported by the journey files itself.

• When the journey files are loaded by the bundler, the underlying loader in the ES build was defaulting to JS which throws error when Typescript types are used inside the journey files. This PR fixes the problem by using appropriate loader for the journey files when push command is invoked. The test is also added to ensure this does not break in the future.

Testing

1. Build the PR - npm run build
2. Create an example journey, example.journey.ts
3. Use the example below which relies on TS typings

const createJourney = (name: string) => {  // TS types
  journey(name, ({ page, params }) => {
    step('launch application', async () => {
      await page.goto(params.url);
    });
  });
};

['a', 'b'].forEach(a => createJourney(a));

4. Run SYNTHETICS_API_KEY="" npm run push

[vigneshshanmugam]

not related to this change, but ensures we never minify the journey files.

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-10-18T20:26:11.843+0000

• Duration: 14 min 24 sec

Test stats 🧪

Test	Results
Failed	0
Passed	203
Skipped	2
Total	205

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[dominiqueclarke]

LGTM. Error is no longer reported.