search

GitSquared / edex-ui

A cross-platform, customizable science fiction terminal emulator with advanced monitoring & touchscreen support.
GNU General Public License v3.0
40.49k stars 2.55k forks source link

ENOENT warnings when compiling on Arch linux #561

Closed croxis closed 5 years ago

croxis commented 5 years ago

This happens both with git and with the AUR 2.2.2

npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/builder-util-fe37377b/out/log.js.map'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/ajv-a28d1bb3/dist/ajv.min.js.map'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/readable-stream-868a6ded/lib/internal'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/builder-util-fe37377b/out/nodeHttpExecutor.js.map'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/readable-stream-868a6ded/lib/internal'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/tweetnacl-0a4cb27f/nacl-fast.min.js'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/builder-util-fe37377b/out/promise.js.map'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/readable-stream-868a6ded/lib/internal'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/builder-util-fe37377b/out/util.js.map'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/tough-cookie-4960d15e/lib/memstore.js'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/dmg-builder-92b0dbca/vendor/mac_alias/osx.py'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/readable-stream-868a6ded/lib/internal'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/tough-cookie-4960d15e/lib/pathMatch.js'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/tough-cookie-4960d15e/lib/permuteDomain.js'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/tough-cookie-4960d15e/lib/pubsuffix.js'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/node-gyp-e19df71d/gyp/pylib/gyp/generator/cmake.py'
npm WARN tar ENOENT: no such file or directory, open '/home/croxis/src/edex-ui/node_modules/.staging/app-builder-lib-59d3d418/templates/icons/proton-native/proton-native.ico'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/7zip-bin-65f8a15b/linux/arm64'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/7zip-bin-65f8a15b/linux/ia32'
npm WARN tar ENOENT: no such file or directory, lstat '/home/croxis/src/edex-ui/node_modules/.staging/7zip-bin-65f8a15b/linux/x64'
npm ERR! code ERR_INVALID_OPT_VALUE
npm ERR! The value "false" is invalid for option "readableHighWaterMark"

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/croxis/.npm/_logs/2019-08-05T15_37_54_051Z-debug.log
GitSquared commented 5 years ago

Sounds like something failed in the archive download, which means there's nothing to fix on this side. I just pushed to the edex-ui-git AUR package; I recommend you try this one as it's more up to date.

Please reopen if it ever happens again.

croxis commented 5 years ago

Tried the AUR and git, same issue. Nothing is being extracted to node_modules. I make the .staging directory manually and still nothing is being populated, so something is very broken on my end. Thanks for the help though! Here is the log: https://termbin.com/2heq

GitSquared commented 5 years ago

I read your log but can't find anything that could help me understand what's going on...

Maybe you have a cache somewhere that's sending empty or corrupted data? Or maybe a firewall is blocking some of NPM's requets?