This just seems like a bug as it shouldn't show modules you can't use directly. In the debugger, it's simply running get-module -name and then nested module is being returned. Best I can tell, it's supposed to be using the current runspace.

/cc @MartinGC94

I reproduced the problem in PowerShell 5.1 with PSReadLine loaded. I ran powershell -noprofile -noninteractive so that PSReadLine would not be loaded. The problem didn't occur. Next I loaded PSReadLine 2.2.0 (to rule out newer versions). The problem returned. So it looks like this is something in the PSReadLine code.

Thank you @ThomasNieto for reporting this experience. We agree that normally you don't see nested modules, and that this is a bug. Similar issue here: #16941

@daxian-dbw could you please move this issue to the PSReadLine repo?

This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.

Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.