dts for entries exposed with aliases are not emitting

[smelukov]

Describe the bug

DTS for exposed entries does not emit If we're using an alias in there entries

import * as path from "node:path";
import {ModuleFederationPlugin} from "@module-federation/enhanced";

export default {
    resolve: {
        alias: {
            foo: path.resolve(__dirname, 'src/sub/foo') // here is an alias for foo
        }
    },
    plugins: [
        new ModuleFederationPlugin({
            exposes: {
                './foo': 'foo', // ❌ not working (no dts created for src/sub/foo), even if it's an existing alias
                // './foo': './src/sub/foo', // ✅ works fine
                './bar': './src/bar'
            },
        })
    ]
}

Reproduction

https://github.com/smelukov/mf-dts-alias-bug/blob/main/webpack.config.ts#L16

Used Package Manager

npm

System Info

...

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.

[ScriptedAlchemy]

Alias is not analyzed. DTS does not use webpack resolvers to extract types. Its just tsc, not actually part of the compile AFIK

@2heal1 is it possible to support resolve alias in dts extraction?

[github-actions]

Stale issue message