-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
FastifyError [Error]: logger options only accepts a configuration object. #479
Labels
Comments
This appears to be caused by the Fastify version bump, which didn't account for Fastify v5's "New logger constructor signature", which is mentioned in the migration guide. I think line 12 in app.ts should be changed as follows: const app = Fastify({
- logger,
+ loggerInstance: logger, |
matteovivona
added a commit
that referenced
this issue
Nov 27, 2024
matteovivona
added a commit
that referenced
this issue
Nov 27, 2024
fix: logger options only accepts a configuration object #479
🎉 This issue has been resolved in version 2.2.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Indeed, it works! Thanks for the very quick fix! |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug Report
After upgrading from 2.2.5 to 2.2.6, the service crashes with the error message:
We are using the ducktors/turborepo-remote-cache:2.2.6 Docker Image.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The service starts successfully as expected, just like in version 2.2.5.
Your Environment
The text was updated successfully, but these errors were encountered: