Mithril.js: [ospec] newlines in error messages confuse the error reporter

[pygy]

Description:

The presence of newlines in error messages cause a line of said message to be displayed instead of the stack trace

Steps to Reproduce:

https://runkit.com/58603d35d1b6b10013e1e652/58603d36d1b6b10013e1e653

[isiahmeadows]

I'll note it wasn't exactly trivial for me to nix it in a cross-runtime setting. Note that if you were to rip the code off, you'll need to remove the calls to formatLineBreaks.

[isiahmeadows]

Closing, since this issue has not been updated in over a month, and typically, issues inactive for that long do not usually produce any action. If you feel something in Mithril needs added or changed, please file a new issue.

[pygy]

The issue is still present.

[isiahmeadows]

Okay. Note that I did actually find a way to address the case myself, so that could be informative.

[RodericDay]

Hmmm how about this:

- var stackTrace = r.error.match(/^(?:(?!Error|[\/\\]ospec[\/\\]ospec\.js).)*$/m)
+ var stackTrace = r.error.match(/^(?:(?!Error|[\/\\]ospec[\/\\]ospec\.js).)*$/gm).slice(-1)

I think there's better approaches, but this one keeps the regex the same. It just captures extra groups that also match the description (m -> gm), and picks the last one (.slice(-1)).