Description
It would be wonderful if PowerShell supported nupkg files natively (PowerShell/PowerShell#7259), but as a stop-gap (or perhaps, as part of the implementation of that), it would be really great if Install-Module
had a parameter set where we just pass the path to a .nupkg file.
In fact, it would be great if you could associate powershell -c Install-Module "%1" -scope CurrentUser
with the package extension, and people could then install modules on Windows by simply right-clicking and choosing Install as PowerShell Module...
NOTE: I think it would be important to also do PowerShell/PowerShellGet#794 while you were at it, to allow modules to more easily ship with multiple platform-specific implementations
Bonus points for making up your own file extension like .psmodule so we don't have the "Install as PowerShell Module" option on all our .nupkg files...