The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ts-node.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 99.885% when pulling c26054ff92f8a0aa2f14e98ebcc0752513c01566 on greenkeeper/ts-node-5.0.0 into e9df481f8283b53afc7d315ed49243af19666995 on master.
Coverage remained the same at 99.885% when pulling c26054ff92f8a0aa2f14e98ebcc0752513c01566 on greenkeeper/ts-node-5.0.0 into e9df481f8283b53afc7d315ed49243af19666995 on master.
Coverage remained the same at 99.885% when pulling b37448dd28a951ff32df7bd70dab57d85aec69d3 on greenkeeper/ts-node-5.0.0 into e9df481f8283b53afc7d315ed49243af19666995 on master.
Version 5.0.0 of ts-node was just published.
The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ts-node.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 32 commits.
68f8220
5.0.0
7164ab7
Remove process spawn, old TypeScript versions (#536)
d5a941c
4.1.0
89d62aa
Disable detached sub-process on Windows (#489)
129153f
4.0.2
f04c5f7
Move
@types
to dev dependencies (#484)3eefb00
Add
--trace-warnings
flag (#488)1541dfe
4.0.1
c6a70f9
Include
register/
directory in published package94cba9c
4.0.0
be7895c
Forward signals correctly (#419)
85c139a
Remove forced exit on inline evals (#477)
d4a1c94
Improve performance on large projects (#461)
c57ded2
Fix
-n
reference in READMEe7591c7
Update README with docs on
--no-
prefixesThere are 32 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: