Better console.trace

console-trace-example.js

// Using console.trace in several places when debugging can be quite the PITA because it prints the entire
// stack directly to the output and makes it difficult to find and read other log messages
//
// this variant will print a neatly collapsed object with a "stack" property that you can manually expand when needed

console.log('>>', { trace: new Error().stack?.slice(12).split('\n') });

trace.js

// attention!! redux dev tools will override console.trace themselves :)
console.trace = (...args) => {
    console.log.apply(console, [
        ...Array.from(args),
        {
            trace: new Error().stack?.slice(12).split('\n'),
        },
    ]);
};

trace.ts

// attention!! redux dev tools will override console.trace themselves :)
console.trace = (...args: any[]) => {
    console.log.apply(console, [
        ...Array.from(args),
        {
            trace: new Error().stack?.slice(12).split('\n'),
        },
    ] as any);
};