Closed zootella closed 5 years ago
Copying these here also:
$ node ./scripts/module-search.js utp-native
Searching for utp-native...
needs "utp-native" version "^2.0.1" in node_modules\@hyperswarm\network\package.json
needs "utp-native" version "^1.7.3" in node_modules\ara-reward-dcdn\package.json
needs "utp-native" version "^1.7.2" in node_modules\discovery-swarm\package.json
is "utp-native" version "1.7.3" in node_modules\utp-native\package.json
Use@DESKTOP-1QOQVPI MINGW64 /c/Documents/p1/ara-file-manager (ej_mainnet)
$ npm ls utp-native
ara-file-manager@0.12.3 C:\Documents\p1\ara-file-manager
+-- ara-filesystem@0.27.0
| `-- ara-network@1.3.8
| `-- discovery-swarm@5.1.4
| `-- utp-native@1.7.3 deduped
`-- ara-reward-dcdn@0.18.0 (github:arablocks/ara-reward-dcdn#8c50d9c507a75a7e236414032d3e10e3424432e5)
+-- @hyperswarm/network@0.0.4
| `-- UNMET DEPENDENCY utp-native@2.1.4
`-- utp-native@1.7.3
npm ERR! missing: utp-native@2.1.4, required by @hyperswarm/network@0.0.4
Hi @jwerle this is the fix you suggested. @mahjiang and I believe it is preventing crashes when archiving is slow/unreliable. So, interested to know your thought on:
-should we make it the default for FM? -is there a better way to prevent Ara modules from trying to use the older utp-native?