Thanks for all your help Peter!

I'm taking a look a this again–filtering out anything that isn't valid shouldn't be too hard–the only issue is that I'm not sure what would be the best way to handle the error.

It could:

1. Do nothing (not output anything).
2. Add a background color of red or something to make it apparent something went wrong.
   2.b Add some text with content saying what the error is.
3. prefered throw an error: postcss errors

After a quick glance–I'm not sure if anything is in place to handle any errors with lost.

Thoughts?

I prefer 3 as well. :)

I'll see what it would take to wire that up. You currently don't have any error handling in lost, right? I'm not missing it?

I suppose if there isn't, I should probably tackle error handling before tackling filtering and then throwing that error.

Yeah I haven't added any err handling

From @wyze

Sorry about the delay here. I cleared the notification and forgot to get back to it!

Testing is simple, just need to check if postcss throws when you pass something not valid. The tests seem basic as I created a method to wrap a majority of the testing since we were just comparing input to output.

Here is a test I added to test/lost-utility.js:

it('throws when not valid value', function() {
var processor = postcss([lost()]);

expect(processor.process('a { lost-utility: notvalid }')).to.throw;

});
And then just bring over the requires like they are in test/check.js.

My gist of the full test/lost-utility.js is here: https://gist.github.com/wyze/7f240bcd6deb985ec776

I'm closing the #193 PR as I need to redo the branch (with the repo transfer) and want to investigate a larger error handling thought process.