docs(infinite-scroll): use proper equality check

[matzar]

Changed '==' to '===' in infinite-scroll readme.

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Updated documentation so people don't get scared when seeing '==' equality.

Issue Number: #

What is the new behavior?

Changed '==' to '===' in infinite-scroll Usage code example.

Does this introduce a breaking change?

• Yes
• No

Other information

[sean-perkins]

There are 5 occurrences of this issue in this file. Can you please update all of them at once? Thanks!

[matzar]

Double checked everything - 5 occurences of double-equals have been replaced with tripple-equals.

[averyjohnston]

Thanks for the PR! The readme file you've updated is mostly auto-generated (everything below the <!-- Auto Generated Below --> comment) and will be overwritten when build is run. The source files for the usage examples are under infinite-scroll/usage. Could you update those instead, and then run npm run build to propagate the changes to the auto-generated files (and commit those updates as well)?

[averyjohnston]

Thanks! This LGTM once tests pass and Sean has a chance to take another look.

[liamdebeasi]

Can we remove the package-lock changes?

[matzar]

Can we remove the package-lock changes?

Now I've commited only infinite-scroll/usage changes and built readme. No package-lock.jsons or api.txt.