Skip to content

Track external Sass dependencies for node_modules imports #242

@fasterthanlime

Description

@fasterthanlime

Problem

To support package Sass imports (e.g. @use "pico"), the Sass cell currently falls back to reading external files from disk.

That allows imports to compile, but it bypasses picante dependency tracking for those external files.

Why this matters

If imported Sass files under node_modules (or other load paths) change, incremental invalidation may miss them.

Follow-up work

  1. Capture the resolved external Sass dependency set during compilation.
  2. Feed those dependencies back into tracked inputs (path + hash/mtime) so picante can invalidate correctly.
  3. Ensure watcher behavior/invalidation covers external Sass deps.
  4. Add regression tests proving changes in imported package Sass trigger CSS rebuilds.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions