Open greenkeeper[bot] opened 7 years ago
After pinning to 2.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 6 commits.
8b02b15
Prepare 2.3.2 release
1b33393
Added speculative test of allowJsImportTypes scenario (should initially fail until fix is applied) (#590)
beaa2b2
Update CHANGELOG.md
cdfb969
Update CHANGELOG.md
c3cea1c
strict null fork (#589)
1c1056f
Update webpack.config.js
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 7 commits.
ab3d571
Prepare 2.3.3 release
69072ad
Fix findConfigFile in Windows (#605)
f55d4df
Update CHANGELOG.md
ac9ae06
Add documentation #599 #600 (#601)
8763b64
fix(tsconfig): stop pass rootDir option to TypeScript compiler.transpileModule (#598)
8c217f6
Update CHANGELOG.md
ce64afe
Update CHANGELOG.md
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
configFile
option - thanks @Loilo!Your tests are still failing with this version. Compare the changes 🚨
basePath
configurable (#618) - thanks @Loilo!The new version differs by 10 commits.
9349914
Added 2.5.2 to test matrix
adf0b19
Prepare for 2.3.5 release
caaeda9
Update CHANGELOG.md
114e5b1
Add an additional check for js files before reusing isExternalLibaryImport (#620) (#622)
3296ef7
Make TypeScript basePath
configurable, fixes #619 (#621)
2547188
Update CHANGELOG.md
7b8eabe
Correctly resolve relative configFile paths (#618)
6704717
update happypack and thread-loader docs and examples (#615)
9161d58
Document the option (#612)
749aa38
Switch execution tests to run against ChromeHeadless (#611)
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
Version 2.3.0 of ts-loader just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As ts-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/12407121) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DxCx/rxjs-diff-operator/builds/253905094?utm_source=github_status&utm_medium=notification)Release Notes
v2.3.0Commits
The new version differs by 12 commits.
00c7ce0
Preparing 2.3.0 release
5e8971c
Update CHANGELOG.md
80e0349
add appendTsxSuffixTo option (#581)
e07cb4e
Update source map docs and examples (#582)
7b447c6
refactor: Use chalk instead of colors (#579)
282e88a
add npm badge
9645cca
Remove unnecessary awaits
5225a21
Update README.md
192cc0f
Split out dynamic import tests into different scenarios (#576)
5c91dd0
Added dynamic import execution test
aecee5e
Archive jsx comparison tests - now covered by execution tests
00af1b4
Shipped v2.2.2
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: