SyntaxError: Unexpected token > at Module._compile (module.js:439:25)
See original GitHub issueDeployment error with the latest version. See here the logs:
npm WARN deprecated This version of npm lacks support for important features,
npm WARN deprecated such as scoped packages, offered by the primary npm
npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
npm WARN deprecated latest stable version. To upgrade to npm@2, run:
npm WARN deprecated
npm WARN deprecated npm -g install npm@latest-2
npm WARN deprecated
npm WARN deprecated To upgrade to the latest stable version, run:
npm WARN deprecated
npm WARN deprecated npm -g install npm@latest
npm WARN deprecated
npm WARN deprecated (Depending on how Node.js was installed on your system, you
npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
npm WARN deprecated on Windows, run them from an Administrator prompt.)
npm WARN deprecated
npm WARN deprecated If you're running the version of npm bundled with
npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
npm WARN deprecated will be bundled with a version of npm@2, which has some small
npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
npm WARN deprecated semver behavior.
npm WARN package.json meteor-dev-bundle@0.0.0 No description
npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle@0.0.0 No README data
npm WARN package.json string_decoder@1.0.3 string_decoder is also the name of a node core module.
npm WARN cannot run in wd meteor-dev-bundle@0.0.0 node npm-rebuild.js (wd=/bundle/bundle/programs/server)
=> Starting meteor app on port:80
/bundle/bundle/programs/server/mini-files.js:82
const unicodeNormalizePath = (path) => {
^
SyntaxError: Unexpected token >
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/bundle/bundle/programs/server/boot.js:9:13)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
SyntaxError: Unexpected token { at Module._compile
Here's my code for election.js: import { isMainThread } from "worker_threads"; import { AssertionError } from "assert"; var Election ...
Read more >SyntaxError:Unexpected token while importing npm module
These modules are scripted in typescript and packaged using yarn build (babel loader is used). We want to import one of the modules...
Read more >Cant build my vuejs app on production but can locally ... - Reddit
SyntaxError : Unexpected token {. at Module._compile (internal/modules/cjs/loader.js:721:23). at Object.Module.
Read more >unexpected token 'export' at object.compilefunction (node:vm ...
SyntaxError : Unexpected token 'export' when running mocha test ... Build error (specifically a syntax error) in material ui node modules which only...
Read more >help with nodejs-related compile issue ("Unexpected token =>")
I'd be looking for some assistance with a user-reported compile error ... args.file.map(f => ({ ^ SyntaxError: Unexpected token > at Module.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
meteor.dockerImage
will be fixed in 1.3.3.This will also be fixed in 1.3.3.
It’s using the wrong docker image. Both configs have the docker image set in
meteor.dockerImage
. Try setting it inmeteor.docker.image
instead. I will try to fix it for the next release.