The js-logger's discuss from jonnyreeves

Messages Threshold

Hi,

Is there any Threshold method in js-logger? or an event that tells me this is the last message or something?

I want to set the handler to send messages to a WS endpoint, but not in every message I have, I want to more that more optimized so I thought about a threshold, something like threshold=5 so after the 5th message I send the array of messages to the server then reset the array...

Thanks.

setLevel(String)

I'm trying to set the log level based on configuration coming from the backend. The backend value is a String: debug, info, warn, error, OFF.
setLevel(String) isn't supported. Am I missing something obvious? Any alternative suggestions?

I suppose I could switch based on the config value and call the corresponding setValue(Level) call.

Uncaught TypeError: Cannot read properties of undefined (reading 'Logger')

Uncaught TypeError: Cannot read properties of undefined (reading 'Logger')
    at logger.min.js:1:2713
    at logger.min.js:1:2789

How I'm using it:

In my js file, I have import * as Logger from './logger.min.js'; Logger.useDefaults();
Then, I call Logger.info("test123").

What could I be doing wrong?

Feature Request - Logger.getLevel

Hi,

it would be nice if there was a method that returns the current level of the logger.

This would allow to change temporarily the level and then get back to a previous value.

For example :

let level = Logger.getLevel()
Logger.setLevel(Logger.OFF)
//do stuff you don't want to log
Logger.setLevel(level) //get back to the previous level

I have added this functionnality (see my pull request)

Ben

Debug Level Not Showing Up

Hi, I tried many things but DEBUG level is not shown for some reason. My configuration:

//Logger.useDefaults();
Logger.useDefaults({
    defaultLevel: Logger.DEBUG,
    formatter: function (messages, context) {
        messages.unshift(new Date().toUTCString())
    }
});

Logger.setLevel(Logger.DEBUG);

// Only log WARN and ERROR messages.
//Logger.setLevel(Logger.WARN);
//Logger.debug("Donut machine is out of pink ones");  // Not a peep.
//Logger.warn("Asteroid detected!");  // Logs "Asteroid detected!", best do something about that!

// Ah, you know what, I'm sick of all these messages.
// But I want to see them again later
//var oldLevel = Logger.getLevel();
//Logger.setLevel(Logger.OFF);
//Logger.error("Hull breach on decks 5 through to 41!");  // ...

// Actually, maybe those logs were quite useful...
//Logger.setLevel(oldLevel);

Logger.debug("I'm a debug message!");
Logger.info("OMG! Check this window out!", window);
Logger.warn("Purple Alert! Purple Alert!");
Logger.error("HOLY SHI... no carrier.");

Logger.debug("XXXXXXXX");
Logger.debug("YYYYYYYY");

// Start timing something
Logger.time('self destruct sequence');

// ... Some time passes ...

// Stop timing something.
Logger.timeEnd('self destruct sequence'); // logs: 'self destruct sequence: XXXms'.

setLevel(Logger.OFF) not working

I have the following but the log still get printed out:

var logger = Logger.get('BaseComponent');
Logger.get('BaseComponent').setLevel(Logger.OFF);
logger.setLevel(Logger.OFF);

Refused to execute script ... MIME type

Getting this when adding script tag to my html:

Refused to execute script from 'https://raw.github.com/jonnyreeves/js-logger/master/src/logger.min.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

Request for tables

Could it be possible to integrate tables into the project? It'd be nice to look at some of my reference data in a well presented way.

Logger.debug output

