Federation Runtime API types not working as expected for loadRemote

[pganster]

Describe the bug

According to the module federation guide, loadRemote should return the inferred types for the supplied remote, but it doesn't. The returned promise always resolve an unknown.

Reproduction

https://github.com/pganster/module-federation-runtime-api-type-prompts

Used Package Manager

yarn

System Info

System:
    OS: Linux 6.10 Arch Linux
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz
    Memory: 34.43 GB / 62.53 GB
    Container: Yes
    Shell: 5.2.32 - /bin/bash
  Binaries:
    Node: 18.16.1 - ~/.nvm/versions/node/v18.16.1/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v18.16.1/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.1/bin/npm
    pnpm: 8.9.2 - ~/.nvm/versions/node/v18.16.1/bin/pnpm

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.

[pganster]

Any opinions @ScriptedAlchemy or is this a known issue?

[ScriptedAlchemy]

I'll raise to my team. Will pull it Monday and see if it notice any specific errors.

[ScriptedAlchemy]

@2heal1 can you take a look?

[2heal1]

Sorry for replying latter , if you want to use API types , you need to add ./@mf-types/* to you tsconfig.json include option ,like this

{
  "compilerOptions": {
    "target": "ES2020",
    "lib": ["DOM", "ES2020"],
    "module": "ESNext",
    "noEmit": true,
    "strict": true,
    "skipLibCheck": true,
    "isolatedModules": true,
    "resolveJsonModule": true,
    "moduleResolution": "node",
    "useDefineForClassFields": true,
    "allowImportingTsExtensions": true,
    "paths":{
      "*": ["./@mf-types/*"]
    }
  },
+ "include": ["src","./@mf-types/*"]
}

[2heal1]

I will add it to our docs