-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PooshError: Unable to resolve plugin "poosh-plugin-s3" (Windows) #1
Comments
Thanks @Jubijub for the bug report 😬 I'm not quite sure but poosh uses a package resolution mechanism that can reach global packages (for the s3 plugin). This mechanism has not been tested on Windows and it looks like it fails:
I need to investigate a little bit... Possible Workaround
Local installation of S3 plugin will create a node_module folder in your working directory, that's why I suggest you to put your static website content inside a dedicated directory:
and use |
I would like to know your global path prefix, can you run |
C:\Users\jubij>npm config get prefix
C:\Users\jubij\AppData\Roaming\npm This is a fairly typical place to store this kind of things for Windows I don't use NVM (this is a fresh install of node (it was not installed on this computer before), and poosh and relates modules are the only non-default modules installed |
I have both, on the path given above, and both directories are populated |
I used path.join in this commit I haven't yet tested it on Windows.. but I think it's gonna be ok.. Let me know @Jubijub 🙃 |
I finally managed to test installation on Windows.. and it's still not working because I forgot that:
|
Now everything is finally fixed to be portable on Windows in v1.0.6 Release. |
Confirmed, it's fixed |
Fresh install on windows 10 64 :
npm install -g poosh-cli poosh-plugin-s3
with no apparent issueI use the following poosh config, which apart from the remote, is the same as the example
I tried both with
plugins : ["s3"]
and the config belowActual result :
The text was updated successfully, but these errors were encountered: