The version 3.0.3 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.
This fix resolves the issue for TypeScript 2.4+ (which is likely 95% of users). For those people stuck on 2.3 or below and impacted by this issue, you should be able to workaround this by setting entryFileCannotBeJs: true in your ts-loader options. This option should be considered deprecated as of this release. The option will likely disappear with the next major version of ts-loader which will drop support for TypeScript 2.3 and below, thus removing the need for this option.
Commits
The new version differs by 38 commits.
81d02dbMerge pull request #658 from johnnyreilly/master
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).
Version 3.0.3 of ts-loader was just published.
The version 3.0.3 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.0.3This fix resolves the issue for TypeScript 2.4+ (which is likely 95% of users). For those people stuck on 2.3 or below and impacted by this issue, you should be able to workaround this by setting
entryFileCannotBeJs: truein your ts-loader options. This option should be considered deprecated as of this release. The option will likely disappear with the next major version of ts-loader which will drop support for TypeScript 2.3 and below, thus removing the need for this option.Commits
The new version differs by 38 commits.
81d02dbMerge pull request #658 from johnnyreilly/master2aaba6eDeprecate entryFileCannotBeJs173bd4cChange getCurrentDirectory behaviour for TypeScript 2.3 and belowa91a8b4make nodeResolutionAllowJs run in 2.4+ onlya2b613atry strategy approach splitting 2.4 and above and 2.3 and below behavioure576c92check old strategy behaviourcb303f5drop resolveTypeReferenceDirectives for a moment9f4cc4fAdd back support for TypeScript < 2.4f832bb6Fix allowJs import @types issuea504b11added nodeResolutionAllowJs test (will fail initially)b182a65republish as 3.0.24348025Tweak docsb70d5afupdate docsb0fb7baMerge pull request #643 from johnnyreilly/master50aa9a5update to v3There are 38 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: