-
Notifications
You must be signed in to change notification settings - Fork 3
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 compiling when partials (imported files) are stored #17
Comments
So - the plugin does not read or parse the files by itself so the plugin
does not know about use or import statements and hence partials.
It delegates the work to the underlying sass library being used when
compiling. ( It comes with a built-in sass library )
There is a functionality called "Dartsass: Watch a directory" ( Right click
on a directory in VSCode explorer and you will see that option ) . When
enabled - the sass cmd line will watch for all changes in that directory
recursively and recompile sass files to css as appropriate. Could be of
some help in your scenario.
You can explore the README to figure out how to configure a watcher etc. on
your platform ( linux / windows etc. )
…On Fri, Feb 19, 2021 at 1:47 PM Lakro ***@***.***> wrote:
If I have scss-subfiles (_partial.scss) which are imported to the
scss-mainfile (style.scss) by @import <https://github.com/import> or @use
<https://github.com/use>:
When I work in the subfiles
and store the subfile ...
the compiling does not start.
The plugin only compiles when the mainfile is saved..
Is there a trick to activate it or ist that an issue or missing
functionality?
I searched for information about that but could not find a solution. A
advice/feedback would be helpful.
br Lakro
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJMNUBRY3DRNGIQGJU5OLS7YNB5ANCNFSM4X35UU3Q>
.
|
Thx for your information. For local testing I checked out I Installed SASS by npm to I tried to add the SassBinPath to local workspace in different versions: I've got everytime the same Error Message: Same when I installed SASS by npm direct into the sass dir: In both cases every try to compile ends with he error message. Is this my not understanding the FAQ ... br Lakro |
Based on your comments above , I assume you are working on linux or a similar *nix variant.
should work. You can try starting a watcher on a directory and see if it launches a "process" on the bottom right side with the indicator - "Sass Watchers: 1 " . Let me know what you see so I can help. |
Thx for this extremly helpful hint!!! No. I am using Win10 with local xampp. (Sorry for not adding that.) Just as information for maybe others with similar questions: Install compiler by npm direct to root project folder In Complete description found in project description Thank your very much for your help. br Lakro |
Once more an additional hint: After installing sass compiler globally by npm to get auto compiling work on partial files: Windows 10: But to use the full path seems to work: Question: is that an issue with the extension or an problem on the windows system? Just to complete infos for maybe fixing it: Thank you for your work. br Lakro |
Sorry for the delayed reply as I am catching up on things now.
If the full path works and the relative path does not work - it may have something to do with the "current project". Were you working on "mutliple projects" in vscode . If so - is the scss file you were working on - in the same project as the one that had the sass package installed i.e. - |
If I have scss-subfiles (_partial.scss) which are imported to the scss-mainfile (style.scss) by @import or @use:
When I work in the subfiles
and store the subfile ...
the compiling does not start.
The plugin only compiles when the mainfile is saved..
Is there a trick to activate it or ist that an issue or missing functionality?
I searched for information about that but could not find a solution. A advice/feedback would be helpful.
br Lakro
The text was updated successfully, but these errors were encountered: