Import-only files are not monitored for changes about django-sass-processor

[jrief]

I see, you mean @import "somefile"; where _somefile.scss does not contain CSS rules, but only stuff which does not materialize into CSS, for instance mixins, variables and functions.

Hmm, difficult to achieve since the sourcemap is the only feasible source which can be used for dependency tracking. Do you have a better idea?

[Skynet0]

My specific setup is something like

css/
  components/
    _button.scss
    _table.scss
  main.scss

Where _button.scss and _table.scss contain declarations, and main.scss contains

@import "components/button";
@import "components/table";

I include <link href="{% sass_src 'css/main.scss' %}" rel="stylesheet" type="text/css" /> in my base template.

If I add a new component _header.scss, main.scss isn't in the sourcemap and therefore an added @import won't be picked up. The scenario you mentioned would likely run into the same general problem.

I don't have a clean solution off the top of my head, unfortunately. Some meh candidates:

• Add an optional "always recompile" argument to the tag (would solve the problem, but not at all elegantly)
• Specify extra files to watch for a particular sass_src (too long to put in the tag; feels clunky to do it in settings)

At the least, adding documentation for this behavior + a workaround would be appreciated.

[jrief]

If I add a new component _header.scss, main.scss …

Do you want to say:

"If I add a new component _header.scss to main.scss … "?

I just checked on my own system. In the sourcemap main.css.map the first entry in sources: […] must be main.scss. This means that touching main.scss triggers a recompilation.

[Skynet0]

Do you want to say:

"If I add a new component _header.scss to main.scss … "?

Yes, thanks.

Ah, I see -- I forgot to mention that I use dart-sass (on M2 MacOS) via https://pypi.org/project/django-sass-processor-dart-sass/. I just checked with libsass, and see the behavior you describe.

[jrief]

so then, can this be closed?

[Skynet0]

Sounds right, yes. I'll open an issue against the other package as an FYI.

[jrief]

django-sass-processor shall be refactored towards dart-sass anyway. There are many nice features such as @use which are not supported by libsass.