Update dependencies, make TypeScript a peer dependency #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to get things moving and learn my way around being a new maintainer, I'm updating the dependencies to bring us back to the present and solve an issue that's been bugging me personally 🚀
Includes changes:
ts-jest
at version 24 supplies a preset for Jest 24s newpreset
option, documentationtestRegex
configuration to only pay attention to*.ts
files for tests, it was running bothjs
andts
files before.>= 2.2.2
a peer dependency which should close out Typescript needs to be a peer dependency #112 and make the plugin a little more flexible for folks on newer versionsThe builds only fail on node 9 as a newer package depends on LTS releases only, should we update the travis pipelines to test only LTS as well? Especially considering GCP and AWS support only LTS releases AFAIK.