Fix Winston logs after esbuild

[hexawulf]

Summary

• preserve logger.ts side effects with sideEffects
• add Winston file transport fallback and error handling
• compile winston-test file with server build
• expose test:logger script
• document logger test instructions

Testing

• npm run build (fails: vite not found)
• npm run test:logger (fails: module not found because build failed)

---

https://chatgpt.com/codex/tasks/task_e_6858d9dc10848322bcf42da03cafb693

Summary by CodeRabbit

• New Features

  • Added a quick logger test script to verify file logging in the production build.

• Documentation

  • Updated the README with instructions for running the logger test and verifying log file creation.

• Bug Fixes

  • Improved error handling for logger file transport failures, with fallback logging and error messages.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The updates introduce a new logger test workflow by modifying the build process to bundle an additional test script, updating documentation with instructions for verifying Winston file logging, and enhancing error handling in the logger implementation. No changes were made to exported APIs or public interfaces.

Changes

File(s)	Summary
README.md	Added instructions for running a logger test after building, describing how to verify log file creation.
package.json	Modified build script to bundle server/winston-test.ts; added test:logger script for logger testing.
server/logger.ts	Refactored file transport creation; added error event listener and fallback logging on transport errors.
server/winston-test.ts	Updated file header comment to reflect correct file extension.

Poem

In the warren, logs now gleam,
With scripts and builds—a bunny’s dream!
Should errors hop, they’re caught with care,
And fallback logs are always there.
So run the test, let Winston sing,
For every log, a joyful spring!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4fc201d and 92b1ce6.

📒 Files selected for processing (4)

• README.md (1 hunks)
• package.json (1 hunks)
• server/logger.ts (2 hunks)
• server/winston-test.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.