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

Sass Library Support #103

Open
chriseppstein opened this issue Aug 28, 2015 · 1 comment
Open

Sass Library Support #103

chriseppstein opened this issue Aug 28, 2015 · 1 comment

Comments

@chriseppstein
Copy link

I don't see any way to tap into the Sass options that are passed to node-sass. Without this, many sass extensions that have javascript functions, custom importers, will not work.

A simple, out of the box solution to this will be to integrate eyeglass into harp, then any sass extension can added to the project with a simple npm install -- eyeglass will discover the extensions and hook them into node-sass automatically (Here's a list of eyeglass compatible sass extensions that already exist)

Are you open to accepting a pull request that add eyeglass as a dependency so that sass modules can be added to projects?

If not, are you open to a pull request to terraform that makes it easier to customize the Sass options (that's all eyeglass needs in order to work)?

@kennethormandy
Copy link
Collaborator

Hey, I’m personally really looking forward to having Eyeglass modules work with Harp, if you want to open up a PR I think that is something we’d be happy to merge.

We’re working on getting Browserify added in next, currently we don’t treat the node_modules directory any differently from any other directory. I assume that needs to change for both, so it might be better to make any changes against this branch the since we’ll merge #98 first.

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

No branches or pull requests

2 participants