Issue/220 highlight null

[nonumpa]

Changes

1. Fixes TypeError: Cannot read property 'split' of undefined #220, return original text if highlight text and hyperlinks are null
   We still need to fix this issue in rumors-api

2. Update package-lock.json, lockfileVersion: 1 -> 2

Snapshot

[coveralls]

Pull Request Test Coverage Report for Build 955810650

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.09%) to 87.107%

---

Totals
Change from base Build 943499647:	0.09%
Covered Lines:	950
Relevant Lines:	1076

---

💛 - Coveralls

[MrOrz]

Thanks a million on the fix!

I wonder why package-lock.json would change in the PR, it seems that we did not change package.json. Suggest exclude that from the PR and we are good to go!

[tw0517tw]

https://github.blog/2021-02-02-npm-7-is-now-generally-available/#changes-to-the-lockfile

npm changes its lockfile version after v7. If you use npm@7 to run npm install you'll get a version change in your lockfile unless you run npm install --no-save.

[nonumpa]

Thanks a million on the fix!

I wonder why package-lock.json would change in the PR, it seems that we did not change package.json. Suggest exclude that from the PR and we are good to go!

I just switched to master from a old branch and ran npm i. I thought it would have dependency error if I don't commit the change. (seems not)

[MrOrz]

Thanks! Let's ship it

[MrOrz]

Seems that we are also changing lockVersion to 2 in this PR. After its merge we should have a stable lockfile. have already changed lockfileVersion to 2 in a previously merged PR.

[nonumpa]

Sorry, my lockfileVersion was from 2 to 1. It seems that running npm install through npm@6 (my local version) will change lockfileVersion back to 1.