Make allow customize /dist naming from consumer's package.

[Kyr]

Motivation.
For the some reasons I would to have ability to customize naming in /dist. postbuild script approach not very comfortable and needs an appropriate modification of manifestos.

This approach use optional naming schema configuration in consumer's package.json, for example "flat" structure:

...
  "distNaming": {
    "output": {
      "development": {
        "filename": "bundle.js",
        "chunkFilename": "[name].chunk.js"
      },
      "production": {
        "filename": "[name].[contenthash:8].js",
        "chunkFilename": "[name].[contenthash:8].chunk.js"
      }
    },
    "media": {
      "filename": "[name].[hash:8].[ext]"
    },
    "files": {
      "filename": "[name].[hash:8].[ext]"
    },
    "css": {
      "filename": "[name].[contenthash:8].css",
      "chunkFilename": "[name].[contenthash:8].chunk.css"
    }
  }
...

Such config applied to default naming schema and then used in webpack's config factory.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[bugzpodder]

I am not seeing this as being useful for anyone else so we'll likely not go for this. What is your use case for requiring custom naming?

[Kyr]

I am not seeing this as being useful for anyone else so we'll likely not go for this. What is your use case for requiring custom naming?

In my opinion there are various use cases that required custom naming.
For example:

• modify target folder for everything that not an image, e.g. use assets/... instead static/media/...;
• modify filenaming or hash parameters (or even avoid hashing), e.g. instead static/css/[name].[contenthash:8].chunk.css define as styles/fragment.[name].css
• in my case, that, it's correct, not very useful for anyone else, I must to be avoided any nesting structure (please don't ask why, not sure that I can explain it clearly, it's legacy);

I'm would not to do eject due to lost gain and gain pain - it's not that I really want.

--scripts-version approach works well for me for the moment, but I would suggest that similar problem could resolved with RCA it self.

Perhaps exists other approach for the same thing, would you like to apoint me?

[stale]

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[mrmckeb]

We have discussed a config file for CRA in the past, but for now we have decided that it's not a priority @Kyr. As @bugzpodder stated, I'm also concerned that this has little value for most users.

Like you, I need this for a project I work on, and we also use a custom fork of react-scripts to achieve this. I think that's the safest approach for now.

Thanks for your time, and in future, I'd suggest raising an issue before a PR so we can discuss it in more detail there :)