Marc-André MoreauArgh. how can I prevent PowerShell from automatically adding more paths to PSModulePath, and just accept the one I'm setting in the PSModulePath environment variable before launching the process?
Why can't PowerShell have nice things? this is not going to be easy to work around
I'm considering trying things I wish I didn't have to: github.com/dotnet/runti...
github.com/dotnet/runtime...
github.com/dotnet/runtime...
well, I think we've got something here. let's startup hook PowerShell to get stuff everyone wanted for years:
good news: I can force-override #$Env:PSModulePath with a startup hook in #PowerShell
bad news: PowerShellGet is a separate powershell module that doesn't care and does its own detection anyway
