-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of awesome-typescript-loader is breaking the build 🚨 #158
Comments
After pinning to 3.1.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 3.2.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 3.2.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 3.2.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits.
See the full diff |
Version 3.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv3.3.0
CommitsThe new version differs by 9 commits.
See the full diff |
Version 3.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesPerformance releaseFixes several big performance problems, info can be found in #517 |
Version 3.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 3.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Version 3.2.0 of awesome-typescript-loader just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As awesome-typescript-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 💪
Status Details
Release Notes
v3.2.0Fixed:
minimatch
replaced withmicromatch
Commits
The new version differs by 13 commits.
02cfb80
chore(release): 3.2.0
3d8f91a
fix: don't kill the loader when compilation.bail = true (#448)
c073af1
fix: environment cache invalidation (#449)
f14eaab
fix(paths-plugin): properly skip .d.ts files
60ffa3c
refactor: use micromatch, update deps
8c4f7c6
docs(README): fix default value
b263879
chore(release): 3.2.0-rc.0
a15de0a
feat: case errors, silent, diagnostics, paths-plugin fixes (#446)
c05e296
Merge pull request #442 from LayfonWeller/patch-1
2ddc46e
Added context in the loader interface
ae3961f
Update instance.ts
f754bc1
Corrected if no context is passed...
0e8abd6
Change the context to webpack provided one
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: