Conversation
- Export format_path_env from vite_install crate - Modify auto_install to return package manager bin_prefix - Add execute_with_package_manager method to avoid building PM twice - Update PATH environment before task execution 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
dc6657b to
42e71d1
Compare
Brooooooklyn
approved these changes
Dec 23, 2025
Member
Author
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
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.

TL;DR
Updates the auto-install process to add the package manager's bin directory to the PATH environment variable, allowing tasks to access the package manager directly.
What changed?
format_path_envfunction public in thevite_installcrateauto_installto return the package manager's bin prefixInstallCommandto accept a pre-built package managerHow to test?
Run the new snap test which verifies that a task can execute
yarn --versiondirectly:Why make this change?
This change ensures that tasks can directly access the package manager without needing to specify its full path. This is particularly useful for scripts that rely on package manager commands (like
yarn,npm,pnpm) being available in the PATH. Previously, tasks would fail if they tried to execute package manager commands directly.