How to run shell script (.sh files) in Gulp 4?
Hello to everyone and Happy New Year!
Since Gulp version 4 I can't run a shell script.
I have simple shell script.
if application id "com.adobe.estoolkit-4.0" is running then
display dialog "Close The App!" buttons {"OK"} default button 1
end if
When I run it this way, it works
const { exec } = require('child_process');
function checkAppisOpen() {
return exec('./utils/check.sh');
};
exports.run = checkAppisOpen;
But when I'm trying to use npm gulp-shell plugin it won't work.
Error: Did you forget to signal async completion?
See the code:
const shell = require('gulp-shell');
function checkAppisOpen() {
return shell('./utils/check.sh');
};
exports.run = checkAppisOpen;
I know I'm doing something wrong. Could please someone explain how this async completion works under the hood. Or at least where I could read about it. Because it seems like gulp documentation is not enough for me https://gulpjs.com/docs/en/getting-started/async-completion
shell gulp exec gulp-4 gulp-shell
add a comment |
Hello to everyone and Happy New Year!
Since Gulp version 4 I can't run a shell script.
I have simple shell script.
if application id "com.adobe.estoolkit-4.0" is running then
display dialog "Close The App!" buttons {"OK"} default button 1
end if
When I run it this way, it works
const { exec } = require('child_process');
function checkAppisOpen() {
return exec('./utils/check.sh');
};
exports.run = checkAppisOpen;
But when I'm trying to use npm gulp-shell plugin it won't work.
Error: Did you forget to signal async completion?
See the code:
const shell = require('gulp-shell');
function checkAppisOpen() {
return shell('./utils/check.sh');
};
exports.run = checkAppisOpen;
I know I'm doing something wrong. Could please someone explain how this async completion works under the hood. Or at least where I could read about it. Because it seems like gulp documentation is not enough for me https://gulpjs.com/docs/en/getting-started/async-completion
shell gulp exec gulp-4 gulp-shell
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23
add a comment |
Hello to everyone and Happy New Year!
Since Gulp version 4 I can't run a shell script.
I have simple shell script.
if application id "com.adobe.estoolkit-4.0" is running then
display dialog "Close The App!" buttons {"OK"} default button 1
end if
When I run it this way, it works
const { exec } = require('child_process');
function checkAppisOpen() {
return exec('./utils/check.sh');
};
exports.run = checkAppisOpen;
But when I'm trying to use npm gulp-shell plugin it won't work.
Error: Did you forget to signal async completion?
See the code:
const shell = require('gulp-shell');
function checkAppisOpen() {
return shell('./utils/check.sh');
};
exports.run = checkAppisOpen;
I know I'm doing something wrong. Could please someone explain how this async completion works under the hood. Or at least where I could read about it. Because it seems like gulp documentation is not enough for me https://gulpjs.com/docs/en/getting-started/async-completion
shell gulp exec gulp-4 gulp-shell
Hello to everyone and Happy New Year!
Since Gulp version 4 I can't run a shell script.
I have simple shell script.
if application id "com.adobe.estoolkit-4.0" is running then
display dialog "Close The App!" buttons {"OK"} default button 1
end if
When I run it this way, it works
const { exec } = require('child_process');
function checkAppisOpen() {
return exec('./utils/check.sh');
};
exports.run = checkAppisOpen;
But when I'm trying to use npm gulp-shell plugin it won't work.
Error: Did you forget to signal async completion?
See the code:
const shell = require('gulp-shell');
function checkAppisOpen() {
return shell('./utils/check.sh');
};
exports.run = checkAppisOpen;
I know I'm doing something wrong. Could please someone explain how this async completion works under the hood. Or at least where I could read about it. Because it seems like gulp documentation is not enough for me https://gulpjs.com/docs/en/getting-started/async-completion
shell gulp exec gulp-4 gulp-shell
shell gulp exec gulp-4 gulp-shell
asked Jan 3 at 12:25
VladVlad
1615
1615
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23
add a comment |
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022254%2fhow-to-run-shell-script-sh-files-in-gulp-4%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
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022254%2fhow-to-run-shell-script-sh-files-in-gulp-4%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
It looks like the preferred way to use gulp.shell is via shell.task. What happens if you use return shell.task(….)? Otherwise try the callback function route: function checkAppisOpen(done) { return shell(…..); done(); };
– Mark
Jan 3 at 15:05
Thank you for the reply @Mark. Unfortunately, in both ways, you pointed, still the same result. The error is: The following tasks did not complete: run [02:21:56] Did you forget to signal async completion?
– Vlad
Jan 4 at 0:23