-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Resolve TypeError #2328
Resolve TypeError #2328
Conversation
Issue represented here: winstonjs#2327
Try running npm i and committing the changes to the lockfile. |
Bug Fix: FileTransportOptions type missing lazy:boolean option (winstonjs#2334)
Can anybody speak to any backward-compatibility issues that may be introduced by changing lockfile v2 to v3? |
I mean, if CI passes… |
Based on the official documentation, backward compatibility is ensured:
https://docs.npmjs.com/cli/v9/configuring-npm/package-lock-json#lockfileversion |
After a bit of research and testing, I think this issue is not related to Winston but may be related with NextJS or webpack |
@adampweb I have run into the same issue referenced above (using winston in next.js middleware). I tested |
Facing the same issue |
Colors was updated in #2353 which likely fixed this. |
Issue represented here: #2327