A better ways to set modules clearly and safely on Windows platform #634

Motivation

As I'm starts developing my wemi project, I started realize there's some way can inprove Environment Modules deployment with install-win.rst mentioned.

Describe the solution you'd like

For Windows Terminal has released few years, I think is OK to give new ways for setup introductions to it.

Describe alternatives you've considered

Assume my Modules installation is C:\Developer\Modules:

In Windows Terminal settings panel, take powershell.exe(System contained PowerShell 5.1) or pwsh.exe (PowerShell 6/7) based profile.

Add command line: powershell / pwsh -NoExit -Command "& Import-Module 'C:\Developer\Modules\init\pwsh.ps1'", then save.

This allows Windows version modules after decompress-copy install, no need modify Environment variables PATH and bypass the install scripts. Just type envmodule can check if it's working.

Additional context

It can works on my device, with USER/System level PATH are not contain Modules install bin path.
Probably a show and tell session 😅, but it can be a modern deployment guide to modern Windows Terminal.

Is your feature request related to a problem? Please describe.

No. But a weak related issue is what I've experienced before. Ping me if dev team/you are interested in.