Skip to content

when parse-server upgrade to 2.7.4 did't work,why? #4688

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

Closed
dovewi opened this issue Mar 31, 2018 · 1 comment
Closed

when parse-server upgrade to 2.7.4 did't work,why? #4688

dovewi opened this issue Mar 31, 2018 · 1 comment

Comments

@dovewi
Copy link

dovewi commented Mar 31, 2018

#> [email protected] start /home/bae/app
#> node --harmony index.js
#/home/bae/app/.bae/node_modules/parse-server/lib/ParseServer.js:124
# const {
# ^
#SyntaxError: Unexpected token {
# at exports.runInThisContext (vm.js:53:16)
# at Module._compile (module.js:374:25)
# at Object.Module._extensions..js (module.js:417:10)
# at Module.load (module.js:344:32)
# at Function.Module._load (module.js:301:12)
# at Module.require (module.js:354:17)
# at require (internal/module.js:12:17)
# at Object.<anonymous> (/home/bae/app/.bae/node_modules/parse-server/lib/index.js:8:21)
# at Module._compile (module.js:410:26)
# at Object.Module._extensions..js (module.js:417:10)
#npm ERR! Linux 3.10.1-grsec
#npm ERR! argv "/home/admin/runtime/node/bin/node" "/home/admin/runtime/node/bin/npm" "start"
#npm ERR! node v4.2.6
#npm ERR! npm v2.14.12
@dovewi dovewi changed the title when parse-server upgrade to 2.7.1 did't work,why? when parse-server upgrade to 2.7.4 did't work,why? Mar 31, 2018
@flovilmart
Copy link
Contributor

Please use a more recent version of node JS. 8.11 for example.

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