Evgeniy Pavlov
Evgeniy Pavlov
In the next release there will be dynamic atlases and the problem will be solved.
Thank you, I will add this in the next release. Travis was executed with an error, I can not merge it.
then the error will be here https://github.com/kutuluk/loglevel-plugin-remote/blob/master/src/remote.js#L277
```js const win = window; if (!win) { throw new Error('Plugin for browser usage only'); } ``` https://github.com/kutuluk/loglevel-plugin-remote/blob/master/src/remote.js#L1-L5 Error in error code. But the result is correct - throw an...
You should not connect the plugin during ssr or connect another plugin that will write logs directly to a file on the server.
If the queue limit is reached, then the server is most likely disconnected or it does not have time to process incoming logs and an error message to send to...
You need to implement the receiving side on server.
```javascript log.warn('%o', { foo: 123 }); ``` or ```javascript log.warn('%j', { foo: 123 }); ```
In my opinion plugin API 2.0 should look like this: ```js //prefix.js function apply(loggerName, options) { return function(methodName) { return function(args) { args.unshift(methodName, options.text, loggerName); }; }; } export default...
Speaking of version 2.0, I meant completely abandoning obsolete environments. Backwards compatibility could be saved with the help of the loglevel/legasy submodule. This is a common practice. But I do...