Does it work inside next.config.js?

[Ademsk1]

I'm using next-runtime-env@1.x, as we are limited in using a Pages Router. I need to use module federation - and the urls to fetch out to inside the config need to be different for different environments.

// next.config.js
// either from default
const NextFederationPlugin = require('@module-federation/nextjs-mf');
const {env} = require('next-runtime-env')

const { configureRuntimeEnv } = require('next-runtime-env/build/configure');
configureRuntimeEnv();
module.exports = {
  webpack(config, options) {
    const { isServer } = options;
    config.plugins.push(
      new NextFederationPlugin({
        name: 'next2',
        remotes: {
          next1: `next1@http://${env('NEXT_PUBLIC_REMOTE')}/_next/static/${
            isServer ? 'ssr' : 'chunks'
          }/remoteEntry.js`,
        },
        filename: 'static/chunks/remoteEntry.js',
        exposes: {
          './title': './components/exposedTitle.js',
          './checkout': './pages/checkout',
        },
        shared: {
          // whatever else
        },
      }),
    );

    return config;
  },
**};**

However, when trying to use this - I can see that the window.__ENV is populated, as is the __ENV.js file, but this never works. Any ideas why?

Thanks

[adlermore]

You can dynamically inject the environment variable by modifying the remotes configuration inside NextFederationPlugin:

remotes: { next1: next1@http://${env('NEXT_PUBLIC_REMOTE')}/_next/static/${
isServer ? 'ssr' : 'chunks'
}/remoteEntry.js, },