Work In Progress: feature: use node-sass's importer hook to help tools track dependencies.

[cgc]

noticed that a hook into sass's @import() statement was recently added to node-sass, so I figured I'd take a stab at writing integration for it! closely follows similar changes to jadeify and lessify, as well as a similar change for a different static asset manager.

This change depends on benbria/browserify-transform-tools#10

[cgc]

it's a bit aggressive to do every possible file, but the alternative is fs.exists. Not sure which is more/less intrusive?

[cgc]

ping @davidguttman

[davidguttman]

Hey, really sorry for the delay on this!

I'm not entirely sure what this is for, but I'm all for it if it adds something you want/need and doesn't affect previous functionality.

As for the specific questions you had:

1. fs.exists is fine with me -- I'd go with the option that is more clear.
2. mocha is ok, personal preference is tape
3. All tests should be run from npm test

[cgc]

Hi @davidguttman,

This change uses a relatively new feature in node-sass to report @import()ed files to watchify (using the file event). In this PR's test case, the files something.scss and _settings.scss are reported to browserify as dependencies of main.scss, so watchify will recompile main.scss if either something.scss or _settings.scss are modified. This can really improve the watchify development process for projects that use @import().

npm test sounds good. I'll look into tape.