Raees Iqbal

bump... This is not working in HHVM 3.12.1. @RickySu Can you please take a look?

I'd like to mention here that this is the exact functionality I was looking for. So, it's a feature for me. I do agree that this should be more explicit...

This functionality was initially implemented in https://github.com/netlify/cli/pull/762 but later reverted because of NodeJS compatibility issues. I'm think maybe we can precompile incompatible code and include that. Opening again to investigate...

It seems like the redirect rules from `netlify.toml` are not being picked up. I've raised this issue internally but in the meantime you can use a [`_redirects` file ](https://docs.netlify.com/routing/redirects/redirect-options/#splats) to...

@fool Can you please shed some light on this. I can reproduce this locally, even after I manually copied `netlify.toml` to publish directory and then make a deployment, the redirect...

Fluentd uses the following format for it's log: ``` { "time" : "2017-07-27", "level":"info", "message":"fluentd worker is now running worker=0", "worker_id":0 } ``` The `level` can be one of: `fatal`,...

As for the implementation, we can either hijack the global `console` variable, e.g. ```js console.log = (...args) => { /* our logic */ } ``` Or we can provide our...

Since we want to capture all logs even if they're not using structured logging methods we provide, we can do a hybrid approach. Provide a `logger` class that plugin authors...

Yes, we can add that warning to the logs but I still think that we should capture the logs from `stdout` and `stderr` (`console.log` and `console.error`) because when something breaks,...

I say that we do distinguish between the two types. And if we go that route, it requires that the plugin authors use our logger library. The logs from our...