-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[chore] Update to support log4js version 2. #2858
Closed
johnjbarton opened this issue
Oct 25, 2017
· 0 comments
· Fixed by karronoli/redpen#10 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed
[chore] Update to support log4js version 2. #2858
johnjbarton opened this issue
Oct 25, 2017
· 0 comments
· Fixed by karronoli/redpen#10 · May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Labels
Comments
johnjbarton
added a commit
to johnjbarton/karma
that referenced
this issue
Nov 2, 2017
Support log4js 2.x as well as 1.x for configuration. Fixes karma-runner#2858
johnjbarton
added a commit
that referenced
this issue
Nov 21, 2017
Support log4js 2.x as well as 1.x for configuration. Fixes #2858
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Works with modern "log4js"
Actual behaviour
Fails with 2.3.9 because setGlobalLogLevel is no longer part of the log4js API
Environment Details
karma.config.js
fileNot
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: