-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom absolute path for npm build #778
Comments
There is no such option but you can work around it. Change |
I guess this helps thanks :) but it would be great if we can pass configs to the script. Can we have it as feature request? |
We generally don’t offer configuration options. Please see this document for more information. This is intentional because it lets other tools integrate with Create React App more tightly because they can make assumptions about where sources and build output are. Since it is always possible to add this on top as an additional script, we don’t see the value in this being configurable, and it’s not worth the downsides in our opinion. |
(Oops, didn’t mean to reopen. Fat finger.) |
@gaearon The biggest value for this type of configuration option is convenience - it's much easier to set a flag than it is to copy the files and delete the build directory, especially when that script is different between Mac and Windows. You could always go the configuration file route similar to For cross-platform dev:
Edit:
|
how would you write
for Windows. I tried with xcopy, but when I npm run build
I get this error in the command line:
|
If I run
npm build
the build files are getting generated in the home directory of the project. Is there any way I can specify custom directory to generate build outside the home directory of the project?Use case : I want to maintain build files and the development code in different repositories so that it will be easy for me to push to my CDN
The text was updated successfully, but these errors were encountered: