Module Not Found in Next.js - AMD module issue and relative paths.

Next.js tries to load the import as AMD, due to relative path resolution in Webpack to get this library to work you need to add the following to next.config.mjs.

const nextConfig = {
  webpack: (config, { isServer }) => {
    config.module.rules.push({
      test: /\.js$/, // Apply this rule to .js files
      include: /node_modules\/cybersource-rest-client/,
      parser: {
        amd: false, // Disable AMD parsing
      },
    });

    return config;
  },
};

Start with the reported next.config.mjs webpack workaround and inspect how the package is imported by Next.js, focusing on the relative-path and AMD parsing behavior described in the issue. Reproduce the Module Not Found failure and establish whether the library can work without consumer-side configuration; the issue does not name a repository file or test.