Fix pino-pretty dependency issue with graceful fallback

[Copilot]

Fixes #10

Problem

The library was failing when pino-pretty was not available with the error:

Error: unable to determine transport target for "pino-pretty"

This occurred because the logger configuration in src/logger.ts was hardcoded to use pino-pretty as a transport in non-production environments, but pino-pretty was only listed as a devDependency. This meant:

• Users installing the package wouldn't get pino-pretty by default
• Production deployments without dev dependencies would fail if NODE_ENV wasn't set to "production"
• The library would crash at initialization instead of gracefully degrading

Solution

Modified the logger configuration to gracefully handle when pino-pretty is not available:

• Added a getTransportConfig() helper function that uses require.resolve() to check if pino-pretty is available
• Falls back to the default pino transport (JSON logging) when pino-pretty is not found
• Maintains existing behavior:
  • Pretty logging in development when pino-pretty is available
  • No transport override in production environments
  • Same log levels and configuration

Testing

Verified the fix works in all scenarios:

Without pino-pretty:

// Works correctly with JSON logging
{"level":40,"time":1755633252091,"pid":3754,"hostname":"...","name":"rivalsjs","msg":"..."}

With pino-pretty:

// Works correctly with pretty formatting
[19:53:00.409] WARN (rivalsjs/3634): `retryOnRateLimit` is not set...

This ensures the library works reliably regardless of whether users have pino-pretty installed, while still providing a better development experience when it's available.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.