[Typescript] Next.js Error fetching types - not exposed by remote app

Migrating this issue over now that the typescript package is located in this repo: https://github.com/module-federation/typescript/issues/25

Essentially, @mf-typescript is being written to .next as that is the output path for Next.js apps, but .next is not being publicly served so any app which wants to download the types from /@mf-typescript/__types_index.json will get a 404.

My suggestion is to output the types to public instead but @pavandv suggests he knows why and has a fix in mind?

[Kinbaum]

@hongkiulam @pavandv I am working on a solution that will allow you to specify the location of the __types_index.json for each remote as you will have situations like described above when mixing various Next and non-Next applications.

For the time being, you can get around this issue by adding the following to your webpack configuration:

config.devServer = {
    static: {
        directory: path.resolve(__dirname, 'public')
    }
};

[hongkiulam]

After this got merged in https://github.com/module-federation/nextjs-mf/pull/302, types are now looked up at /_next/static/chunks/@mf-typescript/__types_index.json.

So the new workaround should be

config.devServer = {
    static: {
        directory: path.resolve(__dirname, '_next/static/chunks')
    }
};