--config flag on CLI for config file

[rcchen]

Searched issues for a similar feature request but couldn't find anything, apologies if this is a dupe.

I'd like to have a --config argument for the node-sass CLI that allows a JSON configuration file to be passed in.

Specifically, it would allow me to consolidate a bunch of the arguments I pass into the CLI right now into a single configuration file that can be shared across my projects.

Example (config.json)

{
  "importer": "../path/to/shared/importer",
  "output": "./dist",
  "sourceMap": true,
}

Example (usage): node-sass --config ../path/to/config.json

Happy to make the contribution if this is something that might be desirable.

[sant123]

@xzyfer, what do you think?

[saper]

Looks like a perfect candidate for the initial implementation of #1156

[IceReaper]

I would prefer to have a node-sass.json file too. This would avoid the need to reconfigure the IDE for every developer again and again.

[patrickwelker]

That'd be very helpful (and a clean portable solution to the mess that some files of mine have become).

[xzyfer]

Could you provide and example of the mess?

…

On 11 Mar. 2018 4:09 am, "Patrick Welker" ***@***.***> wrote: That'd be very helpful (and a clean portable solution to the mess that some files of mine have become). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2113 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWKVUtwPR5MRb4gZXBvOqSKgHRafnks5tdAjPgaJpZM4PzJqN> .

[patrickwelker]

@xzyfer I referred to my package.json file which I use as a task runner since I canceled my Gulp and Grunt subscription. It can easily become a bit crowded in there. I see now that it sounded like I might have pages of pages of custom sass configurations. I always appreciate it when one can specify config files instead of having to add them to the package.json.

[hunkjazz]

Is that a thing, already?