chore(deps-dev): upgrade to v2 of tslib

[celluj34]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[X] Other... Please describe: depedency update

What is the current behavior?

Issue Number: #11 #15

What is the new behavior?

Use tslib v2+

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[NetanelBasal]

Thanks, but I meant to upgrade the entire lib to v12, and create a new major version.

[celluj34]

The reason I only did this much was because (somehow) in the published version of the library, tslib is the only dependency. So there isn't a need to upgrade any others.

I can upgrade the other packages too though, if you feel like it's necessary.

[NetanelBasal]

Yes, because upgrading to v2 is already a breaking change.

[shamoon]

@celluj34 / @NetanelBasal any updates on this?

[NetanelBasal]

It should be part of #18

[shaharkazaz]

Fixed by fa1e5f9, released in v2