swc-loader: allow node_modules .ts and .tsx files

[darrenjaneczek]

What this PR does / why we need it:

It can be convenient to use github imports between private repositories in order to share typescript files.
The previous rule excluded all node_modules files from the swc-loader. This adjustment to the excludes pattern allows for ts and tsx files.

Without this change (or an override to this rule's exclude field), webpack would emit this failing error:

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.

Here is a workaround that I have been using on webpack.config which overrides that of the .config folder:

...
function isSwcLoaderRule(rule: any): rule is RuleSetRule {
  return rule?.use?.loader === 'swc-loader';
}
...


  // BEGIN FIX swc-loader to work with our internal git dependencies
  // Prevents error: "You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file."
  const swcLoaderRule = baseConfig.module?.rules?.filter(isSwcLoaderRule)[0];
  if (!swcLoaderRule) {
    throw new Error('Could not find the swc-loader rule. Has the .config/webpack.config.ts changed?');
  }
  // Exclude node_modules, except for typescript files (.ts, .tsx) possibly shared by git dependencies
  swcLoaderRule.exclude = /(node_modules)(?:(?!.*tsx?$))/;
  // END FIX

Having this exclude pattern within the boilerplate .config would be preferable to pasting this workaround in multiple projects webpack overrides.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged but will not trigger a new release. To trigger a new release add the release label before merging.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.

[jackw]

This feels very specific to a single use case to me. Gonna discuss it further in our slack channel first.