Thanks @synaptiko! Does this work if you link it to your app and run? If all appears to be working on your end, I am fine with merging. We don't do much maintenance on this. I switched to using ember-cli-stylelint myself.

@rwwagner90 thanks for a good hint to test this scenario. There is actually a problem in case you have isDevelopingAddon() { return true; } in a nested addon and you run ember build from the app. The scss files are checked multiple times. I'll debug it and hopefully find some fix to this. But without the isDevelopingAddon flag it works fine.

@synaptiko yeah I believe that was the reason we had not merged these changes in.

@rwwagner90 ok, I "found" a solution but I'm afraid you won't like it :-) It reads some properties available on app, app.project and tree which it's kind of hacky and I'm not sure if it's covering all the other possible cases.

Out of curiosity I also checked ember-cli-stylelint but it seems to me that it suffers by the same issue, it won't work inside the addon.

Btw. by playing with this I discovered that even the code in master has this issue with duplicated output when your app depends on an addon with isDevelopingAddon() { return true; }.

@synaptiko I use ember-cli-stylelint in my addons and it works fine. I think people probably just shouldn't check in isDevelopingAddon() { return true; }

We fixed it in our fork and later we revisit usage of ember-cli-stylelint. No need to keep this PR opened.