adding missing optional peer deps

[john-arccos]

What did you implement:

Updated optional peer dependencies to fix warnings

Closes #XXXXX - didn't make a ticket, pretty straight forward.

This screenshot sums up the issue pretty nicely. yarn link is using my changes, yarn unlink is using the version from npm:

How did you implement it:

How can we verify it:

If you have a project that's using serverless-webpack typescript, and ts-node, you'll see this warning appear when you install it. If you use my branch instead, the warning goes away.

Todos:

• [N/A?] Write tests
• [N/A?] Write documentation
• [N/A] Fix linting errors
• Make sure code coverage hasn't dropped
• Provide verification config / commands / resources
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES
Is it a breaking change?: It shouldn't be. Added two * optional peer dependencies and optional peer @typescript@>=2.0, which was already a requirement of ts-node. I guess if they have typescript 1.X but don't have ts-node it would be breaking? Not sure how you want to classify that. Alternatively, changing it to * would mean it's definitely non-breaking.

[j0k3r]

Looks ok to me, thanks!

[vicary]

LGTM, thanks for contributing!