Marc Bachmann

To be more specific for people who experience this problem: You can bypass that behavior by setting a custom default path. e.g. ```js const wayfarer = require('wayfarer') const r =...

The new `.match` method only returns a matched route, but doesn't invoke the handler. So I'd still keep the `.emit` method.

please provide more info. html & config to reproduce would be nice.

In case somebody wants to work on that, here's some example code how to merge multiple loki streams into one array of logs: https://github.com/livingdocsIO/loki-log-export/blob/3488c019d5f0c2525cdc844e02c3a1a8a7d3e8d2/merge-logs.js#L3-L13

I wrote my own script that supports custom shell scripts and therefore also signals. It uses md5-based file comparison to detect changes on files: https://hub.docker.com/r/livingdocs/file-change-hook It's not really a solution...

I'm having the same issue with systemd, but I guess in my case it's an issue with the setup. That is the error I got: ``` Aug 19 16:42:20 server...

That maybe works. https://github.com/marcbachmann/node-html-pdf/issues/36#issuecomment-110530819

In elasticsearch we're using that dynamic template: ``` [ { "text_prefix": { "match": "text_*", "mapping": { "type": "text" } } }, { "keyword_prefix": { "match": "keyword_*", "mapping": { "type": "keyword"...

Please use the function based `reply` or `replyOnce` in that case. ``` .replyOnce(async function () { return [200, await fetchGroups()] }); ```

Must be Jest specific. I have axios 1.5 working with axios-mock-adapter