Skip to content

Sass.js is a singleton #43

@dougludlow

Description

@dougludlow

I'm running into an issue where I need a separate instance of sass.js per compile, but it appears that sassjs is a singleton.

My use case is that for each file I compile, I cache its directory as a base url and in my custom importer I use that base url to determine the relative path. I'm enclosing that base url in a closure, but anytime I set importer it overrides the previous importer (because sassjs is a singleton) and I'm stuck with the last base url that was set.

Any ideas on how I can get around this? Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions