Customize build folder

[lifeiscontent]

On a project I'm currently working on, we're using a file called BUILD that specifies build instructions for our microservices.

and due to Mac OS Sierra, case insensitivity is an issue, so being able to do something like

react-scripts build --path dist would be ideal in the package.json

is this possible currently?

[viankakrisna]

EDIT: this way is not supported and can be broken anytime there's an update to react-scripts

I wrote an article about that in here: https://medium.com/@viankakrisna/extending-create-react-app-webpack-config-c70828593c96#.o8n88apgl

basically, you can just create a webpack.config.js with this code inside it on your app root

process.env.NODE_ENV = 'production'
var reactScriptsConfig = require('react-scripts/config/webpack.config.prod')
module.exports = Object.assign({}, reactScriptsConfig, {
  output: Object.assign({}, reactScriptsConfig.output, {
     path: './dist'
  })
})

install webpack, and
add this code in your package.json

"build:dist": "webpack --progress",

voila! you customized the build path.

[gaearon]

Note that the above way of using Create React App is entirely unsupported and can break in any version.

[gaearon]

I imagine that we will allow this once we add some basic configuration. However this is not going to happen in the next few months. Some time during 2017, maybe.

[viankakrisna]

+1 to this. The above method is kinda hacky and I found it while debugging a production bug.

[gaearon]

Yea, it's definitely fine for one-off changes, just not something I'd recommend checking in.

[tuchk4]

btw. This feature is useful along with entry point customizing.

scripts: {
  "build": react-scripts build
  "build:lite": BUILD_DIR=build-lite ENTRY=src/lite.js react-scripts build
}

But anyway we should not expect such customizations in near future :)

#1362 (comment)

won’t be introducing more configuration on a case-by-case basis. We might add support for a configuration file at some point, but not now.

[gaearon]

Another direction we could explore here is making it easy for independent apps to share the same components and modules. This way you don't need multiple entries—you just have multiple apps.