Skip to content

v1.1.2 - Critical Server Startup Fix

Latest
Latest

Choose a tag to compare

View all tags
@luw2007 luw2007 released this 11 Dec 16:36
· 5 commits to master since this release
v1.1.2
550eef2

🐛 Critical Bug Fix

This release fixes a critical bug where the server would not start correctly when run directly.

Fixed

  • Server startup detection: Now uses fileURLToPath() and realpathSync() for reliable module detection
  • Path handling: Correctly handles symlink paths (e.g., /tmp vs /private/tmp on macOS)
  • The server now starts properly when executed directly, while still preventing startup during test imports

Technical Details

Previous behavior (v1.1.0-v1.1.1):
The server used a simple string comparison (import.meta.url === file://${process.argv[1]}) which failed on macOS due to symlink resolution differences.

Current behavior (v1.1.2):
Uses proper path resolution with fileURLToPath() and realpathSync() to reliably detect direct execution.

Testing

All tests pass ✅ and the server now:

  • Starts correctly when run directly
  • Responds to MCP protocol messages
  • Does not start during test imports

Installation

npm install -g skim-mcp-server@1.1.2

Full Changelog: v1.1.1...v1.1.2

Assets 2
Loading