arggh

> Stack traces are normally collected if you arm() the logger only: in that case you don't have to provide them. I do call `logger.arm()`, but the scenario I'm testing...

That works, however, wouldn't it be nice, if these two were equal? ``` const normalized = window.logger.tk.computeStackTrace(e); window.logger.error(normalized.message, normalized); ``` ``` window.logger.error(e); ```

I think the doc could be improved with better structure by organizing content and providing more examples, instead of just being a long list of "random snippets of information" about...

As a sidenote, the README on npmjs appears blank: https://www.npmjs.com/package/filog

Well, if I understood correctly, here goes: Actually the second scenario in the first post ("Logging the error objects") is perfectly valid according to the current documentation for `log` method...

I made a reproduction: https://github.com/arggh/filog-router-issue

Some kind of aggregation on the client side, combined with server ride rate limiting would be interesting. Maybe FiLog could have two endpoints, one rate limited for the current logs,...

> ...but I could not figure how to get a browser connected to one Meteor app to connect to Meteor on a separate Meteor server for a logging service instead...

Got confused about the actual reason this issue was opened. Rate limiting (AFAIK) has not yet been implemented, just a Meteor method sender, so I'm re-opening this.

VSCode's similar "Open Editors" section has a "Save all" button. It's a lifesaver, especially with projects where multiple files saved in sequence trigger rebuilds and rebuild-cancellations, or in the worst...