Installing old marked version

[fokusferit]

Over the last 12 months the marked library fixed a couple of issues, regarding security, performance and also regExr.

Currently I'm facing the following problem when using Addon-Info in Combination with a Github Flavored Markdown:

Using Inner HTML at the beginning results in the issue that the rules.html Regular Expression from Marked is only able to recognize one Inner HTML item, afterwards it fails.

As an example, below is the Markdown result of Storybook + Addon-Info for our README which starts with the following Markdown:

<p align="center">
<img src="https://raw.githubusercontent.com/fabric-design/scss/master/fabric-logo.png"/>
</p>

<p align="center"></p>
=======

#### A set of React UI components for Retail Operations department.

#### Current Stewards:

---

results in the Following:

but it should look like this:

Solution:

Can we update your package.json dependency of marked to 0.6.0 ?

Issue:

Using the ^ (carat) with a leading Zero in npm semver results in only patch update cycle, this means, the last version npm installs is 0.3.19 and not 0.6.0. This might be intended or not (as I didn't knew that the carat operator behaves different between a leading Zero and 1).

[ndelangen]

@fokusferit I tried upgrading, but it has a bad effect on the support for inline elements such as <span> and <font> within markdown blocks.

If you make sure there a blank line between your html & markdown the above code should work I think.

[christianalfoni]

I will try to find some time to get down the latest marked here and see what we can do about the evaluation :)

[patsplat]

This PR patches marked #98