Merged
Conversation
… detects the same module installed some other place on the system Fixes #45
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.
Fixes #45
This pull request fixes an issue with the
Install-ModuleFastfunction where it doesn't install modules in the specified destination if the same module is already installed in a different location on the system.To address this issue, I have added a new parameter
-DestinationOnlyto theInstall-ModuleFastfunction. When this parameter is specified, the function will only consider the specified destination and not any other paths currently in thePSModulePath. This is useful for scenarios where you want to ensure that the modules are installed in a specific location, such as in a CI environment.I have also made changes to the
Get-ModuleFastPlanandFind-LocalModulefunctions to support the new-DestinationOnlyparameter.