You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2022. It is now read-only.
git clone this repo locally onto an OSX machine (this one running 10.14)
Run the commands provided in this project's README.md
> npm i && npm start
Watch 100's of lines of messages scroll by, including many warnings about vulnerable packages (which I tried addressing however the updates didn't affect this particular issue so I reverted rather than chasing those issues).
node -v
v12.6.0
npm -v
6.9.0
node_modules/.bin/pm2 ls
┌──────────┬────┬─────────┬─────────┬─────┬─────────┬─────────┬────────┬─────┬────────┬─────────────────┬──────────┐
│ App name │ id │ version │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
├──────────┼────┼─────────┼─────────┼─────┼─────────┼─────────┼────────┼─────┼────────┼─────────────────┼──────────┤
│ zip2zim │ 0 │ 1.0.0 │ cluster │ 0 │ errored │ 30 │ 0 │ 0% │ 0 B │ julianharty_air │ disabled │
└──────────┴────┴─────────┴─────────┴─────┴─────────┴─────────┴────────┴─────┴────────┴─────────────────┴──────────┘
Even if the current code isn't fit for 2019, it does actually run on Node v8 after all.
Still doesn't process the large ZIP file successfully, something to aim for with the rewrite? :)
Here's an extract of the various commands I ran for posterity. This is with a clean checkout of this codebase (removing/reverting any package dependency updates)
git clone this repo locally onto an OSX machine (this one running 10.14)
Run the commands provided in this project's README.md
Watch 100's of lines of messages scroll by, including many warnings about vulnerable packages (which I tried addressing however the updates didn't affect this particular issue so I reverted rather than chasing those issues).
A partial extract from
~/.pm2/pm2.log
The pm2 output log and pm2 error log for the process are both empty.
PS: this isn't the same error as #2 from what I can tell.
The text was updated successfully, but these errors were encountered: