How configure cache-busting hash names for federated bundles and NOT the manifest.js?

[JasonKleban]

Although I already have federated modules basically working, I'm struggling with my production-ish hardening configuration. I've read all the docs on these topics I can find, but it hasn't clicked for me yet.

I want an output folder like this:

dist/
    component-one-bundle.9c7b069b154d09fd32df.js
    component-two-bundle.53180faa2a1705141a8b.js
    manifest.js

where manifest.js is the stable name well-known by consuming applications in their own remotes configuration. The manifest is not meant to be cached for very long and can be checked for updates by consumers regularly. The "bundle" files are the bulk of the code which are considered immutable and can be cached by consumers/intermediaries forever. The manifest file will always contain the current full contenthashed "bundle" file names.

Perhaps I'm misunderstanding the intended output? But I'm unable to exactly achieve the effect.

Confusions:

• My exposes-only webpack output doesn't really have any need for a traditional "entry". I'd like to avoid needing one/making one/cluttering the output folder/pointing to an ~empty file in my source code for it. If this can't easily be avoided, I can accept that but I want to confirm that it is unavoidable.
• output.filename can take a function, but moduleFederationOptions.filename can only be a string. When output.filename is used, the federated bundle files still don't get the contenthash treatment. When moduleFederationOptions.filename is set (to a string, only) it contenthashes even manifest (no surprise there, but it is against the requirement for a stable file name).
• Even with moduleFederationOptions.filename, I don't find the contenthashed names referenced in the manifest file or anywhere else. I don't know how they would be found otherwise.

Can someone who knows please comment on a few of these so I can clear up my understanding?

({
    // I don't think I have any need for a traditional entry-point
    // but without it, webpack will not generate the federated bundles
    entry: "./src/index.tsx",
    // or
    entry: {
        "why": "./src/index.tsx"
    },
    output: {
        // I expect:
        // * one manifest file that has a stable name 
        //   but will be expected to have a short http cache policy (elsewhere)
        // * contenthash-named bundles for each exposed component which could be considered
        //   immutable and forever cachable.
        filename: (pathData) => {
            return pathData.chunk.name === "manifest"
                ? '[name].js' 
                : '[name].[contenthash].js';
        }
    },
    plugins: [
        new UniversalFederationPlugin({
            name: "manifest",
            isServer: isServerBundle,
            // Does not accept a function
            filename: '[name].[contenthash].js',
            exposes: {
                // Since react-lazy only supports default exports, 
                // each of these is essentially mapped to a single 
                // (outer-most) component
                "./component-one": {
                    import: "./src/entry-points/component-one.tsx",
                    name: "component-one-bundle",
                },
                "./component-two": {
                    import: "./src/entry-points/component-two.tsx",
                    name: "component-two-bundle",
                }
            },
        })
    ]
})

[JasonKleban]

These questions remain for me when trying v2.2.2

[JasonKleban]

Partially related regarding ignoring the main entry: webpack/webpack#16445

[JasonKleban]

OK, I think I solved this for my situation. Sharing what I learned here:

dist/
    component-one-bundle.9c7b069b154d09fd32df.js
    component-two-bundle.53180faa2a1705141a8b.js
    main.7075c4a4082e21e07a82.js      << I think this should be strictly unnecessary when there is no main entry point, but it has code in it
    remoteEntry.15f79666d72a0e213e5f.js       << should really have all the code that main..js has, I figure? but no biggie
    mf-manifest.json << I http serve this with a custom cache policy of a short duration, other files can be cached ~forever
    mf-stats.json << I don't know what this is for

({
    // Still required to have a main entry point, but it can just be an empty file.
    entry: "./src/index.tsx",
    output: {
        filename: '[name].[contenthash].js',
        publicPath: `where/other/apps/can/find/me/from/browser`,   << a publicPath is required.  There's a warning about it, but if you don't know what to expect you might be tempted to ignore it - but you won't get the critical mf-manifest.json file.
    },
    plugins: [
        new UniversalFederationPlugin({
            name: "mf_app",      << Must be different from other exposes names.  MUST BE A VALID JS IDENTIFIER!  Currently emits an unhelpful error message
            isServer: isServerBundle,
            filename: 'remoteEntry.[contenthash].js',
            exposes: {
                "./component-one": {
                    import: "./src/entry-points/component-one.tsx",
                    name: "component-one-bundle",
                },
                "./component-two": {
                    import: "./src/entry-points/component-two.tsx",
                    name: "component-two-bundle",
                }
            },
        })
    ]
})

[ScriptedAlchemy]

#2488

[ScriptedAlchemy]

use a runtime plugin.
#2488