Skip to content
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

Open
greenkeeper bot opened this issue Jun 28, 2017 · 8 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jun 28, 2017

Version 3.2.0 of awesome-typescript-loader just got published.

Branch Build failing 🚨
Dependency awesome-typescript-loader
Current Version 3.1.3
Type devDependency

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
  • bitHound - Dependencies null Details
  • bitHound - Code null Details
  • dependency-ci Dependencies checked Details
  • semaphoreci The build failed on Semaphore. Details

Release Notes v3.2.0

Fixed:

  1. #448
  2. #422
  3. minimatch replaced with micromatch
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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jun 28, 2017

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.

@greenkeeper
Copy link
Author

greenkeeper bot commented Jun 28, 2017

Version 3.2.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

  • c3a0167 chore(release): 3.2.1
  • 589683f fix: speedup caching by pre-hashing cacheIdentifier

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 26, 2017

Version 3.2.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

  • 5304203 chore(release): 3.2.2
  • 9473d2c fix(dependencies): upgrading node dependencies (#472)

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Aug 14, 2017

Version 3.2.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 8 commits.

  • 6e420c8 chore(release): 3.2.3
  • fce79fb Merge branch 'master' of github.com:s-panferov/awesome-typescript-loader
  • 90022ae fix: delay sending diagnotics request
  • 5c7b0de fix(checker): pass through execArgv to checker child process (#479)
  • b109ee4 Update README.md (#467)
  • 8ffacb0 docs(README): fix small inconsistency (#470)
  • 0c6c905 Update README.md (#471)
  • 8a947ed fix / clarify several lines in README (#475)

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 1, 2017

Version 3.3.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v3.3.0
  • Add errorsAsWarnings option.
  • Add forceIsolatedModules option.
  • Write some docs about performance issues.
  • use enhancedResolve to resolve babel-core
  • performance issue on case-insensitive file systems #507
Commits

The new version differs by 9 commits.

  • e926dbe chore(release): 3.3.0
  • 3d68c74 style: lint issue
  • bc9b544 feat: add errorsAsWarnings option
  • 2975dec docs: more about performance issues
  • 7f74bba feat: add forceIsolatedModules
  • 83e0e83 docs: add a note about performance
  • 9f7e978 fix: use enhancedResolve to resolve babel-core
  • cda6cb2 docs: add info about .babelrc, fixes #510
  • fc04d29 fix: performance issue on case-insensitive file systems #507

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 18, 2017

Version 3.4.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes Performance release

Fixes several big performance problems, info can be found in #517

Commits

The new version differs by 7 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 1, 2017

Version 3.4.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 5 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 24, 2018

Version 3.5.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 7 commits.

  • 9bbc065 chore(release): 3.5.0
  • c966685 refactor: update some deps
  • ad7cfad feat: allow setting getCustomTransformers as a path to a module (#531)
  • edc8ed9 Use Error for emitted warn (#532)
  • b9f17f3 Update README.md (#535)
  • d4e7398 cleanup dependencies (#536)
  • bec43a0 fix TSC compatible issues that prevent compilation (#537)

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

0 participants