fix: Activate NVM and pyenv in entrypoint to fix node PATH issue #310
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.
Fixes #294
This commit activates NVM and pyenv early in the entrypoint.sh script to ensure that node and python binaries are available in the PATH for all subsequent operations, including subprocess calls from Python scripts.
Previously, when Python scripts used subprocess.run() to call node commands, they would fail with FileNotFoundError because NVM was only sourced in bash/zsh config files, not in the subprocess environment.