The version 3.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 tsconfig-paths.
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.
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).
Coverage remained the same at 99.891% when pulling 26123217e84e164e6d0d1a10a1c90751b1a94100 on greenkeeper/tsconfig-paths-3.0.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Coverage remained the same at 99.891% when pulling ac7e922c8a7ae528d957fe058bcd6584c4657136 on greenkeeper/tsconfig-paths-3.0.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Coverage remained the same at 99.891% when pulling ac7e922c8a7ae528d957fe058bcd6584c4657136 on greenkeeper/tsconfig-paths-3.0.0 into 6c0bacf4edc803c842c6cc54595d20c25c5c975c on master.
Version 3.0.0 of tsconfig-paths was just published.
The version 3.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 tsconfig-paths.
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 27 commits.
fb18f9d
3.0.0
0f52e6d
Update changelog for 3.0.0
69e55c6
Prepare docs for new release
440b6b6
Fix examples for api changes
e103859
Add async version of matchPath (#27)
6c50d47
Cleanup mocha opts
fdf8699
Fix code coverage
e76e946
Include all files in coverage
f1d967f
Spelling
584f381
Refactor
d831f7a
Optimize performance by sorting by longest prefix only once
726d421
Refactor json reading
f7bc219
Readonly
776e9bd
Rename file
083dd80
Simplify package reader so external programs like webpack plugin can provide it
There are 27 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: