node-ts / logger Goto Github PK

The dependency @types/jest was updated from 24.0.11 to 24.0.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/jest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency tslib was updated from 1.9.3 to 1.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tslib is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi,

I'm trying to implement the autobindLoggers functionality, but it seems the documentation on https://github.com/node-ts/logger/tree/master/packages/logger-core about this is out of date

1. the function is named autobindLoggers, instead of autobindLogger
2. I get typescript errors when I try to implement this code:

    super (bind => {

      // Creates new named loggers for all targets in the container, including the above services
      autoBindLoggers(bind)
    })
  }

Parameter 'bind' implicitly has an 'any' type, but a better type may be inferred from usage.ts(7044)
Type '(bind: any) => void' has no properties in common with type 'ContainerOptions'.ts(2559)

What ís the correct way to implement this?

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

The dependency @types/node was updated from 11.13.4 to 11.13.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The dependency ts-jest was updated from 24.0.2 to 24.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-jest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The logger factory builds a logger per IoC target, and when there are more than 10 targets then node will display the following warning:

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 31 unpipe listeners added. Use emitter.setMaxListeners() to increase limit

This is because each logger instance defines its own console transport that internally adds listeners. This is related to: winstonjs/winston#1334

That ticket "resolves" the issue by increasing the number of listeners, which just kicks the can down the road. Instead, this fix should attempt to use a singleton logger, but configured to log the target name depending on the logging source.

The dependency lerna was updated from 3.13.2 to 3.13.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lerna is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