Closed greenkeeper[bot] closed 6 years ago
Merging #104 into develop will increase coverage by
0.49%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## develop #104 +/- ##
===========================================
+ Coverage 87.59% 88.08% +0.49%
===========================================
Files 34 34
Lines 403 403
Branches 11 11
===========================================
+ Hits 353 355 +2
+ Misses 46 45 -1
+ Partials 4 3 -1
Impacted Files | Coverage Δ | |
---|---|---|
...nents/progress-sample/progress-sample.component.ts | 100% <0%> (+6.66%) |
:arrow_up: |
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 a90271f...d6673c2. Read the comment docs.
Update to this version instead 🚀
Fixed
register/
directory to packageUpdate to this version instead 🚀
Changed
@types
deps to dev depsUpdate to this version instead 🚀
Changed
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 4.0.0 of ts-node was just published.
The version 4.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
"Fast" By DefaultChanged
--fast
is the default behaviour now, use--type-check
for type checking behaviourAdded
@types
packagesFixed
Commits
The new version differs by 25 commits.
94cba9c
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-
prefixese8bdbed
Stricter
undefined
checks for optionsce1eceb
Update
chalk
and related typesd02f8f1
Check
options.project == null
instead of falsy1d630f9
chore(package): update tslint-config-standard to version 7.0.0 (#454)
88e9a9d
Update mocha docs in README (#446)
3718bf1
Update
chalk
imports (#451)6dd8867
chore(package): update react to version 16.0.0 (#435)
a62b3b6
chore(package): update mocha to version 4.0.0 (#438)
c01709c
fix(package): update source-map-support to version 0.5.0 (#439)
There are 25 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: