-
Notifications
You must be signed in to change notification settings - Fork 885
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
Issue with Nullish Coalescing Operator (??) on Chrome 79 and below #1775
Comments
I don't think we have the bandwidth to do either. I think the only solution for your problem is to remove |
Chrome 79 was released in 2019 (https://cloud.google.com/blog/products/chrome-enterprise/admin-insider-whats-new-in-chrome-enterprise-release-79). Chrome's LTS version is at 102 at the time of this post (https://support.google.com/chrome/a/answer/11333726). I do not see any reason we should try and support such an old release as 79. |
Next.js supports Chrome 64+. Given that pino is recommended by Next.js, it would be beneficial for pino to also support this version. This ensures a consistent experience for developers using both tools. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hello
pino
maintainers,I've come across an issue while using the
pino
library in an environment running Chrome version 79 and below [can i use] It appears that the Nullish Coalescing Operator (??
) used in the library isn't recognized by these older versions of Chrome, leading to aSyntaxError: Unexpected token '?'
.Given the widespread usage of Chrome and potential for projects to require support for older versions, it might be worth considering either:
Steps to reproduce:
pino
library in a project with browser options.pino({ browser: { ... } })
SyntaxError
.I also tested this on Android Chrome version 78.0.3904 and observed the same issue.
Thank you for your work on this library, and I appreciate your attention to this matter.
The text was updated successfully, but these errors were encountered: