-
Notifications
You must be signed in to change notification settings - Fork 463
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
Export AST #430
Comments
sourcemaps contains all imported files, you can probably use that. |
That's a bit of a hack, but you're right that I probably good. An AST would still be helpful for other operations. |
+1 for a proper AST. Would help with dependency tree operations plus lowers the barrier to entry for other linters besides scss-lint. |
+1 from me. I'd really like access to the AST for being able to map a proper dependency graph |
I wonder if this is doable by reading the source map (just landed in #481). |
I solved my immediate problems by accepting that sass is a black box. Luckily libsass has a stats object you can pass in, which it fills with the files that were included in the build. No proper dependency tree, ast node reference or anything, but it solved my problem of setting up file watchers automatically on any file that might be of interest |
Aha, so it does. Nice find: https://github.com/sass/node-sass#stats |
I need to get the Sass AST so I can query it for things like imported files.
References: sass/node-sass#248
The text was updated successfully, but these errors were encountered: