Component Name/ Function in LWC Log Entry are null.

[robferro]

Hello!

I'm testing out the unmanaged package and noticed that when an LWC logs an entry, the Component Name and Function are null. I can find the LWC name buried in the stack trace, but I was wondering if there was a way to populate these fields?

I'm using the import { createLogger } from 'c/logger'; method and below is the snippet that creates the log:

this.logger.error(errMessage); this.logger.saveLog().then(() => { console.log('done with async save'); });

[robferro]

I tried using this method based on the recipe:

const entry = this.logger.error(this.message).setError(someError).addTag('lwc logging demo');

But anytime I add the setError method, the dev console throws an error:

[robferro]

@jongpie No dice on that setting unfortunately. I copied the exact same code from the connectedCallback function in your demo. And I see the below log entry:

This is the code:

import { LightningElement, api } from 'lwc';
import { createRecord } from "lightning/uiRecordApi";
import { ShowToastEvent } from "lightning/platformShowToastEvent";

import ACCOUNT_OBJECT from "@salesforce/schema/Account";
import NAME_FIELD from "@salesforce/schema/Account.Name";

import { createLogger } from 'c/logger';

export default class TestLWC extends LightningElement {
    @api
    logger;

    name = "";

    async connectedCallback() {
      this.logger = await createLogger();
      try {
        this.logger.error('test error entry');
        this.logger.warn('test warn entry');
        this.logger.info('test info entry');
        this.logger.debug('test debug entry');
        this.logger.fine('test fine entry');
        this.logger.finer('test finer entry');
        this.logger.finest('test finest entry');
        throw new Error('A bad thing happened here');
    } catch (error) {
        this.logger.error('>>> connectedCallback error: ' + error.message).setError(error);
        this.logger.saveLog().then(() => {
            console.log('done with async save');
        });
    }
    }

[robferro]

I noticed that I can see the component name in the stack trace. Is there something strange in there that could be messing up the logic to extract the component name?

[jongpie]

@robferro there is definitely something strange in the stack trace that you're seeing - although it has the component name, it seems to be missing the function name, which is causing problems with parsing the data. When testing this in my own scratch orgs, the stack traces have a line that contain the function name and the component name, like:

// Component name: c/loggerLWCDemo, function name: renderedCallback
renderedCallback@modules/c/loggerLWCDemo.js:225:26

// Component name: c/loggerLWCDemo, function name: logInfoExample
logInfoExample@modules/c/loggerLWCDemo.js:3:5759

These lines (example shown in the screenshot below) are parsed to determine the component name & function - but since the stack traces in your org don't seem to have the same format, Nebula Logger isn't able to parse the data. Looking at the stack trace you provided, it doesn't seem to contain the function name anywhere, so I'm not sure how to resolve this problem.

[robferro]

I'm not sure either... We'll see if we can find a pattern for the root cause once we go live with the framework. Thanks for taking a look!

[jongpie]

That sounds great, thanks @robferro. My guess is it's still somehow related to an org setting somewhere under Setup (even though those 2 session settings didn't seem to explain it). If you find any pattern in your orgs, or notice a difference in the format of the stack traces, let me know. I'll also try to continue to reproduce the issue on my side.