Closed greenkeeper[bot] closed 6 years ago
Merging #262 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #262 +/- ##
=======================================
Coverage 61.77% 61.77%
=======================================
Files 16 16
Lines 259 259
Branches 52 52
=======================================
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 8b992e0...d0709d8. Read the comment docs.
Update to this version instead 🚀
reportFiles
option - thanks @freeman!contextAsConfigBasePath
with context
option. Strictly speaking a breaking change. However, given the original option was never able to fulfil its intended purpose I've decided to treat this as just a new feature; there seems no possibility that anyone can be using contextAsConfigBasePath
- thanks @christiantinauer!experimentalWatchApi
option until it has been thoroughly tested. All being well it is likely to become the default behaviour for ts-loader in future - thanks @sheetalkamat!The new version differs by 42 commits.
6444fa4
Fix up tests
e8a4bb0
Merge pull request #688 from christiantinauer/master
c6354c1
Merge branch 'master' into master
3d41633
Fix reportFile tests
ea8dfd7
Merge pull request #701 from freeman/reportFiles
92a73e2
Merge in watch fixes
27469c2
Add missing comma
64914e0
Merge branch 'master' into reportFiles
6d55769
Fixed believed issue with watch implementation cc @sheetalkamat
4a6b0da
Fix tests and place watchApi usage behind experimentalWatchApi option
7add160
Merge pull request #685 from sheetalkamat/builderApi
3015608
Merge pull request #714 from TypeStrong/feature/create_2_7_test_pack
72b1648
upgrade CI to run with 2.7 rc
9a63c78
include emit changes for 2.7 in test pack
44fa12b
create 2.7 test output
There are 42 commits in total.
See the full diff
Version 3.2.0 of ts-loader was just published.
The version 3.2.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-loader.
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
v3.2.0contextAsConfigBasePath
- thanks @christiantinauerCommits
The new version differs by 99 commits.
e5b2f51
Prepare 3.2.0 release
ba72dfc
Merge pull request #681 from christiantinauer/master
c95bdfe
Merge pull request #673 from trodrigues/master
f37e438
Update browserMocks.js
2d09770
Add description of option "contextAsConfigBasePath" to README.
02fe053
Fixed comparison test "validateLoaderOptionNames".
4c713e0
Add execution-test for option "contextAsConfigBasePath".
ebd2bb5
Add new loader option "contextAsConfigBasePath", which when set to true, parses to tsconfig file with respect to webpack context path (https://webpack.js.org/configuration/entry-context/#context) instead of the location of the config file. So all relative paths in config file are treated relative to webpack context This makes configurations possible, where the tsconfig file is located in a npm package or elsewhere in the project structure.
88809f9
Update README with explanation
5a32a07
Update example to actually include some typed code
013bac9
Merge pull request #678 from johnnyreilly/master
0951587
regenerate output for 2.6 and add 2.6 to test matrix
512c9e6
create ts 2.6 comparison-test results
4d4b8aa
upgraded to building with ts 2.6
e4cbeb8
Merge pull request #676 from gsteacy/master
There are 99 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: