gulp-shell: command executing continuously












0















I have never tried to execute a CLI command before through Gulp until today. What I am trying to do is:




  • Watch for changes in *js files through gulp watch in my project

  • Trigger browserify CLI command to rebuild my main.js to build.js file.

  • Using npm package gulp-shell to achieve the above through gulp.


My gulpfile.js file



var gulp = require("gulp");
var shell = require('gulp-shell');

gulp.task('browserify-changes', shell.task('browserify js/main.js -o js/build.js -d'));

gulp.task('watch', function() {
gulp.watch('js/*.js', gulp.series('browserify-changes'));
});



Apparently the CLI command browserify js/main.js -o js/build.js -d works fine if I directly execute it through my bash.




BUT



When I want the same thing to happen through gulp watch I get this:



...
[1] [09:40:48] Using gulpfile D:workspacefungulpfile.js
[1] [09:40:48] Starting 'watch'...
[1] [09:40:54] Starting 'browserify-changes'...
[1] [09:40:55] Finished 'browserify-changes' after 305 ms
[1] [09:40:55] Starting 'browserify-changes'...
[1] [09:40:55] Finished 'browserify-changes' after 295 ms
[1] [09:40:55] Starting 'browserify-changes'...
[1] [09:40:56] Finished 'browserify-changes' after 307 ms
[1] [09:40:56] Starting 'browserify-changes'...
[1] [09:40:56] Finished 'browserify-changes' after 301 ms
[1] [09:40:56] Starting 'browserify-changes'...
[1] [09:40:57] Finished 'browserify-changes' after 302 ms
[1] [09:40:57] Starting 'browserify-changes'...
... and on
... and on until my bash goes crazy


Just a note: I have tried all other plugins (like gulp-shell) available on the internet, my problem doesn't change.
Please help me understand what am I doing wrong and how can I fix it?



Thanks










