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

Support @import #13

Closed
lloydwatkin opened this issue Jul 9, 2014 · 1 comment
Closed

Support @import #13

lloydwatkin opened this issue Jul 9, 2014 · 1 comment

Comments

@lloydwatkin
Copy link

I know its a bad idea to include @import but some sites use this (we have them in development, not production).

Running it against the split files would make it easier to trace where my collisions are.

@SlexAxton
Copy link
Owner

Yea, there's two paths here, support loading in a 'folder' and support sourcemaps, so we can point back at your original files. Both of those are probably top priority as far as next features go. But they're already an issue ( #7 , #8 ), so I'm going to close this, and this'll be marked on both of those issues now.

Thanks!

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

No branches or pull requests

2 participants