error: [object SourceAnnotation] on Windows

[taylor1791]

On two different windows boxes

$ npm install -g api-mock
$ api-mock my\test\api.md
info:    Enabled Cross-Origin-Resource-Sharing (CORS)
info:           Allow-Origin: *
info:           Allow-Methods: GET, PUT, POST, PATCH, DELETE, TRACE, OPTIONS
info:           Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization, Referer, Prefer
info:    Listening on port 3000
error:   [object SourceAnnotation]
undefined

Any ideas?

[taylor1791]

If the API blueprint has carriage returns, it breaks in protagonist.

[ecordell]

Thanks for making a note of that!

api-mock uses protagonist to parse, which in turn uses snowcrash. The carriage returns are actually enforced in the C parser itself.

[zation]

@taylor1791 I got the same error as yours. Can you please let me know what do you mean by carriage? And how you fix this problem?
Thanks!

[ecordell]

@zation A carriage return is a control character (see: http://en.wikipedia.org/wiki/Carriage_return). On unixy systems, a new line is specified with just a newline character (\n in C-style escaping), but on windows it's often a new line + a carriage return (\n\r).

A lot of text editors have options for converting between the two styles. If your editor's find-replace supports escaping, you can even just replace \n\r with \n and call it a day.

[zation]

@ecordell thanks a lot! But I found my problem is not about the carriage return, it's because the spaces length for a tab is not standard...