Optional sheetify.json?

[jamsinclair]

Slightly related to #119. I find plugins pollute the package.json browserify property and become a bit cumbersome due to heavy nesting.

What are gut feelings towards an optional sheetify.json file?

E.g.

sheetify.json file with plugins and options defined

{
  "use": [
    "sheetify-sass",
    [
      "sheetify-postcss",
      {
        "plugins": [
          "autoprefixer"
        ]
      }
    ]
  ],
  "basedir": "."
}

My now cleaner package.json

.......
  "browserify": {
    "transform": [
      "sheetify/transform",
      "babelify"
    ]
  }
.......

I'm happy to contribute a PR to add this functionality, if contributors/owners are okay with this suggestion and direction 😸

[yoshuawuyts]

Nah, not I'm not too interested in this; browserify doesn't have a separate file either and I think we should kinda follow their lead.

…

On Thu, Mar 16, 2017 at 2:12 PM Jamie ***@***.***> wrote: Slightly related to #119 <#119>. I find plugins pollute the package.json browserify property and become a bit cumbersome. What are gut feelings towards an optional sheetify.json file? E.g. sheetify.json file with plugins and options defined { "use": [ "sheetify-sass", [ "sheetify-postcss", { "plugins": [ "autoprefixer" ] } ] ], "basedir": "." } My now cleaner package.json ....... "browserify": { "transform": [ "sheetify/transform", "babelify" ] } ....... I'm happy to contribute a PR to add this functionality, if contributors/owners are okay with this suggestion and direction 😸 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#120>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWlerTNTXI3_lsE7nGMoV0qad9CD9QNks5rmTVFgaJpZM4MfR1p> .

[jamsinclair]

Good point, totally makes sense 👍

Closing, because issue question now answered.