Chrome (I'm on v.54) have some usefull filters (log, info, debug...)
Logger.log() output in log filter
but Logger.debug() don't output in debug filter

Declaration file not recognized by typescript compiler

I'm using typescript 2.3.4. When I declare a triple-slash directive pointing to logger.d.ts:

/// <reference path="../node_modules/js-logger/src/logger.d.ts" />

and write Logger in my source file, the compiler doesn't recognize it and throws the following error:

error TS2304: Cannot find name 'Logger'.

logger.debug('...') calls don't work when level is set to logger.DEBUG

logger.debug('...') calls are NOT printed when level is set to logger.DEBUG when using v1.4.1.
logger.info('...') and above are printed.
With v1.3.0 it works fine.

This is the basic functionality of a logger, if this doesn't work than it's pretty much useless :P

For the project where I'm using it I'm writing my code in TypeScript and compiling it with latest version of webpack, it might be relevant.
Will be using v1.3.0 until this issue is resolved.

Thanks!

Support non-standard console methods

I would like to use js-logger with console.group. I know it's not standard, but I don't see why js-logger couldn't implement all console methods available in the current environment.

npm package 1.4.1 has different code from github

Hello,
I've noticed that the js-logger source code get by npm install js-logger has different code from the githoub. The nuget package and the github have the same version 1.4.1. Calling the Logger.trace("Some log") cause error because this function not exists in npm package.

Regards

Add 'enabledFor' method into ILogger interface in d.ts

No DEMO link in readme

the readme is missing one of the most important thing - it doesnt contain demo.

for example, the BlackBird.js demo - http://demo.jb51.net/js/Blackbird/index.html

see how well it demonstrates the behavior.

A possible typo in README

It seems there is a typo in Log Handler Functions section of README.md:

You can configure the handler function via Logger.setHandler nothing that the supplied function expects two arguments

Question : stack trace

When using default console, we can see where in our code there is this log (error whatever)
but since this plugin use Function.prototype.apply.call(hdlr, console, messages);
all logs are from logger.js:181

So, is there a way to see where is our log from ?

about Logger.debug

newer chrome do not support console.debug.

Create a method for setHandler and useDefaults

I'm using this to log on the server and client and need to duplicate a bit of the useDefaults function in a setHandler function (to send back to the browser console). It would be nice if this was doable from the library itself.

line number

How to show the correct line number?

Migrate away from gulp

Let's remote a dependency by moving the build system to use npm scripts.

Logging into plain text files

Hi,
I was wondering if this library provides logging data into plain text files instead of the regular web console.

The idea is that if we could log onto separate files, we could have a look at them at our own leisure, let alone send them over to someone for debugging.

I was expecting something like -
var myLogger = new Logger('/path/to/txt/file/where/data/will/be/logged')

As per the above line, all logs will be saved onto that file. If the file doesn't already exist, a new file will be created.

Thanks in advance,
Ashish Deshpande

createDefaultHandler has no .ts reference

How to use with require or import?

Can you add to the README how to use the Logger without adding a <script> tag in the HTML but rather using it as a module with require or import statements?
So it isn't added to the global namespace.

Mention babel-plugin-js-logger in README.md

Hi,

hope you like the following nice babel plugin:

https://www.npmjs.com/package/babel-plugin-js-logger
https://github.com/core-process/babel-plugin-js-logger

Would you like to add a reference to your README.md?

Thanks!

Niklas

no line number output in log message

It would be nice to support line numbers in the debug-panel.
The native window.console shows line numbers and are clickable to the destination.

getLevel in docs but not in release

Methods like getLevel are in the documentation but not in the current release.
Could you please do a release?

Request for giving access to time variable in Logger.timeEnd()

I am currently using

logger.time('Powers Fetched');
setTimeout(() => {
    ...
    logger.timeEnd('Powers Fetched');
}, 1500);

but it gives me ugly decimal numbers like 1514.76513671875ms

My proposal is to give us access to the time variable, maybe as a callback as second paramter or an optional config object, so we can set the decimal points, change unit, etc. If something like this already exists, please shed some light on it.

setLevel doesn't seem to work

This code in a Vue 3 store (using webpack, not using typescript):

  import jsLogger from 'js-logger';

  const log = jsLogger.get('SettingsStore');
  log.info('Named Settings logger level set to ' + JSON.stringify(log.getLevel()));
  log.info('Debug enabled: ' + log.enabledFor(jsLogger.DEBUG));
  log.debug('Test debug message');

doesn't log the last message:

[SettingsStore] Named Settings logger level set to {"value":1,"name":"TRACE"}
[SettingsStore] Debug enabled: true

I am new to ES6 & mocules, I must be missing something obvious??

Changing the last line to log.info outputs the message... what am I missing?

This is what I have in package.json:

"js-logger": "^1.6.1",

Inconsistent string interpolation

I'm sure this is likely an issue with the way I've set things up (latest node, bable, webpack, ) but I cannot get string interpolation to work when using Logger.get. ex:

import Logger from 'js-logger'

Logger.useDefaults()
Logger.warn('TEST')
Logger.warn('TEST %sPOLATED', 'INTER')
const log = Logger.get('Log')
log.warn('Test')
log.warn('TEST %sPOLATED', 'INTER')

Will output:

TEST
TEST INTERPOLATED
[Log] Test
[Log] TEST %sPOLATED INTER

So what am I not understanding here?

In addition, if I do not use Logger.useDefaults(), for example by replacing that line with Logger.setLevel(Logger.INFO), I won't see any logs at all. Any thoughts as to why this occurs?

How do I extend the logger?

By default, Logger.get() returns ILogger which is only good for calling the particular logging methods. As far as I found, I can't even set some additional values to the context.

What is the proper "entry point" if I want to extend js-logger, like adding additional error levels, logging methods for the new levels, wrapping or overriding the base methods, while having it (hopefully) strongly typed?

The 1.5.0 version does not work with typescript 3.1.3 (EDIT 1.4.1 works)

The 1.5.0 and 1.4.1 version does not work with typescript 3.1.3. I have not tested other versions. Here is the error message I get.

...../node_modules/js-logger/src/logger.d.ts
(112,1): An export assignment cannot be used in a module with other exported elements.

log levels

Hi i just checked the code and i like the logger :)

