Open
Description
Describe the feature or problem you’d like to solve
Hi 👋 , I checked the dependencies and noticed that it's a fairly short list of direct dependencies already 💪 .
But with the introduction of the log/slog
package in the Go standard library in Go 1.21 in 2023, there's a way to do structured logging without a third party dependency, so the number of direct dependencies could be reduced even further. As long as no specific logrus
features or conveniences are required, could it make sense to migrate to slog
?
Proposed solution
Migrate from third party library github.com/sirupsen/logrus
to standard library log/slog
.
Benefit: One less direct dependency (and thus lower supply chain risk, less maintenance burden for updates, maybe quicker build times)
Additional context
- Official blog post about
log/slog
: https://go.dev/blog/slog - Package reference: https://pkg.go.dev/log/slog