glenn2223/vscode-live-sass-compiler

BUG: SASS compilation kills React processes with ENOENT, interfering with Webpack cache files

evilgeniuscreative opened this issue · 4 comments

evilgeniuscreative commented

BUG:

Any SCSS errors, and sometimes even just SCSS compiling at all will kill the run process with an error similar to this:

[Error: ENOENT: no such file or directory, stat '/Users/me/Documents/ReactT/App/node_modules/.cache/default-development/1.pack'] {
errno: -2,
code: 'ENOENT',
syscall: 'stat',
path: '/Users/me/Documents/React/App/node_modules/.cache/default-development/1.pack'
}

The only difference in the errors is the final filename. Sometimes it's 2.pack or 1.pack or occasionally something else.

After lots of testing, this seems to be related directly to the SCSS processing, and only happens at that time.

glenn2223 commented

I don't believe this has anything to do with my extension. Do you have any thing that packs all your CSS files together?

I only say because you mention webpack, which the extension doesn't apply to your workspace

If your sure that the kids to do with SASS processing and not the packing of files then you should be able to reproduce it using sass directly from the command lineref

evilgeniuscreative commented
glenn2223 commented

But the error you get mentions '/Users/me/Documents/ReactT/App/node_modules/.cache/default-development/1.pack'. An error with my extension wouldn't mention a pack file in your project.

If you can still reproduce the error using the SASS CLI - with nothing else enabled or running in the background - you would be better opening an issue over at sass/dart-sass. As it's this package that processes the compilation. I just integrate that with some VS Code stuff (and some other feature stuff 😜)

evilgeniuscreative commented