SWC minify's mangling of classnames causes GCP library to fail an internal type check that relies on constructor.name

[Driptap]

Summary

Using GCP's BigQuery library to create a table from a file in GCS requires passing a (GCP Bigquery defined class) File object to the BigQuery client.

  const file = storage.bucket('bucket-name').file('file-name');
  const [job] = await dataset.table(tableId).load(file, metadata);

The BigQuery client checks the constructor.name amongst other things to ensure the correct object is passed.

isCustomType(unknown: any, module: string) {
    function getConstructorName(obj: Function) {
      return obj.constructor && obj.constructor.name.toLowerCase();
    }
// Truncated from previous link

The typecheck fails from what I have come to the conclusion is the mangling of the class name, resulting in a runtime error with the minified code.

⨯ Error: Source must be a File object.

I don't want to comment on this method of type checking an object, it seems it may be a recurring issue with other libraries that rely on this or similar methods; ie. as describe in this issue and this discussion.

It seems there is a possibility to configure SWC not to mangle class or function names.

I have made use of the serverMinification flag to overcome this issue but thought it'd be good to share this while SWC is being adopted into next.js.

I don't have a lot of time to create a repro repository required for submitting a bug, so would be keen to know if there is another solution to allow the disabling of class name mangling that I've overlooked before putting time into that.

/// Next.js config 
export default {
  swcMinify: true,
  experimental: {
    serverMinification: false,
  },
};