Output errors?

[RobLoach]

When SASS building fails, it just outputs:

> metalsmith
  Metalsmith · undefined

We do return the error, should Metalsmith do a better job of error reporting?

[stevenschobert]

Hey @RobLoach. Yeah, it definitely should be printing our something more useful than that. Can you provide some more details about what you're seeing?

I had thought @ubenzer had fixed that in #12, but maybe something changed since then.

If so, we can add a test case for it for future reference.

[stevenschobert]

@RobLoach Were you still having issues with this?

[RobLoach]

@stevenschobert I believe I fixed the error with that pull request branch. Will do more testing and report back.

[RobLoach]

Syntax errors still report undefined from Metalsmith.

[stevenschobert]

@RobLoach How are you handling errors in your project? Any compilation errors should be available through Metalsmith's build callback (this was handled in #12).

metalsmith(__dirname)
  .use(sass())
  .build(function done(err) {
    // err should contain errors
  });

[thiagodemellobueno]

@stevenschobert we're using metalsmith.json, is there a catch (or a plugin) that can gracefully handle errors in a similar manner?

[stevenschobert]

Corrected in v0.6.1! Sorry about that folks, looks like when it was implemented in #12, errors were being passed up the chain as a simple string.

Metalsmith's CLI expects the error to be an actual Error object. I've updated the tests and patched it in 9a15861.

Let me know if that works for you!

[RobLoach]