fix: use realpath for main module detection in service - #16
Merged
Conversation
The simple string comparison of import.meta.url vs process.argv[1] fails on macOS due to symlink resolution differences: - /tmp vs /private/tmp - /opt/homebrew/opt vs /opt/homebrew/Cellar This caused brew services to fail because launchd runs the script via the symlinked path but import.meta.url resolves to the real path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
import.meta.urlvsprocess.argv[1]fails on macOS due to symlink resolution differences (/tmpvs/private/tmp,/opt/homebrew/optvs/opt/homebrew/Cellar)This was causing launchd to start the process but immediately exit because the main module check returned false.