Closed greenkeeper[bot] closed 6 years ago
Merging #313 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #313 +/- ##
=======================================
Coverage 61.77% 61.77%
=======================================
Files 16 16
Lines 259 259
Branches 54 54
=======================================
Hits 160 160
Misses 99 99
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 f9a6148...85bf801. Read the comment docs.
Update to this version instead ๐
Changed
-T
short flag for transpile only modeUpdate to this version instead ๐
Fixed
Update to this version instead ๐
Fixed
Script#runInThisContext
via REPL to ensure objects all exist in the same contextUpdate to this version instead ๐
Fixed
Buffer.from
instead of deprecated new Buffer
Update to this version instead ๐
Fixed
normalize
for Windows to workUpdate to this version instead ๐
Changed
declarationMap
option from input configuration under ts-node
Update to this version instead ๐
Fixed
emitDeclarationOnly
from configuration to ensure config is validUpdate to this version instead ๐
Fixed
buffer-from
module for old-node.js compatibilityAdded
Update to this version instead ๐
Added
--files
) can be used to disable loading files from tsconfig.json
by defaultUpdate to this version instead ๐
Changed
tsconfig.json
files by default to speed up startup
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 enabletranspileOnly
orts-node/register/transpile-only
for the faster transpiler without type checking.Changed
typeCheck == true || transpileOnly == false
Commits
The new version differs by 46 commits.
68c130c
6.0.0
58b243c
Use
strict
intsconfig.json
aa9052d
Add
transpileOnly
flag, default totypeCheck
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
ab7dd0f
5.0.1
0c7fa0d
Ignore
rootDir
errors (#544)10af1c5
Vague README improvements
fd1985d
Fix incorrect environment variables in docs (#538)
68f8220
5.0.0
There are 46 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: