question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Yarn command failed

See original GitHub issue

Yarn ‘add’, ‘upgrade’ command failed except ‘remove’

  • React Nattive: 0.47.1
  • Client OS & Version: Win10

I need upgrading other RN module running ‘yarn upgrade xxx’ and got this. Delete ‘node_modules’ , clear yarn cache has no effects. Unless remove realm can I upgrade other modules.

[4/4] Building fresh packages… ████████████████████████████████████████████████████████████[1/2] ⠐ react-native-elements: *** [2/2] ⠐ realm: not ok [-/2] ⠐ waiting… [-/2] ⠈ waiting… error D:\new BLEHygrometer\node_modules\realm: Command failed. Exit code: 1 Command: C:\WINDOWS\system32\cmd.exe Arguments: /d /s /c node-pre-gyp install --fallback-to-build Directory: D:\new BLEHygrometer\node_modules\realm Output: node-pre-gyp info it worked if it ends with ok node-pre-gyp info using node-pre-gyp@0.6.36 node-pre-gyp info using node@7.10.0 | win32 | x64 node-pre-gyp info check checked for “D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” (not found) node-pre-gyp http GET https://static.realm.io/node-pre-gyp/1.10.3/realm-v1.10.3-node-v51-win32-x64.tar.gz node-pre-gyp ERR! Tried to download(undefined): https://static.realm.io/node-pre-gyp/1.10.3/realm-v1.10.3-node-v51-win32-x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for realm@1.10.3 and node@7.10.0 (node-v51 ABI) (falling back to source compile with node-gyp) node-pre-gyp http socket hang up

D:\new BLEHygrometer\node_modules\realm>if not defined npm_config_node_gyp (node “C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\…..\node_modules\node-gyp\bin\node-gyp.js” clean ) else (node “” clean ) gyp info it worked if it ends with ok gyp info using node-gyp@3.5.0 gyp info using node@7.10.0 | win32 | x64 gyp info ok

D:\new BLEHygrometer\node_modules\realm>if not defined npm_config_node_gyp (node “C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\…..\node_modules\node-gyp\bin\node-gyp.js” configure --fallback-to-build “–module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” --module_name=realm “–module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64” ) else (node “” configure --fallback-to-build “–module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” --module_name=realm “–module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64” ) gyp info it worked if it ends with ok gyp info using node-gyp@3.5.0 gyp info using node@7.10.0 | win32 | x64 gyp info spawn C:\Python27\python.EXE gyp info spawn args [ ‘C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py’, gyp info spawn args ‘binding.gyp’, gyp info spawn args ‘-f’, gyp info spawn args ‘msvs’, gyp info spawn args ‘-G’, gyp info spawn args ‘msvs_version=auto’, gyp info spawn args ‘-I’, gyp info spawn args ‘D:\new BLEHygrometer\node_modules\realm\build\config.gypi’, gyp info spawn args ‘-I’, gyp info spawn args ‘C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\addon.gypi’, gyp info spawn args ‘-I’, gyp info spawn args ‘C:\Users\Richard\.node-gyp\7.10.0\include\node\common.gypi’, gyp info spawn args ‘-Dlibrary=shared_library’, gyp info spawn args ‘-Dvisibility=default’, gyp info spawn args ‘-Dnode_root_dir=C:\Users\Richard\.node-gyp\7.10.0’, gyp info spawn args ‘-Dnode_gyp_dir=C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp’, gyp info spawn args ‘-Dnode_lib_file=node.lib’, gyp info spawn args ‘-Dmodule_root_dir=D:\new BLEHygrometer\node_modules\realm’, gyp info spawn args ‘–depth=.’, gyp info spawn args ‘–no-parallel’, gyp info spawn args ‘–generator-output’, gyp info spawn args ‘D:\new BLEHygrometer\node_modules\realm\build’, gyp info spawn args ‘-Goutput_dir=.’ ] gyp info ok

D:\new BLEHygrometer\node_modules\realm>if not defined npm_config_node_gyp (node “C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\…..\node_modules\node-gyp\bin\node-gyp.js” build --fallback-to-build “–module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” --module_name=realm “–module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64” ) else (node “” build --fallback-to-build “–module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” --module_name=realm “–module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64” ) gyp info it worked if it ends with ok gyp info using node-gyp@3.5.0 gyp info using node@7.10.0 | win32 | x64 gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe gyp info spawn args [ ‘build/binding.sln’, gyp info spawn args ‘/clp:Verbosity=minimal’, gyp info spawn args ‘/nologo’, gyp info spawn args ‘/p:Configuration=Release;Platform=x64’ ] �ڴ˽���������һ������һ����Ŀ����Ҫ���ò������ɣ������ӡ�/m�����ء� MSBUILD : error MSB3428: δ�ܼ��� Visual C++ ������VCBuild.exe����Ҫ���������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ��������������װ��������λ�ã ��뽫��λ�����ӵ�ϵͳ·���С� [D:\new BLEHygrometer\node_modules\realm\build\binding.sln] gyp ERR! build error gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\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:276:23) gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at ChildProcess.emit (events.js:194:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) gyp ERR! System Windows_NT 10.0.14393 gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js” “build” “–fallback-to-build” “–module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node” “–module_name=realm” “–module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64” gyp ERR! cwd D:\new BLEHygrometer\node_modules\realm gyp ERR! node -v v7.10.0 gyp ERR! node-gyp -v v3.5.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute ‘node-gyp.cmd build --fallback-to-build --module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node --module_name=realm --module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64’ (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (D:\new BLEHygrometer\node_modules\node-pre-gyp\lib\util\compile.js:83:29) node-pre-gyp ERR! stack at emitTwo (events.js:106:13) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:194:7) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:899:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) node-pre-gyp ERR! System Windows_NT 10.0.14393 node-pre-gyp ERR! command “C:\Program Files\nodejs\node.exe” “D:\new BLEHygrometer\node_modules\node-pre-gyp\bin\node-pre-gyp” “install” “–fallback-to-build” node-pre-gyp ERR! cwd D:\new BLEHygrometer\node_modules\realm node-pre-gyp ERR! node -v v7.10.0 node-pre-gyp ERR! node-pre-gyp -v v0.6.36 node-pre-gyp ERR! not ok Failed to execute ‘node-gyp.cmd build --fallback-to-build --module=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64\realm.node --module_name=realm --module_path=D:\new BLEHygrometer\node_modules\realm\compiled\node-v51_win32_x64’ (1) info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:20 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
knethcommented, Aug 21, 2017

@adyanced static.realm.io is hosted by AWS which is blocked in some countries. Does it an issue for you?

@nuocgansoi Did you install Visual C++ (the error message indicates that it is missing).

0reactions
knethcommented, Dec 18, 2018

@benhartouz We don’t support node 11 yet. It is tracked by #2149.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Yarn Start Command failed with exit code 1 - node.js
SOLUTION · Go to start-menu -> search and type environment variables and open it · There will be a variable named PATH. Append...
Read more >
Error Codes | Yarn - Package Manager
This informational message occurs when Yarn wishes to let you know that a package will need to be built for the installation to...
Read more >
Yarn error command failed with exit code 127 · Issue #3897
My yarn wont load for some reason. I always get a error with command failed with exit code 127. I cant seem to...
Read more >
Getting error messages when running yarn commands
I am getting this odd error message. I noticed it when I tried to update Redwood. It does not seem to matter what...
Read more >
yarn build error "Command failed with exit code 137"
Exist code 137 means the build process ran out of memory. You will need to increase the amount of memory available or enable...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found