Provide an easy way to add additional module paths to PSModulePath via settings

Some projects might benefit from an easy way to add paths to their PowerShell session’s PSModulePath so that modules in non-standard paths are available for IntelliSense and parse-time checks.

One specific use case is developing multiple DSC resources in the same folder structure. You will get parse-time errors about missing DSC resources if your the other resources you’re developing cannot be found in the PSModulePath.

It’s fairly easy to change your Microsoft.VSCode_profile.ps1 to add your workspace path to $env:PSModulePath but that setting will not transfer to other developers in the project. If this was a workspace-level setting, it could be enabled for anyone who opens the code in VS Code.

[daviwil]

Yep, exactly what I’m thinking, the setting would be a list of paths that defaults to just ${workspaceRoot}. And the nice thing is that I’m already adjusting the PSModulePath to add the “bundledModulesPath” so this would just be a generalization of what I’m doing already 😃

[SeeminglyScience]

I need too dig more in the code to give you a better answer on how to properly implement this feature.

Pretty sure we already add the bundled modules path to PSModulePath, so it could probably be added there.

It’s worth noting though, this could also cause some unintended code execution. If a workspace adds a PSModulePath with a module that exports a function for every letter (i.e. one function called a, one called b, etc) then typing anything in the editor pane will cause the psm1 to be invoked.

A lot less problematic than workspace profiles, but still something to consider.