Error with boxyhq/saml-jackson plugin when using Webpack NextModuleFederation Plugin

[KiranManohar1990]

Hello Team,

Need your suggestions here on the below issue, kindly help to resolve these issues.

I’m encountering an error when using the boxyhq/saml-jackson plugin in conjunction with the Webpack NextModuleFederation Plugin in my project. The error message is as follows:

error connecting to engine: sql, type: postgres db: TypeError: Native is not a constructor

Steps to Reproduce:
Set up a project with the following dependencies:
boxyhq/saml-jackson
webpack
@module-federation/nextjs-mf

Expected Behavior:
The project should compile and run without any errors or warnings.

Actual Behavior:
The webpack build process runs and when starting the application and clicking on button to sso into the application we are receiving the below error

error connecting to engine: sql, type: postgres db: TypeError: Native is not a constructor.

Without webpack and next modulefederation plugin the apps works fine with boxyhq integration.

Environment:

Node.js version: 20.15.0
NPM/Yarn version:10.7.0
Operating System: Local machine(Windows), Linux on server hosts.
boxyhq/saml-jackson version: 1.27.1

Sample next.config.mjs for the webpack and module federation configuration.

import nextTranslate from 'next-translate';
import { NextFederationPlugin } from '@module-federation/nextjs-mf';
const config = nextTranslate({
reactStrictMode: true,
swcMinify: true,
output: 'standalone',
eslint: {
ignoreDuringBuilds: true,
},
basePath: /${process.env.NEXT_PUBLIC_BASE_PATH},
webpack: (
/** @type {{ plugins: NextFederationPlugin[]; module: { rules: any[] }; }} */ config,
) => {
// Configure Module Federation Plugin
config.plugins.push(
new NextFederationPlugin({
name: 'hostapp',
filename: 'static/chunks/remoteEntry.js',
remotes: {},
extraOptions: {},
}),
);

    // Add JSON loader
    config.module.rules.push({
        test: /\.json$/,
        type: 'javascript/auto',
        use: {
            loader: 'json-loader',
        },
    });

    return config;
},

});

export default config;

[deepakprabhakara]

My best guess is that some modules are being removed (as webpack thinks it's unused). Could you try adding the following lines to the server code in your app and see if it helps:-

import { native } from 'pg';
native; // reference it

If that works we can look to add that into our code.

[niwsa]

@KiranManohar1990 Sorry for the delayed response. I haven't been able to reproduce the issue yet. I tried using the config that you shared but I guess there are some env/settings specific to your setup. Will try with a minimal module fed setup.

[KiranManohar1990]

@niwsa Thank you, kindly let me know if any further details are required from our end, right now we are blocked by this and trying to find an alternate solution if this doesn't work, but i am sure that i am missing few specific properties which might definitely resolve this issue and hope its work as we don't want to change existing solutions.

[niwsa]

@KiranManohar1990 I would probably require your help in setting up the next.config with module federation. Can we connect over a call. You can reach me at [email protected]

[niwsa]

@KiranManohar1990 Alternatively, you can do away with the preloading of the SSO connection, you can later add it by calling the library methods