redux-toolkit.legacy-esm.js not actually compatible with Webpack 4 due to optional chaining

[Zacqary]

Upgrading to Redux Toolkit 2.x on a Webpack 4 repo fails due to this line:

if (cache?.has(value))

Webpack 4 doesn't support optional chaining without some additional plugins that can break many large projects. Is it possible to switch back to the pre-2.x transpiling method for the legacy build?

[markerikson]

Yeah, you're right, that's not getting transpiled properly - that build should have optional chaining being compiled away.

......

whoa. That's clearly not right:

  // ESM, embedded `process`: fallback for Webpack 4,
  // which doesn't support `exports` field or optional chaining
  {
    format: 'esm',
    name: 'legacy-esm',
    target: 'esnext',
    minify: false,
    env: '',
  },

That should be target: 'es2017'.

I can try to fix that this evening.

Actually rather surprised no one reported this yet.

[Zacqary]

Actually rather surprised no one reported this yet.

I guess this is useful data on how many codebases still on Webpack 4 are trying to upgrade Redux (not many).

Thanks for the quick response!

[markerikson]

Okay, that's out in https://github.com/reduxjs/redux-toolkit/releases/tag/v2.2.2 !