copy files with npm copyfiles to another directory










0















I want that in the end of my build script, the build folder will be copy to another location, so I tried using copy-files-package -



"build": "react-scripts build && copyfiles build/*. out",


I was not able to figure out how to copy the entire build folder to another location, trying to specify the location like C:/someLocaion/build2 will result in the console showing SomeLocaion/build2.










share|improve this question






















  • What does the current script produces?

    – Abrar
    Nov 14 '18 at 15:27











  • creates a build folder, and nothing else.

    – Itsik Mauyhas
    Nov 14 '18 at 15:30











  • Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

    – Abrar
    Nov 14 '18 at 15:41











  • I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

    – Abrar
    Nov 14 '18 at 15:42






  • 1





    @Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

    – RobC
    Nov 14 '18 at 19:08















0















I want that in the end of my build script, the build folder will be copy to another location, so I tried using copy-files-package -



"build": "react-scripts build && copyfiles build/*. out",


I was not able to figure out how to copy the entire build folder to another location, trying to specify the location like C:/someLocaion/build2 will result in the console showing SomeLocaion/build2.










share|improve this question






















  • What does the current script produces?

    – Abrar
    Nov 14 '18 at 15:27











  • creates a build folder, and nothing else.

    – Itsik Mauyhas
    Nov 14 '18 at 15:30











  • Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

    – Abrar
    Nov 14 '18 at 15:41











  • I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

    – Abrar
    Nov 14 '18 at 15:42






  • 1





    @Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

    – RobC
    Nov 14 '18 at 19:08













0












0








0








I want that in the end of my build script, the build folder will be copy to another location, so I tried using copy-files-package -



"build": "react-scripts build && copyfiles build/*. out",


I was not able to figure out how to copy the entire build folder to another location, trying to specify the location like C:/someLocaion/build2 will result in the console showing SomeLocaion/build2.










share|improve this question














I want that in the end of my build script, the build folder will be copy to another location, so I tried using copy-files-package -



"build": "react-scripts build && copyfiles build/*. out",


I was not able to figure out how to copy the entire build folder to another location, trying to specify the location like C:/someLocaion/build2 will result in the console showing SomeLocaion/build2.







npm create-react-app copyfile






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 14 '18 at 14:37









Itsik MauyhasItsik Mauyhas

1,40722055




1,40722055












  • What does the current script produces?

    – Abrar
    Nov 14 '18 at 15:27











  • creates a build folder, and nothing else.

    – Itsik Mauyhas
    Nov 14 '18 at 15:30











  • Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

    – Abrar
    Nov 14 '18 at 15:41











  • I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

    – Abrar
    Nov 14 '18 at 15:42






  • 1





    @Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

    – RobC
    Nov 14 '18 at 19:08

















  • What does the current script produces?

    – Abrar
    Nov 14 '18 at 15:27











  • creates a build folder, and nothing else.

    – Itsik Mauyhas
    Nov 14 '18 at 15:30











  • Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

    – Abrar
    Nov 14 '18 at 15:41











  • I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

    – Abrar
    Nov 14 '18 at 15:42






  • 1





    @Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

    – RobC
    Nov 14 '18 at 19:08
















What does the current script produces?

– Abrar
Nov 14 '18 at 15:27





What does the current script produces?

– Abrar
Nov 14 '18 at 15:27













creates a build folder, and nothing else.

– Itsik Mauyhas
Nov 14 '18 at 15:30





creates a build folder, and nothing else.

– Itsik Mauyhas
Nov 14 '18 at 15:30













Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

– Abrar
Nov 14 '18 at 15:41





Well, I ran the same script react-scripts build && copyfiles build/* out and it outputs out/build/* with the contents inside.

– Abrar
Nov 14 '18 at 15:41













I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

– Abrar
Nov 14 '18 at 15:42





I am assuming you are using Windows. In that case the problem is with using &&. Use & instead.

– Abrar
Nov 14 '18 at 15:42




1




1





@Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

– RobC
Nov 14 '18 at 19:08





@Abrar - The && operator works perfectly ok in npm scripts for chaining tasks on Windows too. It's logic is analogous to Bash too, i.e. the command on the right will only execute if the command on the left exits successfully with a zero exit code.

– RobC
Nov 14 '18 at 19:08












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53302679%2fcopy-files-with-npm-copyfiles-to-another-directory%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53302679%2fcopy-files-with-npm-copyfiles-to-another-directory%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Top Tejano songwriter Luis Silva dead of heart attack at 64

政党

天津地下鉄3号線