Tomas Della Vedova

Hello! You can use [`@elastic/ecs-pino-format`](https://github.com/elastic/ecs-logging-js/tree/master/loggers/pino) that will format to ECS automatically for you :) ```js const ecsFormat = require('@elastic/ecs-pino-format')() const pino = require('pino')({ ...ecsFormat }) ```

I have a similar issue when using native ESM in node v14 with `"type":"module"` and Fastify, I was able to solve it with this workaround: ```js // app.js export default...

@Ethan-Arrowood agreed! Please also add the references to the issues you are mentioning, so we have a single place where we are tracking them all. > This is a contradictory...

Hello! Why you need to access `start`? It is basically an internal API, and calling `ready` automatically calls `start` behind the scenes.

> I would prefer a minimum set of features that each framework (or combination) has to provide for the benchmarks to be meaningful. I don't think this would work, because...

> But we should be open for innovations which don't comply with the download rate. The question is, how do you define if a project is innovative or not? In...

> Remove call of ready() inside close() Why remove the `ready` call? If you have already started the app nothing will change, if the app is not yet started why...

> For me, it's wrong that close handle more than it should. If you want to bootstrap the app call start or enable autostart period. *I strongly suggest you to...

> What's your problem? Again. > Then you will mix up again two different things starting and closing. As a user, I expect that close will close my application and...

I like it! I suggest to use [node-archy](https://github.com/substack/node-archy), in `find-my-way` we are using a way to complex method :P We should think how to handle unnamed plugins.