Flowchart parsing issue with CRLF

Describe the bug Mermaid sometimes fails to parse valid flowchart input if new lines are encoded as CRLF instead of LF. This causes unexpected behaviour when using subgraphs, and potentially in other situations too. This may occur when static content served by Windows systems is fed to Mermaid.

Potential root cause This might be caused by flow.jison defining NEWLINE as \n instead of the more platform independent regex \r?\n.

Workarounds

• Convert CRLF to LF, either programmatically or on the file system
• Migrate away from Windows

To Reproduce See codepen and snippet below. The last statement results in a parsing error in the console.

const dotest = (test, input) => {
  try {
    mermaid.render(test, input, () => {}); 
  } catch (err) { 
    console.error("Error in %s:\n\n%s", test, err);
  }
};
mermaid.initialize({startOnLoad: false});
dotest("Test1", "graph LR\nsubgraph\nA --> B\nend");
dotest("Test2", "graph LR\r\nsubgraph\r\nA --> B\r\nend");

Expected behavior No errors are written to the console.

Desktop (please complete the following information):

• Mermaid: 8.2.3
• OS: Windows 7
• Browser: Google Chrome
• Version: 75.0.3770.142

[GDFaber]

This seems to me like a good start for someone who is new to the project. I’d like to give it a try if that’s ok for you.

[IOrlandoni]

Thank you everyone for your contributions!