Skip to content

dependancies: "npm install" fails on pulling @AlCalzone node-aead-crypto #3

@afleuryg

Description

@afleuryg

Hi,
While trying to install, I got this bunch of errors:

node-pre-gyp ERR! Tried to download(404): https://github.com/AlCalzone/node-aead-crypto/releases/download/v1.0.2/node-v83-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for node-aead-crypto@1.0.2 and node@14.16.0 (node-v83 ABI) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(undefined): https://github.com/AlCalzone/node-aead-crypto/releases/download/v1.0.2/node-v83-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for node-aead-crypto@1.0.2 and node@14.16.0 (node-v83 ABI) (falling back to source compile with node-gyp)
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppBuild.targets(325,5): error MSB3371: The file "Release\obj\node_aead_crypto\node_aead
_crypto.tlog\unsuccessfulbuild" cannot be created. The process cannot access the file 'C:\Users\AFG\Desktop\tradfri-app-master\node_modules\node-aead-crypto\build\Release\obj\node_aead_c
rypto\node_aead_crypto.tlog\unsuccessfulbuild' because it is being used by another process. [C:\Users\AFG\Desktop\tradfri-app-master\node_modules\node-aead-crypto\build\node_aead_crypto.
vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Windows_NT 10.0.18363

From my current ignorance, I see 2 possibilities:

  • @AlCalzone changed/deleted its repository (changed the name ?)
  • I may have to update Visual Studio to the latest version

There is a third possibility: I didn't understand something.

Any idea?
Thanks in advance for any help...
A.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions