feat: Switch to cosmiconfig-typescript-loader

[marek-saji]

Description

Switch from unmaintained @endemolshinegroup/cosmiconfig-typescript-loader to cosmiconfig-typescript-loader.

Why?

I’ve run into a problem in one of my projects where running jest gave errors.

Error: Jest: Failed to parse the TypeScript config file …/jest.config.ts
  Error: Debug Failure. False expression: Non-string value passed to
  `ts.resolveTypeReferenceDirective`, likely by a wrapping package
  working
  with an outdated `resolveTypeReferenceDirectives` signature. This is
  probably not a problem in TS itself.
      at readConfigFileAndSetRootDir
      (…/node_modules/jest-config/build/readConfigFileAndSetRootDir.js:136:13)
          at readConfig
          (…/node_modules/jest-config/build/index.js:233:18)
              at readConfigs
              (…/node_modules/jest-config/build/index.js:420:26)
                  at runCLI
                  (…/node_modules/@jest/core/build/cli/index.js:132:59)
                      at Object.run
                      (…/node_modules/jest-cli/build/cli/index.js:155:37)

Caused by ts-node@9 (jestjs/jest#12655) and upgrading to 10 was hold off by lingui depending on
@endemolshinegroup/cosmiconfig-typescript-loader.

And generally speaking — better to make a switch from a package that was
last updated two years ago and seems abandoned.

Checklist

• Includes tests
• Includes documentation

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
js-lingui	✅ Ready (Inspect)	Visit Preview	May 30, 2022 at 2:11PM (UTC)

[semoal]

it's strange that this snapshot it's added right? Looks like the config is not loaded correctly

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.