fix(config): check extension before ts-node register

[xel23]

Call require('ts-node').register() after checking configFilePath has .ts extension

Fixes #3329

сс @devoto13

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[AppVeyorBot]

✅ Build karma 2927 completed (commit 4157266d7a by @xel23)

[karmarunnerbot]

✅ Build karma 530 completed (commit 4157266d7a by @xel23)

[karmarunnerbot]

✅ Build karma 529 completed (commit 4157266d7a by @xel23)

[devoto13]

@xel23 Thanks for the PR!

I guess we can land it as a workaround to solve the most painful appearance of this issue, but I don't think it "fixes" the issue. We really should implement a systematic solution as outlined in #3329 (comment).

Technically this is a breaking change. People, who might have relied on type-checking their karma.conf.js with allowJS: true will no longer have the type-checking. As this does not prevent them from running Karma, I am willing to do so to resolve the issue for the majority of users. @johnjbarton What do you think?

[maksimr]

Ping

[karmarunnerbot]

🎉 This PR is included in version 6.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[jimbojw]

Thank you so much for fixing this! 🥳 🎉