Following the discussion #19 and recent NuGet breaking changes (retired API).
It makes sense to remove the module FarPackage from PowerShellFar.
Reasons:
Users should use the online install/update scenario described in README instead of using local FarPackage. This reduces chances of FarPackage being out of date and related issues.
FarPackage distribution with PowerShellFar is awkward anyway because in many cases using it requires Far Manager exit. This makes little sense for having FarPackage in PowerShellFar\Modules.
Following the discussion #19 and recent NuGet breaking changes (retired API). It makes sense to remove the module FarPackage from PowerShellFar. Reasons:
PowerShellFar\Modules
.