My question is: would it be more common to use the standard log levels like BSD syslog levels?

There is a rfc: https://tools.ietf.org/html/rfc3164#section-4.1.2 (Page 8, last lines) Log level 0 - 7 for the severity.

           0       Emergency: system is unusable
           1       Alert: action must be taken immediately
           2       Critical: critical conditions
           3       Error: error conditions
           4       Warning: warning conditions
           5       Notice: normal but significant condition
           6       Informational: informational messages
           7       Debug: debug-level messages

If you agree i can fork it if you like and send a pull request.

Kind regards

yarn?

>yarn add js-Logger

yarn add v1.22.4
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/js-Logger: Not found".

When logging the line number comes from the logger instead the file where the logger is used

I 'm using the js-logger in my project, but as you can see in the below logging records , the line number is referring to a line number in the logger.js file .

how can I get the line number of the file where the logging is enabled?

`
DEBUG-Wed, 02 Oct 2019 09:19:46 GMT Desk polling done at Wednesday, October 2nd 2019, 11:19:46 am logger.js:188

DEBUG-Wed, 02 Oct 2019 09:19:49 GMT Desk polling done at Wednesday, October 2nd 2019, 11:19:49 am logger.js:188 `

How to remove stacktrace from trace logs?

I like 3 levels of logging. Info for general information. Debug for more debug items. And trace for a lot of logs like all streaming messages. In js-logger, the Logger.trace also logs a stacktrace. This is too much information and I don't need it specifically.

Can you disable the stacktrace logging in Logger.trace?

Fails in Node (window is not defined)

var Logger = require('js-logger');

....
}(window));
  ^
ReferenceError: window is not defined

I fail to see the point in releasing a Node package that does not run on Node.

Request for api to set log-level of the Profile calls

Currently, they appear to be pumping out on the INFO level by default.

Make Logger object immutable

Calls like Logger.WARN = null should be forbidden. How about using Object.freeze?

logLevel typo in README.md

README suggests this:

Logger.useDefaults({
    logLevel: Logger.WARN,
    formatter: function (messages, context) {
        messages.unshift('[MyApp]');
        if (context.name) messages.unshift('[' + context.name + ']');
    }
})

However logLevel property should be defaultLevel according to the code.

Add Support for Cascading LogLevel Configuration

JSLogger should cascade the LogLevel configuration for named loggers based on their namespace, so for example:

var loggerA = Logger.get("parentNS.clientA");

// Configure the LogLevel of the parent namespace
Logger.get("parentNS").setLevel(Logger.WARN);

loggerA.info("Info Message"); // No output
loggerA.warn("Warning Message"): // Logs "Warning Message"

This feature would provide developers a way to express log levels for an entire group of clients without having to manually list them all out.

Log Handler for Splunk

Splunk Http Event Logging requests authentication to be sent during POST request via headers.

Something likes:
"headers": {"authorization": "Splunk {token}"

How can this be done using js-logger?

Formatting example breaks console substition

  formatter: function (messages, context) {
    // prefix each log message with a timestamp.
    messages.unshift(new Date().toUTCString());
  },
});

will break: logger.log('Hello %s', 'Jonny')

Logger.setHandler improvement

Hi!

var myHandler = function(messages, context){
//send log to server e.t.c
}
Logger.setHandler(function (messages, context) {
    myHandler(messages, context);
    //And now i want to define parent handler implementation. How can I do it?
});

export ILogger interface

Hello,

we are using your component and find it a very handy component. But we use VueJS in combination of typescript. And it is a petty that you do not export the ILogger interface in your logger.d.ts

Now we use a any object, and it would be nice to have the ilogger interface available for better typescript.

Thanks

Add missing TRACE debug level in ts definitions

Pretty self explanatory

Support console colors

Chrome and Firefox both support colors in console. For example:

console.log('%c console colors', 'background: black; color: yellow');

js-logger should be able to pass this through to the underlying console implementation (as they are just additional parameters).

Please packed a esm version, standalone file.

Logger.log() actually print log at INFO level

It should print LOG level instead - triggering console.log()

jonnyreeves / js-logger Goto Github PK

js-logger's Issues

Recommend Projects

Recommend Topics

Recommend Org