Verifying deployment: FAILED because of const unicodeNormalizePath = (path) => { Unexpected token >

my global node version is and meteor version is 4.7.3 npm v4.3.0 Here is mupx log

[146.185.183.65] npm WARN deprecated on Windows, run them from an Administrator prompt.) [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated If you’re running the version of npm bundled with [146.185.183.65] npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS [146.185.183.65] npm WARN deprecated will be bundled with a version of npm@2, which has some small [146.185.183.65] npm WARN deprecated backwards-incompatible changes made to npm run-script and [146.185.183.65] npm WARN deprecated semver behavior. [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No description [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No repository field. [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No README data [146.185.183.65] npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server) [146.185.183.65] => Starting meteor app on port:80 [146.185.183.65] [146.185.183.65] /bundle/bundle/programs/server/mini-files.js:74 [146.185.183.65] const unicodeNormalizePath = (path) => { [146.185.183.65] ^ [146.185.183.65] SyntaxError: Unexpected token > [146.185.183.65] at Module._compile (module.js:439:25) [146.185.183.65] at Object.Module._extensions…js (module.js:474:10) [146.185.183.65] at Module.load (module.js:356:32) [146.185.183.65] at Function.Module._load (module.js:312:12) [146.185.183.65] at Module.require (module.js:364:17) [146.185.183.65] at require (module.js:380:17) [146.185.183.65] at Object.<anonymous> (/bundle/bundle/programs/server/boot.js:9:13) [146.185.183.65] at Module._compile (module.js:456:26) [146.185.183.65] at Object.Module._extensions…js (module.js:474:10) [146.185.183.65] at Module.load (module.js:356:32) [146.185.183.65] npm WARN deprecated This version of npm lacks support for important features, [146.185.183.65] npm WARN deprecated such as scoped packages, offered by the primary npm [146.185.183.65] npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the [146.185.183.65] npm WARN deprecated latest stable version. To upgrade to npm@2, run: [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated npm -g install npm@latest-2 [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated To upgrade to the latest stable version, run: [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated npm -g install npm@latest [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated (Depending on how Node.js was installed on your system, you [146.185.183.65] npm WARN deprecated may need to prefix the preceding commands with sudo, or if [146.185.183.65] npm WARN deprecated on Windows, run them from an Administrator prompt.) [146.185.183.65] npm WARN deprecated [146.185.183.65] npm WARN deprecated If you’re running the version of npm bundled with [146.185.183.65] npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS [146.185.183.65] npm WARN deprecated will be bundled with a version of npm@2, which has some small [146.185.183.65] npm WARN deprecated backwards-incompatible changes made to npm run-script and [146.185.183.65] npm WARN deprecated semver behavior. [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No description [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No repository field. [146.185.183.65] npm WARN package.json meteor-dev-bundle@0.0.0 No README data

[jyoti-openair]

I have set PORT 3000 already, I’m not sure where the issue was so I tried, pm2-meteor, now I have deployed using it

On Mar 6, 2017 7:54 AM, “Jose A. Arellano Vega” [e-mail] wrote:

You can setting up the port to use on your mup.js.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/zodern/meteor-up/issues/505#issuecomment-284285874, or mute the thread https://github.com/notifications/unsubscribe-auth/AK6KUzLlUKDw2gesu8eSTQXGHsk3Wf2nks5ri2r0gaJpZM4MSh15 .

[rclai]

I’m having the same problem and I have the right Docker image in place, but my error instead says:

/root/.meteor/packages/meteor-tool/.1.4.4_1.1t9hste++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/tools/cli/main.js:1487
}).run();
   ^

SyntaxError: Unexpected token y
    at Object.parse (native)
    at /tools/cli/main.js:803:12

=> Build Error. Check the logs printed above.
Error: build-error
    at ChildProcess.<anonymous> (/root/.nvm/versions/node/v6.10.2/lib/node_modules/mup/lib/modules/meteor/build.js:46:16)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:886:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:501:12)

If I try to build using the meteor CLI, it works fine, just not with mup unfortunately.