PowerShell / PowerShell/PSResourceGet
Installing modules trigger script path warning
Open
Nobody has claimed this yet.
Needs-Triage
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
Install pester and it will trigger the script path warning.
Expected behavior
# No warning
Actual behavior
Install-PSResource pester
WARNING: The installation path for the script does not currently appear in the CurrentUser path environment variable. To make the script discoverable, add the script installation path, C:\Users\Thomas\Documents\PowerShell\Modules, to the environment PATH variable.
Error details
N/A
Environment data
beta20
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning with Install-PSResource pester using the reported beta20 environment, then trace where the script installation path warning is emitted. Done means installing Pester no longer warns when the path is valid, while script discoverability remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100