custom absolute path for npm build #778

Activity

1. gaearon commented on Sep 27, 2016

   

   gaearon

   on Sep 27, 2016

   Contributor

   More actions

   There is no such option but you can work around it. Change build in your package.json scripts to perform an additional step, like react-scripts build && cp -r build ../your-folder. If you're on Windows the command would look differently but the idea is the same. There are also ways to write it in a cross platform way if you remove spaces before and after ampersands and launch a Node script that copies files instead of a UNIX command. I hope this helps!

   👍React with 👍7Reacted by Iurii Kucherov, David Fox, William Le, Philip Cox, Or Duan, Rajat Saxena and ZoranZilicFTN
2. gaearon

   closed this as completedon Sep 27, 2016
3. adityashankert commented on Sep 27, 2016

   

   adityashankert

   on Sep 27, 2016

   Last edited by adityashankert

   Author

   More actions

   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?
4. gaearon commented on Sep 27, 2016

   

   gaearon

   on Sep 27, 2016

   Contributor

   More actions

   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.
5. gaearon

   reopened this on Sep 27, 2016
6. gaearon

   closed this as completedon Sep 27, 2016
7. gaearon commented on Sep 27, 2016

   

   gaearon

   on Sep 27, 2016

   Contributor

   More actions

   (Oops, didn’t mean to reopen. Fat finger.)
8. ChuckkNorris commented on Aug 26, 2017

   

   ChuckkNorris

   on Aug 26, 2017

   Last edited by ChuckkNorris

   More actions

   @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 .angular-cli.json which would still enable other scripts to always know the build directory by reading that file.

   For cross-platform dev:

   "scripts": {
       "windows-build": "react-scripts build && xcopy /f /y build wwwroot",
       "mac-build": "react-scripts build && cp -r build ../wwwroot"
     }
   

   Edit:
   If you switch to use either Git Bash or Ubuntu Bash on Windows, the Unix commands work just fine:
   Example which builds the react app, copies the contents from the /build folder to the /wwwroot directory and removes the build directory:

     "scripts": {
       "build": "react-scripts build && cp -r build/. wwwroot && rm -R build",
     }
   
9. ZoranZilicFTN commented on Feb 22, 2018

   

   ZoranZilicFTN

   on Feb 22, 2018

   Last edited by ZoranZilicFTN

   More actions

   how would you write

     "scripts": {
       "build": "react-scripts build && cp -r build/. wwwroot && rm -R build",
     }
   

   for Windows.

   I tried with xcopy, but when I npm run build
   where

     "scripts": {
           "build": " "react-scripts build && xcopy C:\FolderOne C:\FolderTwo",
     }
   

   I get this error in the command line:

   npm ERR! Failed to parse json
   npm ERR! Unexpected token ' in JSON at position 212 while parsing near '...-env.dev",
   npm ERR! "build": '"xcopy C:\FolderOne...'

   👍React with 👍1Reacted by ZoranZilicFTN

   ❤️React with ❤️1Reacted by ZoranZilicFTN
10. lock

    locked and limited conversation to collaborators on Jan 20, 2019