Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Vscode safe write from which? #28927

Closed
sbfkcel opened this issue Jun 17, 2017 · 5 comments
Closed

Vscode safe write from which? #28927

sbfkcel opened this issue Jun 17, 2017 · 5 comments
Assignees
@bpasero
Labels
file-io File I/O info-needed Issue requires more information from poster nodejs NodeJS support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@sbfkcel
Copy link

sbfkcel commented Jun 17, 2017

You need to allow the function to be turned off.
Otherwise, in the real-time compiler will cause the compiler is not successful.

https://webpack.js.org/guides/development/#adjusting-your-text-editor
@bpasero
Copy link
Member

bpasero commented Jun 19, 2017

We do not have atomic saving in VS Code. File writes go directly into the file.

@bpasero bpasero closed this as completed Jun 19, 2017
@sbfkcel
Copy link
Author

sbfkcel commented Jun 19, 2017

@bpasero
Vscode save the file there is a certain problem, there are many developers have the problem. see:

sass/node-sass#1894 (comment)

@bpasero
Copy link
Member

bpasero commented Jun 19, 2017 •
edited

@sbfkcel we use fs.writeFile(), if there is an issue with that I suggest to report this to node.js directly.

Can you please update the summary and description in a way that describes the problem fully.

@bpasero bpasero reopened this Jun 19, 2017
@bpasero bpasero self-assigned this Jun 19, 2017
@bpasero bpasero added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jun 19, 2017
@bpasero bpasero added this to the Backlog milestone Jun 19, 2017
@bpasero bpasero added the info-needed Issue requires more information from poster label Jun 19, 2017
@sbfkcel
Copy link
Author

sbfkcel commented Jun 19, 2017

@bpasero The problem should be above the node fs module.
Think you~~ 👍

@bpasero bpasero added file-io File I/O nodejs NodeJS support issues labels Nov 13, 2017
@bpasero bpasero removed this from the Backlog milestone Nov 16, 2017
@bpasero
Copy link
Member

bpasero commented Nov 17, 2017

I do not understand.

@bpasero bpasero closed this as completed Nov 17, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bpasero bpasero

Labels
file-io File I/O info-needed Issue requires more information from poster nodejs NodeJS support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bpasero @sbfkcel