The version 6.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.
Release NotesType Check By Default
Many people were having issues with "fast" transpilation being the default over full project type checking like tsc. Type checking the full project upfront is slower but expected behaviour, so it's the default once again. You can still enable transpileOnly or ts-node/register/transpile-only for the faster transpiler without type checking.
Changed
Default behaviour is typeCheck == true || transpileOnly == false
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).
coveralls
commented
6 years ago
Version 6.0.0 of ts-node was just published.
The version 6.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.
Release Notes
Type Check By DefaultMany people were having issues with "fast" transpilation being the default over full project type checking like
tsc. Type checking the full project upfront is slower but expected behaviour, so it's the default once again. You can still enabletranspileOnlyorts-node/register/transpile-onlyfor the faster transpiler without type checking.Changed
typeCheck == true || transpileOnly == falseCommits
The new version differs by 10 commits.
68c130c6.0.058b243cUsestrictintsconfig.jsonaa9052dAddtranspileOnlyflag, default totypeCheckf2ede03chore(package): update @types/mocha to version 5.0.0 (#557)5ebd393Note type check features failing at runtime (#555)6ea624bAdd note to README about watching (#408)c882abbAdd instructions for VS Code (#554)47efa34chore(package): update package-lock.json (#551)97fb330chore(package): update proxyquire to version 2.0.0 (#547)a953579Update README screenshotSee 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: