Using ES version of library (node_module) is not working

Describe the bug

Webpack throws an error when I change my code to use “es” version of libraries

Environment

Steps to reproduce

1. Add @material-ui/core to your project
2. Use any “es” variant of the code from that library. This particular code uses optional chaining in es version of the code

import TextField from "@material-ui/core/es/TextField";

1. Webpack dev yarn start or Webpack build yarn build both fails with the following error

The fix

• So after digging throught the issue, I have found out that this is happening due to Optional Chaining and Nullish Coalescing not supported in the JS parser acorn v6.x.x which is what Webpack 4 uses. Issue details here
• And on my computer, I edited the webpack config in node_modules and added the two presets to the last module rules which processes JS outside of src.
• This has fixed the issue

---

If this usecase is generic enough, Can I raise a pull request to make these changes??

If not, I can use something like react-app-rewired to edit it for our usecase. Also this change will be temporary until we move to Webpack 5.

[ben-razor]

This is fixed in Create React App v5 for the modules I was having issues with.

[Aftabnack]

@Malvineous actually Babel is run for node module code as well with preset-env which uses browser list to transpile, I’d say the support is good for library code too. But acorn issue is preventing us from using Optional chaining & Nullish coalescing from library code.