Gulp watch task is running multiple times when editing a file with VS Code
I just recently switched from Atom to VS Code, and I've been having an issue with my watch
gulp task running multiple times when saving.
Some things I've tried:
- I disabled all extensions, and the issue still occurred.
- I modified a file in Notepad multiple times, and the issue does not occur.
I'm fairly certain that this is something to do with how VS Code saves files. I did some digging, and I found this SO answer, which indicates that some editors create a "buffer" file before actually writing to the file you've edited, and I've also found this issue on VS Code's GitHub repository that seems to indicate that VS Code may be doing some kind of buffer file thing, but I haven't been able to identify how the files are named (otherwise I'd exclude them from the glob).
I have two possible ideas on how to solve this:
How can I tellGulp.watch()
to finish before it starts again?- How does VS Code name its "buffer" files, so that I can exclude them from being watched?
Either method above seems like it should work for my purposes, but I'm open to other suggestions as well.
EDIT: I figured out how to resolve this using the first method, but I think the second method would be ideal.
visual-studio-code gulp gulp-watch gulp-4
add a comment |
I just recently switched from Atom to VS Code, and I've been having an issue with my watch
gulp task running multiple times when saving.
Some things I've tried:
- I disabled all extensions, and the issue still occurred.
- I modified a file in Notepad multiple times, and the issue does not occur.
I'm fairly certain that this is something to do with how VS Code saves files. I did some digging, and I found this SO answer, which indicates that some editors create a "buffer" file before actually writing to the file you've edited, and I've also found this issue on VS Code's GitHub repository that seems to indicate that VS Code may be doing some kind of buffer file thing, but I haven't been able to identify how the files are named (otherwise I'd exclude them from the glob).
I have two possible ideas on how to solve this:
How can I tellGulp.watch()
to finish before it starts again?- How does VS Code name its "buffer" files, so that I can exclude them from being watched?
Either method above seems like it should work for my purposes, but I'm open to other suggestions as well.
EDIT: I figured out how to resolve this using the first method, but I think the second method would be ideal.
visual-studio-code gulp gulp-watch gulp-4
add a comment |
I just recently switched from Atom to VS Code, and I've been having an issue with my watch
gulp task running multiple times when saving.
Some things I've tried:
- I disabled all extensions, and the issue still occurred.
- I modified a file in Notepad multiple times, and the issue does not occur.
I'm fairly certain that this is something to do with how VS Code saves files. I did some digging, and I found this SO answer, which indicates that some editors create a "buffer" file before actually writing to the file you've edited, and I've also found this issue on VS Code's GitHub repository that seems to indicate that VS Code may be doing some kind of buffer file thing, but I haven't been able to identify how the files are named (otherwise I'd exclude them from the glob).
I have two possible ideas on how to solve this:
How can I tellGulp.watch()
to finish before it starts again?- How does VS Code name its "buffer" files, so that I can exclude them from being watched?
Either method above seems like it should work for my purposes, but I'm open to other suggestions as well.
EDIT: I figured out how to resolve this using the first method, but I think the second method would be ideal.
visual-studio-code gulp gulp-watch gulp-4
I just recently switched from Atom to VS Code, and I've been having an issue with my watch
gulp task running multiple times when saving.
Some things I've tried:
- I disabled all extensions, and the issue still occurred.
- I modified a file in Notepad multiple times, and the issue does not occur.
I'm fairly certain that this is something to do with how VS Code saves files. I did some digging, and I found this SO answer, which indicates that some editors create a "buffer" file before actually writing to the file you've edited, and I've also found this issue on VS Code's GitHub repository that seems to indicate that VS Code may be doing some kind of buffer file thing, but I haven't been able to identify how the files are named (otherwise I'd exclude them from the glob).
I have two possible ideas on how to solve this:
How can I tellGulp.watch()
to finish before it starts again?- How does VS Code name its "buffer" files, so that I can exclude them from being watched?
Either method above seems like it should work for my purposes, but I'm open to other suggestions as well.
EDIT: I figured out how to resolve this using the first method, but I think the second method would be ideal.
visual-studio-code gulp gulp-watch gulp-4
visual-studio-code gulp gulp-watch gulp-4
edited Nov 20 '18 at 16:52
JacobTheDev
asked Nov 20 '18 at 16:47
JacobTheDevJacobTheDev
6,3252170128
6,3252170128
add a comment |
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%2f53397722%2fgulp-watch-task-is-running-multiple-times-when-editing-a-file-with-vs-code%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%2f53397722%2fgulp-watch-task-is-running-multiple-times-when-editing-a-file-with-vs-code%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