share|improve this question



























    0















    I have never tried to execute a CLI command before through Gulp until today. What I am trying to do is:




    • Watch for changes in *js files through gulp watch in my project

    • Trigger browserify CLI command to rebuild my main.js to build.js file.

    • Using npm package gulp-shell to achieve the above through gulp.


    My gulpfile.js file



    var gulp = require("gulp");
    var shell = require('gulp-shell');

    gulp.task('browserify-changes', shell.task('browserify js/main.js -o js/build.js -d'));

    gulp.task('watch', function() {
    gulp.watch('js/*.js', gulp.series('browserify-changes'));
    });



    Apparently the CLI command browserify js/main.js -o js/build.js -d works fine if I directly execute it through my bash.




    BUT



    When I want the same thing to happen through gulp watch I get this:



    ...
    [1] [09:40:48] Using gulpfile D:workspacefungulpfile.js
    [1] [09:40:48] Starting 'watch'...
    [1] [09:40:54] Starting 'browserify-changes'...
    [1] [09:40:55] Finished 'browserify-changes' after 305 ms
    [1] [09:40:55] Starting 'browserify-changes'...
    [1] [09:40:55] Finished 'browserify-changes' after 295 ms
    [1] [09:40:55] Starting 'browserify-changes'...
    [1] [09:40:56] Finished 'browserify-changes' after 307 ms
    [1] [09:40:56] Starting 'browserify-changes'...
    [1] [09:40:56] Finished 'browserify-changes' after 301 ms
    [1] [09:40:56] Starting 'browserify-changes'...
    [1] [09:40:57] Finished 'browserify-changes' after 302 ms
    [1] [09:40:57] Starting 'browserify-changes'...
    ... and on
    ... and on until my bash goes crazy


    Just a note: I have tried all other plugins (like gulp-shell) available on the internet, my problem doesn't change.
    Please help me understand what am I doing wrong and how can I fix it?



    Thanks










    share|improve this question

























      0












      0








      0








      I have never tried to execute a CLI command before through Gulp until today. What I am trying to do is:




      • Watch for changes in *js files through gulp watch in my project

      • Trigger browserify CLI command to rebuild my main.js to build.js file.

      • Using npm package gulp-shell to achieve the above through gulp.


      My gulpfile.js file



      var gulp = require("gulp");
      var shell = require('gulp-shell');

      gulp.task('browserify-changes', shell.task('browserify js/main.js -o js/build.js -d'));

      gulp.task('watch', function() {
      gulp.watch('js/*.js', gulp.series('browserify-changes'));
      });



      Apparently the CLI command browserify js/main.js -o js/build.js -d works fine if I directly execute it through my bash.




      BUT



      When I want the same thing to happen through gulp watch I get this:



      ...
      [1] [09:40:48] Using gulpfile D:workspacefungulpfile.js
      [1] [09:40:48] Starting 'watch'...
      [1] [09:40:54] Starting 'browserify-changes'...
      [1] [09:40:55] Finished 'browserify-changes' after 305 ms
      [1] [09:40:55] Starting 'browserify-changes'...
      [1] [09:40:55] Finished 'browserify-changes' after 295 ms
      [1] [09:40:55] Starting 'browserify-changes'...
      [1] [09:40:56] Finished 'browserify-changes' after 307 ms
      [1] [09:40:56] Starting 'browserify-changes'...
      [1] [09:40:56] Finished 'browserify-changes' after 301 ms
      [1] [09:40:56] Starting 'browserify-changes'...
      [1] [09:40:57] Finished 'browserify-changes' after 302 ms
      [1] [09:40:57] Starting 'browserify-changes'...
      ... and on
      ... and on until my bash goes crazy


      Just a note: I have tried all other plugins (like gulp-shell) available on the internet, my problem doesn't change.
      Please help me understand what am I doing wrong and how can I fix it?



      Thanks










      share|improve this question














      I have never tried to execute a CLI command before through Gulp until today. What I am trying to do is:




      • Watch for changes in *js files through gulp watch in my project

      • Trigger browserify CLI command to rebuild my main.js to build.js file.

      • Using npm package gulp-shell to achieve the above through gulp.


      My gulpfile.js file



      var gulp = require("gulp");
      var shell = require('gulp-shell');

      gulp.task('browserify-changes', shell.task('browserify js/main.js -o js/build.js -d'));

      gulp.task('watch', function() {
      gulp.watch('js/*.js', gulp.series('browserify-changes'));
      });



      Apparently the CLI command browserify js/main.js -o js/build.js -d works fine if I directly execute it through my bash.




      BUT



      When I want the same thing to happen through gulp watch I get this:



      ...
      [1] [09:40:48] Using gulpfile D:workspacefungulpfile.js
      [1] [09:40:48] Starting 'watch'...
      [1] [09:40:54] Starting 'browserify-changes'...
      [1] [09:40:55] Finished 'browserify-changes' after 305 ms
      [1] [09:40:55] Starting 'browserify-changes'...
      [1] [09:40:55] Finished 'browserify-changes' after 295 ms
      [1] [09:40:55] Starting 'browserify-changes'...
      [1] [09:40:56] Finished 'browserify-changes' after 307 ms
      [1] [09:40:56] Starting 'browserify-changes'...
      [1] [09:40:56] Finished 'browserify-changes' after 301 ms
      [1] [09:40:56] Starting 'browserify-changes'...
      [1] [09:40:57] Finished 'browserify-changes' after 302 ms
      [1] [09:40:57] Starting 'browserify-changes'...
      ... and on
      ... and on until my bash goes crazy


      Just a note: I have tried all other plugins (like gulp-shell) available on the internet, my problem doesn't change.
      Please help me understand what am I doing wrong and how can I fix it?



      Thanks







      javascript gulp






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 1 at 4:22









      Siddhartha ChowdhurySiddhartha Chowdhury

      1,3321023




      1,3321023
























          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%2f53992990%2fgulp-shell-command-executing-continuously%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%2f53992990%2fgulp-shell-command-executing-continuously%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

          Mossoró

          Error while reading .h5 file using the rhdf5 package in R

          Pushsharp Apns notification error: 'InvalidToken'