chore(deps): update dependency typescript to v4

[renovate]

This PR contains the following updates:

Package	Update	Type	Change	Sourcegraph
typescript (source)	major	devDependencies	3.9.7 -> 4.0.2

---

Release Notes

Microsoft/TypeScript

v4.0.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v4.0.0 (Beta).
• fixed issues query for Typescript v4.0.1 (RC).
• fixed issues query for Typescript v4.0.2.

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[JamieMagee]

Blocked by taoqf/node-html-parser#61. I'll try and contribute a fix upstream.

[JamieMagee]

Upstream isn't responsive to my patch, and it looks like the maintainer hasn't been active since June. I don't want to fork and maintain the package, so I'll switch out node-html-parser for cheerio instead.

[viceice]

I've found that jsdom is much more strict while parsing html. So is can throw errors if html structure is somehow invalid. 🤔

What alternatives do we have beside cheerio ?

[viceice]

maybe fork node-html-parser until upstream is fixed?

[JamieMagee]

I've found that jsdom is much more strict while parsing html. So is can throw errors if html structure is somehow invalid.

What alternatives do we have beside cheerio ?

I chose jsdom as it is still being maintained, whereas cheerio's most recent release is an RC from 1 year ago or a 0.x version from 4 years ago. Also jsdom has a similar API to node-html-parser, compared to parse5 or htmlparser2 which I also considered.

maybe fork node-html-parser until upstream is fixed?

It's technically possible, but I'd prefer not to take on the maintenance burden. And it's hard to say if or when upstream will be fixed. the maintainer hasn't been active on GitHub for 3 months.

[renovate-release]

🎉 This PR is included in version 23.20.0 🎉

The release is available on:

• GitHub release
• 23.20.0

Your semantic-release bot 📦🚀