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.

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

No SASS error message shown in VS Code. #14

Open
cwsoft opened this issue Dec 28, 2020 · 3 comments
Open

No SASS error message shown in VS Code. #14

cwsoft opened this issue Dec 28, 2020 · 3 comments

Comments

@cwsoft
Copy link

cwsoft commented Dec 28, 2020

When the .scss files contain an error, the VS Code Plugin only shows the return status code (e.g. Process exited with code: 65) instead of showing the detailed error message like shown when running sass --error-css option switched on. This behaviour doesn´t change with dartsass.debug option false or true either.

Would it be possible to always show the error message in the VS Code console so we can fix it right in the editor wihtout the need to open a terminal and check whats going on?

@akkumar
Copy link
Contributor

akkumar commented Jan 21, 2021

This seems like a crazy error so let me debug the same.

Couple of questions for me to understan / reproduce this better:

  1. Is the sassbinPath property set when you were using this ?
    or
  2. Is it because you were "watching" a directory and changing files in that directory ?

@cwsoft
Copy link
Author

cwsoft commented Jan 24, 2021

// My Dart Sass configuartion settings used in VSCode:
"dartsass.debug": false,
"dartsass.sassBinPath": "C:\Users\xxx\AppData\Roaming\npm\node_modules\sass\sass.js",
"dartsass.targetDirectory": "css",
"dartsass.disableMinifiedFileGeneration": false,
"dartsass.disableSourceMap": true,
"dartsass.disableAutoPrefixer": false,
"dartsass.autoPrefixBrowsersList": ["> 1%", "last 2 versions"]

Error happens when an error occurs in one of the SASS files. In this case I need to run SASS from the commandline so I am able to detect whats wrong.

@akkumar
Copy link
Contributor

akkumar commented Jan 10, 2022

This seems like a regression but at least I am unable to reproduce the same in the recent releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants