Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting a "unexpected token =" error when trying to run on node version 14.21.3 #2

Open
wiill opened this issue Dec 13, 2024 · 2 comments

Comments

@wiill
Copy link

wiill commented Dec 13, 2024

$ 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

/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)

@nuryagdym
Copy link
Owner

Hi, seems like I forgot to publish 0.3.0 on npm. I published it now.

On my PC I tried to run v0.2.1 on node v14.21.3 but it did face any errors. Can it be that file was corrupted while downloading the package?

@wiill
Copy link
Author

wiill commented Dec 13, 2024

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.

Cheers again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants