archivebox / electron-archivebox Goto Github PK

The ability to have a specific OS build is highly suggested due to security risks of many users who will not and will not be able to use docker. Including, the use of Doctor requires technical skills and some machine specifications will not allow it all (physically impossible).

Overall, this a huge overhead and should be completely avoided.
Depending on Docker will cause the project to fail and remain experimental only.

Have you considered using React Native instead of Electron? It uses much less RAM and can use native UI components.

Unfortunately it's only available for Windows and MacOS at the moment - no Linux :(

https://microsoft.github.io/react-native-windows/

C:\Users\warshell\electron-archivebox>npm start
npm WARN config global --global, --local are deprecated. Use --location=global instead.

[email protected] start
electron-forge start

√ Checking your system
√ Locating Application
× Preparing native dependencies

An unhandled error has occurred inside Forge:
Could not detect abi for version 18.0.3 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
Error: Could not detect abi for version 18.0.3 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
at Object.getAbi (C:\Users\warshell\electron-archivebox\node_modules\electron-rebuild\node_modules\node-abi\index.js:36:9)
at new Rebuilder (C:\Users\warshell\electron-archivebox\node_modules\electron-rebuild\src\rebuild.ts:112:44)
at rebuildWithOptions (C:\Users\warshell\electron-archivebox\node_modules\electron-rebuild\src\rebuild.ts:363:21)
at doRebuild (C:\Users\warshell\electron-archivebox\node_modules\electron-rebuild\src\rebuild.ts:416:12)
at asyncFn (C:\Users\warshell\electron-archivebox\node_modules@electron-forge\core\src\util\rebuild.ts:15:23)
at C:\Users\warshell\electron-archivebox\node_modules@electron-forge\async-ora\src\ora-handler.ts:35:5
at new Promise ()
at asyncOra (C:\Users\warshell\electron-archivebox\node_modules@electron-forge\async-ora\src\ora-handler.ts:34:10)
at _default (C:\Users\warshell\electron-archivebox\node_modules@electron-forge\core\src\util\rebuild.ts:14:9)
at _default (C:\Users\warshell\electron-archivebox\node_modules@electron-forge\core\src\api\start.ts:44:9)
at C:\Users\warshell\electron-archivebox\node_modules@electron-forge\cli\src\electron-forge-start.ts:58:19

An unhandled error has occurred inside Forge:                                                                                                                 Could not detect abi for version 12.0.1 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
Error: Could not detect abi for version 12.0.1 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
at Object.getAbi (/home/user/repos/archivebox-desktop/node_modules/node-abi/index.js:30:9)
at new Rebuilder (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:112:44)
at rebuildWithOptions (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:363:21)
at doRebuild (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:416:12)
at asyncFn (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/util/rebuild.ts:15:23)
at /home/user/repos/archivebox-desktop/node_modules/@electron-forge/async-ora/src/ora-handler.ts:35:5
at new Promise (<anonymous>)
at asyncOra (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/async-ora/src/ora-handler.ts:34:10)
at _default (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/util/rebuild.ts:14:9)
at _default (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/api/start.ts:44:9)
at /home/user/repos/archivebox-desktop/node_modules/@electron-forge/cli/src/electron-forge-start.ts:58:19
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `electron-forge start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-03-16T22_13_51_504Z-debug.log

Not sure if it was just a problem on my end. Happened on a fresh install after running npm start step following steps in readme.

Ended up fixing with a npm update --depth 100

I think it's a problem with a dependency of a dependency, not necessarily anything wrong in this project

Please release this as a AppImage for Linux users.

Check chocolatey-community/chocolatey-package-requests#1048 for more info