Build creating multiple classes with the same name

[thecaligarmo]

Build creating multiple classes with the same name

[icyJoseph]

Hi,

Could you try this out?

module.exports = {
    experimental: {
        serverMinification: false,
        ....
    },
    ....
}

And see if that helps out? Also, you have two next.config files, you probably want to drop one of them.

[thecaligarmo]

I removed the next.config.mjs file (locally) and edited the next.config.js file to be:

module.exports = {
  // ... rest of the configuration.
  output: "standalone",
  experimental: {
      serverMinification: false,
  },
  reactStrictMode: true,
};

It's still minifying from the looks of it as it's still changing the class names to o and such (and thus makes it so the problem is still there). Is this dependent on a particular version of Next? (Mine's showing up as version 14.1.3)

Additional note: I tried the same thing but with using next.config.mjs instead and the same issue. I also checked on 2 different browsers in case it was a cacheing issue and that didn't resolve the issue.

[icyJoseph]

Turn off swcMinify too, that one is at the root of the config, not experimental

[thecaligarmo]

Here's the updated config:

module.exports = {
  // ... rest of the configuration.
  output: "standalone",
  experimental: {
      serverMinification: false,
  },
  reactStrictMode: true,
  swcMinify: false,
};

Unfortunately still getting the same error =/ Again tried on a couple browsers and ran build twice just in case.

Just in case it is a cache thing: Do I need to delete old builds or by running npm run build and then npm run start that should automatically handle old build cleanups and such and only use the most recent build correct?

[thecaligarmo]

I don't know what you mean by default/name exports. You mean in the config file?

[icyJoseph]

I wonder if you could try to set up a reproduction repository? like try to remove as much as possible from the business logic, and just keep the code that breaks

[thecaligarmo]

I tried to remove as much as I could. I'm still getting an error that more than 1 item is being called the same thing. The good thing is that now there's a lot less collisions, but there's still collisions.

To help separate things, I created a new branch:
https://github.com/thecaligarmo/ngu-idle-calculators/tree/test-next

[thecaligarmo]

As an update. using the serverMinification and the swcMinify did nothing, but adding the following:

  webpack: (
    config,
    { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack }
  ) => {
    config.optimization.minimize = false
    return config
  },

made it so minimization was no longer happening and everything is working again. I'm not sure if that means this is no longer a bug or not, but from the looks of other issues, this seems to creep up every so often, so not sure what the best fix is.