Improve logging

[d-roak]

Currently we are using console.log and console.err for debugging. We want to create a debug mode where we can check logs, otherwise they shouldn't be displayed.

Research and implement the best approach you can find for this

[JanLewDev]

I'm on it.

[d-roak]

done at #102 , needs further investigation on how to:

• properly log nested objects without showing too much info
• implement generic logging for types that throw errors

[gregemax]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged

I have a strong background in TypeScript, specializing in creating efficient logging utilities. My experience will help implement a robust solution that enhances maintainability and debugging in our projects.

How I plan on tackling this issue

Define Debug Mode: Use an environment variable to toggle debug mode.

Create a Logger: Develop a TypeScript logger that wraps console.log and checks debug mode.

Integrate the Logger: Replace existing logging calls for consistency.

Testing: Ensure logs behave as expected in both modes.

[onlydustapp]

Hey @gregemax!
Thanks for showing interest.
We've created an application for you to contribute to Topology.
Go check it out on OnlyDust!

[d-roak]

Go ahead! Assigned

[d-roak]

Any further attempts, please check previous PRs for extra comments. One extra thing that was not mentioned in the last round of comments:

• We want to be able to setup different log levels and configs to each package. The log configs should be passed in the constructor of each package

[d-roak]

for tracking #172

[gregemax]

hey
consider a logger like winston or pino with browser-specific handling plugins for more control over object logging and nested data.

[d-roak]

hey @gregemax, are you going to continue this task or can i drop the assignment and close the pr?

[gregemax]

@d-roak
should i use winston or pino for the logger

[d-roak]

winston

[d-roak]

assigning it internally