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
Had some fun trying to build again, got a bunch of those errors, puzzling to me:
> deltachat-desktop@1.28.2 build:backend /home/hpk/p/delta/desktop
> tsc --build src/main
../node/dist/context.d.ts:9:10 - error TS2305: Module '"stream"' has no exported member 'EventEmitter'.
9 import { EventEmitter } from 'stream';
While the README says v14.0.0 or newer is required, i use v14.8.12. Turns out that v14.8.13 avoids the above error.
It seems that v16 (stable node) is actually working. The whole thing took me like an hour to figure out, and it has happened before that i stumbled into node version issues.
Could the "npm run build" (or npm install) be made to check that a known-to-work version (from some list) is used?
The text was updated successfully, but these errors were encountered:
you need to use #2687, this is because deltachat-node master is already on node 16
or you just use the slightly older deltachat node version on tag 1.77.0 for now.
Could the "npm run build" (or npm install) be made to check that a known-to-work version (from some list) is used?
The readme of dc node says it uses node 16 now and the changelog of dc node also states that. also while doing npm i you should have gotten a warning that deltachat-node needs nodejs version 16 now, maybe that warning is broken?
Had some fun trying to build again, got a bunch of those errors, puzzling to me:
While the README says v14.0.0 or newer is required, i use v14.8.12. Turns out that v14.8.13 avoids the above error.
It seems that v16 (stable node) is actually working. The whole thing took me like an hour to figure out, and it has happened before that i stumbled into node version issues.
Could the "npm run build" (or npm install) be made to check that a known-to-work version (from some list) is used?
The text was updated successfully, but these errors were encountered: