Cannot use files with multiple dots in their names in remote exposes

[artieeez]

Describe the bug

When using files that contain two dots in their filenames (e.g., bar.component.tsx) in the exposes configuration, the remote module is ignored. This results in the exposed module not being included in the generated declarations and failing to work in the consumer when imported.

exposes: { './foo': './src/components/foo.tsx', './bar': './src/components/bar.component.tsx' }

In this scenario:

• ./bar will not be included in the generated declarations.
• It will not work in the consumer if imported.

There are no errors thrown in the producer during the build process. However, you can confirm the issue by:

• Checking the missing declaration in the dist folder.
• Trying to import the remote in a consumer, which will result in an error.

Reproduction

https://github.com/artieeez/rsbuild-module-federation-issue

Used Package Manager

npm

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
    Memory: 10.34 GB / 19.83 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.7.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[artieeez]

The issue began after the release of version v0.2.7.

[artieeez]

Found the issue. I'll open a PR