JS CLI: Load plugins from the command line

[Hackzzila]

Since this is supposed to replace Ruby Sass, I thought I should ask here. Writing a package manager, I would like to see plugin support like Less, where you can use --foo to use the plugin less-plugin-foo. Currently I had to make my own command for compiling Sass (using node-sass) so I can have preprocessors, postprocessors, functions, and importers. Related to #10 and #9.

[nex3]

I'd definitely like to support some kind of plugin loading from the CLI (although allowing any flag name seems like a forwards-compatibility nightmare). Maybe something like --use foo.

That said, this is probably a post-1.0.0 feature—I want to get the core and the node-sass compatibility rock solid first.

[Hackzzila]

Once #10 and #9 are done I could probably make a PR for this, since I happen to know Dart.

[gabrielmaldi]

Now that Dart Sass supports both sourcemaps and extension functions, I'd love to migrate from Ruby Sass right away!

The one thing that's stopping us is this issue. @Hackzzila, now that #9 and #10 are done, would you be willing to work on a PR for this? Thanks!

[xzyfer]

We have been discussing this on and off in Node Sass. The current thinking is something like .sassrc file.

[nex3]

Before taking a PR, we need to come up with an interface that's agreed on between Dart Sass and Node Sass. My preference would also be to wait on this until we have the next revision of the function and importer APIs implemented, so that we don't encourage more use of the existing APIs that we plan to deprecate.

[bdkjones]

It's been a few years since any of the "plugin" issue threads have seen updates. Is there a consensus on how this will move forward yet?

[nex3]

Issues like these need someone to drive them forward in order for progress to be made. The path forward is clear: create a design proposal and iterate on it based on feedback. But someone needs to be willing to invest the time and energy to walk down that path.