npm install -g @aws-amplify/cli error #1996
Comments
|
+1 |
|
We’ve seen the gyp issue for certain npm versions and adding the unsafe-perm parameter should help fix it - ‘npm install -g @aws-amplify/cli --unsafe-perm=true’? |
|
This command worked for me. if i don't use 'unsafe-perm=true' my installation was failing on optional packages. with the above command the apmlify cli continued installing ignoring the optional packages like gyp, fs-ext |
SwaySway
added
installation
|
I switched back to previous version. All good now.
Amplify team - you better cover the release to npm with some tests
…On Thu, Aug 8, 2019, 20:07 Anant Rao ***@***.***> wrote:
This command worked for me. if i don't use 'unsafe-perm=true' my
installation was failing on optional packages. with the above command the
apmlify cli continued installing ignoring the optional packages like gyp,
fs-ext
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1996?email_source=notifications&email_token=AAHVI6ZYIBTQAKALNZ376ATQDRHFLA5CNFSM4IKJ5EH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34I7FY#issuecomment-519606167>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHVI65QGMWZSWFRZR3GK5DQDRHFLANCNFSM4IKJ5EHQ>
.
|
|
@lielran We are aware of this npm issue and working on the fix so that you don't have to use the --unsafe-perm parameter, but as a workaround as i mentioned above you can use Note: This issue is prevelant only in certain platform specific npm versions. |
|
Ran in to the same issue, the Node v10.16.2 |
|
+1 |
SwaySway
added
bug
|
+1 Mac OS: Darwin Kernel Version 18.6.0 |
Updated install script to install dynamodb local inside user home directory instead of package root partial fix#1996
|
We have a fix for npm global install. Could you guys try to install the cli using the following command and see if it still fails to install npm install -g @aws-amplify/cli@ddb-local-install-script |
|
The @ddb-local-install-script version still fails for me. Log: |
|
@kernwig it looks like those errors were for optional installations. Could you run |
|
$ amplify -v |
|
Looks like the installation was successful. Could you try to run the mock server on an existing project and see if that works as expected. cd <project-root>
amplify mock |
|
I don't have a working project. :-/ |
|
npm install -g @aws-amplify/cli@ddb-local-install-script isnt working |
|
|
|
I tried My versions: Despite all the errors, I was able to successfully run |
|
Same issue, Windows 10. My prompt said that Amplify-CLI was successfully installed without that options(gyp, fs-ext). Is is serious damage to use amplify cli? I hope that I could understand full subsequences of absence of these options. Node version: 10.16.0 final prompt on installing @aws-amplify/cli: |
|
Same issue here. How can we install an old version that works? |
|
I have Similar issue npm install -g npm choco upgrade python //------------------------------------------------------------------------------------------------------------
C:\Users\psyrenpark\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\zmq>if not defined npm_config_node_gyp (node "C:\Users\psyrenpark\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Users\psyrenpark\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Ignore installation errors for optional dependencies: gyp, fs-ext Successfully installed the Amplify CLIJavascript Getting Started - https://aws-amplify.github.io/docs/js/start Android Getting Started - https://aws-amplify.github.io/docs/android/start iOS Getting Started - https://aws-amplify.github.io/docs/ios/start npm WARN rollback Rolling back [email protected] failed (this is probably harmless): EPERM: operation not permitted, lstat 'C:\Users\psyrenpark\AppData\Roaming\npm\node_modules@aws-amplify\cli\node_modules\fsevents\node_modules' |
|
I also encountered the With following tree: we can deduce that while kafka-node has a newer version with a fix SOHU-Co/kafka-node#760 applied, moscajs/ascoltatori#195 hasn't progressed to use a newer kafka-node. |
|
Hey guys, we released a version of the CLI - v3.14.0 which fixes the npm warnings and the associated errors during npm/yarn installations. It also takes care of the EOL dependency issues. Please install the latest version of the CLI - |
|
Solution from #1996 (comment) Documented on StackOverflow. |
|
Sudo makes better since so that it prompts for a device password and overrides the permission errors. Genius! |
|
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
npm install -g @aws-amplify/clifailed due to the new versionoutput:
The text was updated successfully, but these errors were encountered: