Gareth Jones

Most likely is that the files are being written to a different location when running in beanstalk. Have you checked locations like `/var/log`? Alternatively, if you can ssh into the...

Looks like you're trying to use webpack to bundle up code to use in a browser, but you're also configuring a rolling file stream - file streams won't work in...

I don't think that warning would come from using a file appender, because the file appenders are listed in the core appenders - which avoids the dependency-is-an-expression problem. Could you...

Related to #575 - needs a standard way to handle appender errors.

This sounds like a duplicate of #901

I can see this being useful, so thanks for the PR. My only concern is that there could be someone out there that's logging a function somehow, and this would...

Leaving this open because it's still a good idea, but it'll need to some work to port to tap tests and allow for turning it off and on.

It's not possible at the moment, but you could implement this in a similar way to the `categoryFilter` and `logLevelFilter` appenders. They wrap around other appenders, and filter what gets...

Go for it @mattiacapitanio - just follow these [guidelines for contributing](https://log4js-node.github.io/log4js-node/contrib-guidelines.html) and you'll be fine.

The layouts that come with log4js mostly use [util.format](https://nodejs.org/api/util.html#utilformatformat-args), which in turn uses [util.inspect](https://nodejs.org/api/util.html#utilinspectobject-options) - which is where the default maximum length of an array's contents to be displayed comes...