setLevel doesn't seem to work

[jonnyreeves]

setLevel doesn't seem to work

[jonnyreeves]

What do you see when you step through the code in the debugger? Which console method is being invoked?

…

On Wed, 15 Jun 2022, 17:42 franck102, ***@***.***> wrote: 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? — Reply to this email directly, view it on GitHub <#110>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABQ36I7SHZXSQE3VBHFJRLVPIBXXANCNFSM5Y36TMSQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[franck102]

Ooops, good question, console.debug() is being invoked with the correct message, which made me realise I simply needed to adjust the displayed levels in Chrome dev tools UI :)

Sorry for the false alarm :)

[jonnyreeves]

No worries, perhaps consider raising a pull request to update the readme with this advice for future explorers?

…

On Wed, 15 Jun 2022, 19:19 franck102, ***@***.***> wrote: Ooops, good question, console.debug() is being invoked with the correct message, which made me realise I simply needed to adjust the displayed levels in Chrome dev tools UI :) Sorry for the false alarm :) — Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABQ36JN2SAYBU5FM7F7YPDVPINCJANCNFSM5Y36TMSQ> . You are receiving this because you commented.Message ID: ***@***.***>

[franck102]

No worries, perhaps consider raising a pull request to update the readme with this advice for future explorers?
…
On Wed, 15 Jun 2022, 19:19 franck102, @.> wrote: Ooops, good question, console.debug() is being invoked with the correct message, which made me realise I simply needed to adjust the displayed levels in Chrome dev tools UI :) Sorry for the false alarm :) — Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABQ36JN2SAYBU5FM7F7YPDVPINCJANCNFSM5Y36TMSQ . You are receiving this because you commented.Message ID: @.>

I can, the main confusion though came from me initially trying to use npm i js-vue-logger in my Vue (non typescript) project. I ended up uninstalling and using npm i js-logger instead.
I found the library on this page: https://openbase.com/js/js-vue-logger... and I'm still not sure what the difference is, if any, between the two packages. After that I assumed I hadn't properly installed or I wasn't properly using the library. Are those instructions correct for a Vue 3 user:

1. npm install js-logger
   Do not install js-vue-logger, it is ...?
   You can use the js-logger package both for typescript-enabled and for non-typescript projects

2. In main.js or in App.vue:

import logger from 'js-logger';
logger.useDefaults();
logger.setLevel(Logger.WARN|INFO|DEBUG...);
logger.info('Logging level set to ' + JSON.stringify(Logger.getLevel()));

[jonnyreeves]

This js-vue-logger package has no association with js-logger. I do not recommend it be used.

…

On Thu, 16 Jun 2022, 05:36 franck102, ***@***.***> wrote: No worries, perhaps consider raising a pull request to update the readme with this advice for future explorers? … <#m_2476872830761350725_> On Wed, 15 Jun 2022, 19:19 franck102, *@*.*> wrote: Ooops, good question, console.debug() is being invoked with the correct message, which made me realise I simply needed to adjust the displayed levels in Chrome dev tools UI :) Sorry for the false alarm :) — Reply to this email directly, view it on GitHub <#110 (comment) <#110 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABQ36JN2SAYBU5FM7F7YPDVPINCJANCNFSM5Y36TMSQ <https://github.com/notifications/unsubscribe-auth/AABQ36JN2SAYBU5FM7F7YPDVPINCJANCNFSM5Y36TMSQ> . You are receiving this because you commented.Message ID: @.*> I can, the main confusion though came from me initially trying to use npm i js-vue-logger in my Vue (non typescript) project. I ended up uninstalling and using npm i js-logger instead. I found the library on this page: https://openbase.com/js/js-vue-logger... and I'm still not sure what the difference is, if any, between the two packages. After that I assumed I hadn't properly installed or I wasn't properly using the library. Are those instructions correct for a Vue 3 user: 1. npm install js-logger *Do not install js-vue-logger, it is ...?* *You can use the js-logger package both for typescript-enabled and for non-typescript projects* 2. In main.js or in App.vue: import logger from 'js-logger'; logger.useDefaults(); logger.setLevel(Logger.WARN|INFO|DEBUG...); logger.info('Logging level set to ' + JSON.stringify(Logger.getLevel())); — Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABQ36NJLDFBOGC4V6KROY3VPKVMXANCNFSM5Y36TMSQ> . You are receiving this because you commented.Message ID: ***@***.***>

[franck102]

Argh, I'll blame crappy UI on openbase.com: on Chrome/MacOS if you start reading the description for js-logger then scroll slightly back up a small band shows up at the top with the essential info for js-vue-logger - as being the first / previous item in the list I assume.
Once I liked the description I took the npm command from that :)