Marked: Whitespace in fenced code info string breaks rendering

[camwiegert]

Describe the bug

When there is whitespace in the info string of a fenced code block, like so:

```html foo

...the block is not parsed as a code block. It appears to be rendered as a paragraph:

<p>```html foo</p>

To Reproduce

Steps to reproduce the behavior:

1. Add a whitespace character in the info string of a fenced code block.
2. Render with the default renderer.

Expected behavior

When there is whitespace in the info string, GFM appears to use the first word as the language and ignore the rest. (As demonstrated here) I would expect Marked to do the same by default and pass the entire info string to a custom renderer.

Thank you! 👋

[camwiegert]

For reference, here is the GFM spec on info strings.

[UziTech]

comfirmed

common mark spec example #112

[Feder1co5oave]

1387 returns this:

~
bin/marked
```html foo
^D

~~

which seems correct

[camwiegert]

Thanks for addressing this! 😄