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
below is my error stack trace when starting up my app on a PI 3B+ with mentioned version, whereas all is fine running on a PI4 with
$ node -v
v12.22.5
using 0.2.1 version of your module, based on info from npmjs.com, would latest version manual install from github solve the problem ?
looking forward to your answers...
Cheers
/node_modules/node-ftpsync/src/remote-to-local-sync.js:15
static isModified = (localFile, remoteFile) => {
^
SyntaxError: Unexpected token =
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
The text was updated successfully, but these errors were encountered:
Hi @nuryagdym , thanks a lot for your quick feedback.
Actually, after digging deeper, it seems I have nodejs versions conflicting between my root user (still 8.17) and my standard user (successfully updated to v14.21.3 as previously mentioned)
And additionnaly, my setup is using pm2 (as root) so still using the 8.x...
Sorry for bothering, please consider the issue as closed as it appears clearly my PI3B+ setup is inconsistent (based on stretch, which is not supported anymore...). I'll update from npm , but as you said it does't seem to be a bug on your side.
$ node -v
v14.21.3
below is my error stack trace when starting up my app on a PI 3B+ with mentioned version, whereas all is fine running on a PI4 with
$ node -v
v12.22.5
using 0.2.1 version of your module, based on info from npmjs.com, would latest version manual install from github solve the problem ?
looking forward to your answers...
Cheers
The text was updated successfully, but these errors were encountered: