Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we deprecate this package? #65

Open
H4ad opened this issue Jan 18, 2025 · 2 comments
Open

Should we deprecate this package? #65

H4ad opened this issue Jan 18, 2025 · 2 comments

Comments

@H4ad
Copy link

H4ad commented Jan 18, 2025

Hey, I'm started working again in the nodejs logging proposal, and since we merged nodejs/node#53239, should we deprecate this package? Or at least, by default use the built-in version in Node.js when available, and fallback to this version when not available?

Let me know what do you think

@mcollina
Copy link
Owner

I'll happily deprecate this once I stop supporting some old version of pino that runs on Node.js versions that will never receive that.

As for pino, we should start migrating it on newer node versions.

We should schedule a call on the log work soon.

@H4ad
Copy link
Author

H4ad commented Jan 18, 2025

I can create a PR to use the built-in version when is available.

Once you deprecate the older versions of node for this package, then we can deprecate this package and make it just an alias for the built-in version, what do you think?

We should schedule a call on the log work soon.

Sure! You have me on Twitter (x), feel free to ping me there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants