Update ts-loader to the latest version 🚀 #557
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.3.1 just got published.Update to this version instead 🚀 Release Notesv3.3.1CommitsThe new version differs by 4 commits.
See the full diff |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 3.3.0 of ts-loader was just published.
The version 3.3.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.3.0reportFilesoption - thanks @freeman!contextAsConfigBasePathwithcontextoption. 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 usingcontextAsConfigBasePath- thanks @christiantinauer!experimentalWatchApioption until it has been thoroughly tested. All being well it is likely to become the default behaviour for ts-loader in future - thanks @sheetalkamat!Commits
The new version differs by 141 commits.
6444fa4Fix up testse8a4bb0Merge pull request #688 from christiantinauer/masterc6354c1Merge branch 'master' into master3d41633Fix reportFile testsea8dfd7Merge pull request #701 from freeman/reportFiles92a73e2Merge in watch fixes27469c2Add missing comma64914e0Merge branch 'master' into reportFiles6d55769Fixed believed issue with watch implementation cc @sheetalkamat4a6b0daFix tests and place watchApi usage behind experimentalWatchApi option7add160Merge pull request #685 from sheetalkamat/builderApi3015608Merge pull request #714 from TypeStrong/feature/create_2_7_test_pack72b1648upgrade CI to run with 2.7 rc9a63c78include emit changes for 2.7 in test pack44fa12bcreate 2.7 test outputThere are 141 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