Closed greenkeeper[bot] closed 6 years ago
Merging #70 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #70 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 154 154
Branches 2 2
=====================================
Hits 154 154
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update bd7a75d...b845fea. Read the comment docs.
Update to this version instead 🚀
Fixed
rootDir
errorsUpdate to this version instead 🚀
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
typeCheck == true || transpileOnly == false
The new version differs by 10 commits.
68c130c
6.0.0
58b243c
Use strict
in tsconfig.json
aa9052d
Add transpileOnly
flag, default to typeCheck
f2ede03
chore(package): update @types/mocha to version 5.0.0 (#557)
5ebd393
Note type check features failing at runtime (#555)
6ea624b
Add note to README about watching (#408)
c882abb
Add instructions for VS Code (#554)
47efa34
chore(package): update package-lock.json (#551)
97fb330
chore(package): update proxyquire to version 2.0.0 (#547)
a953579
Update README screenshot
See the full diff
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 2 commits.
68f8220
5.0.0
7164ab7
Remove process spawn, old TypeScript versions (#536)
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: