Use marked instead of roaster + update marked

[aminya]

Description of the Change

This:

• Uses marked instead of roaster which was deprecated years ago.
• Updates marked to the latest version

Benefits

• The old roaster was deprecated years ago and can bring many bugs and security issues.
• The new marked has many improvements to its engine. Follows the latest GitHub behavior and has fixed a huge number of bugs, security issues, etc.

Possible Drawbacks

N/A

Applicable Issues

Closes #1148
Fixes #500

[aminya]

@UziTech You are one of the main "marked" developers. It would be nice if you review this!

GitHub does not break line in a single line anymore. Should we update the failing test?
This is based on: markedjs/marked#1620.

[UziTech]

Github does support single line breaks on comments but not on readmes. I would do the same thing here. Enable line breaks for descriptions but not on the readme content.

I noticed that marked is being used in an asynchronous way, but since marked doesn't need to connect to the file system or database it still just runs on the main thread, which can be bad for performance and lead to ReDos attacks. We should run marked in a worker or Task wherever we want it to be off the main thread.

[aminya]

Github does support single line breaks on comments but not on readmes. I would do the same thing here. Enable line breaks for descriptions but not on the readme content.

Does this mean what you are suggesting?

I noticed that marked is being used in an asynchronous way, but since marked doesn't need to connect to the file system or database it still just runs on the main thread, which can be bad for performance and lead to ReDos attacks. We should run marked in a worker or Task wherever we want it to be off the main thread.

We need to merge atom/atom#21139 to be able to use WebWorkers. I think Task would be expensive here as it would start a new fork for every rendering.

After we merge atom/atom#21139, we can definitely use WebWorkers for this.

[UziTech]

Does this mean what you are suggesting?

yes

I think Task would be expensive here

I agree we should wait for web workers

[UziTech]

It looks like the tests fail because the renderer is removing html but the test expects <br/> to be allowed. marked fixed inline html not going through the html renderer which is why it is breaking when updating marked.

The solution would be to not allow all html or update the renderer to allow <br/>.

[aminya]

I added br method. If it does not work, I think we need to change html method to something like this:

renderer.html = (src) => {
	const match = src.match(/<br\/>/);
	if (match) {
		return `<br/>`
	}
	return ''
}

[aminya]

@sadick254 @darangi This is ready to go! 😃 All the tests pass.