RoXoM

This PR not fix #242. https://github.com/bowen0/customize-cra/blob/2e924d2dfff5fb4d91e53988a322fa881e5df3ce/src/customizers/webpack.js#L131-L132 https://github.com/bowen0/customize-cra/blob/2e924d2dfff5fb4d91e53988a322fa881e5df3ce/src/customizers/webpack.js#L193-L196 https://github.com/bowen0/customize-cra/blob/2e924d2dfff5fb4d91e53988a322fa881e5df3ce/src/customizers/webpack.js#L145-L148 this code still cause the problem.

@Anish-Agnihotri Yeah!!!!! This PR #185 is what I am going to do. I found it has been merge into `next` branch. I'm very excited that someone has already done this.

> I ran into this issue when using the `classnames` module, and I solved it by storing the value in a variable and using it in `styleName` property. > >...

I am using `@dr.pogodin/babel-plugin-react-css-modules` with CRA v4. It work well for me.

This is How React team gets component name. https://github.com/facebook/react/blob/master/packages/shared/getComponentNameFromType.js But, I'm not sure what the best solution for using this module. Copy files?? or other way??

It seem like work well in `postcss-less` v5

I don't know if it works well ```js [ "import", { "libraryName": "@ant-design/icons", "customName": (name, file) => { // do something in this // return `libs/${name}` } } ] ```

```shell WARNING in ./node_modules/@react-keycloak/core/lib/context.js Module Warning (from ./node_modules/thread-loader/dist/cjs.js): Failed to parse source map from '{yourProjectPath}/node_modules/@react-keycloak/core/lib/@react-keycloak/core/context.ts' file: Error: ENOENT: no such file or directory, open '{yourProjectPath}/node_modules/@react-keycloak/core/lib/@react-keycloak/core/context.ts' @ ./node_modules/@react-keycloak/core/lib/index.js 2:0-26 2:0-26 @...

I use `[ignoreWarning](https://webpack.js.org/configuration/other-options/#ignorewarnings)` to ignore the warning. **This is a workaround before we resolve the problem.** ```js // in webpack config module.export = { // ... ignoreWarnings: [ { module:...

> If we're not using CRACO is there a solution? > > I've not been able to install CRACO in the project due to the new React Scripts. You can...