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

Is custom importer option really needed considering there is already includePaths? #60

Open
ivanblazevic opened this issue Jan 18, 2022 · 0 comments
Labels
question Further information is requested

Comments

@ivanblazevic
Copy link
Owner

@LakMoore just wanted to quick check - have you ever used custom importer, just wondering was it working for you because configuration is in json and for importer we need to provide JS function? Reason for asking is because I am upgrading sass lib and importer now has different structure so I would also like to cover it with e2e tests but first wanted to check if that feature is really required because there is already includePaths option which is alternative for importer.

Originally posted by @ivanblazevic in #2 (comment)

@ivanblazevic ivanblazevic added the question Further information is requested label Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant