Install-RequiredModule

Author(s)

• Joel 'Jaykul' Bennett

Tags

Install Requirements Development Dependencies Modules

Dependencies

This script has no dependencies.

Release Notes

5.1.1 Fix the support for prerelease versions
5.1.0 Supports Upgrading Modules
- Added -Upgrade to allow searching for newer versions of installed modules while still enforcing the version range
- Includes a warning when in -Upgrade mode, if there is a newer version that will not be installed because of the version range
Also...
- Added Optimize-Dependency, and use it to make sure we install dependencies in order
- Work around an issue installing modules where OLD versions have a dependency that has been de-listed
- Wrote more tests. Fixed stuff that did not work as expected
5.0.5 Fix the -Destination parameter
5.0.2 Fix a bug with PowerShellGet 1.0.0.1
5.0.1 Fix PowerShell 5 .Where bug again (sorry)
5.0.0 Available as a module, with multiple repository support
BREAKING CHANGES:
- No longer automatically trusts PSGallery. You must ensure that there is at least one repository registered and trusted, or use the `-TrustRegisteredRepositories` to trust all repositories.
- Allows installing from any trusted repository. There is also new syntax for the RequiredModules hashtables to support specifying a specific repository for any specific module. See the ReadMe or the help for Install-RequiredModule.
MAJOR IMPROVEMENTS:
- Supports passing the RequiredModules hashtable directly on the commandline, rather than requiring a file.
- Also available in the "RequiredModules" module
By default, we only install from trusted repositories. You should mark the repositories you regularly install from as trusted repositories. See the following example to trust the default PSGallery:
Register-PSRepository -Default -ErrorAction Ignore -InstallationPolicy Trusted
Get-PSRepository -Name PSGallery | Set-PSRepository -InstallationPolicy Trusted
4.1.1 Minor fixes for edge cases and options
4.1.0 Support non-PSGallery feeds
4.0.6 Fix a double -Verbose problem
4.0.5 Let the -Destination be non-empty (so we do not have to re-download every time)
4.0.4 Fix PowerShell 5 .Where bug
4.0.3 Fix module check when using -Destination to force all modules to be in destination
4.0.2 Fix Remove-Module error
4.0.1 Add logging outputs
4.0.0 BREAKING CHANGE: require the -Destination to start empty (allow -CleanDestination to clear it)
Fix for adding the destination to PSModulePath multiple times
Started testing this so I can ship it to PowerShellGet
3.0.0 BREAKING CHANGE: switch -SkipImport to -Import -- inverting the logic to NOT import by default
Add -Destination parameter to support installing in a local tool path
2.0.1 Squash mistaken "InstallError" message caused by Select-Object -First
Clean up output that was unexpected
2.0.0 BREAKING CHANGE: use NuGetVersion to support wildcards like 3.*
Improve the error messages around aborted or failed installs
1.0.1 Fix "Version 3.4.0 of module Pester is already installed"
1.0.0 This is the first public release - it probably does not work right