question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unexpected token ) after latest update (1.7.2)

See original GitHub issue

I’ve this error message after the latest update (f51b931c831ed405e535025aea24dafdffb11e11)

//node_modules/lcov-result-merger/node_modules/vinyl-fs/node_modules/gulp-sourcemaps/index.js:38 debug(() => {return options;}); SyntaxError: Unexpected token ) at exports.runInThisContext (vm.js:73:16) at Module._compile (module.js:443:25) at Object.Module._extensions..js (module.js:478:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Module.require (module.js:365:17) at require (module.js:384:17) at Object.<anonymous> (//node_modules/lcov-result-merger/node_modules/vinyl-fs/lib/src/index.js:8:18) at Module._compile (module.js:460:26) at Object.Module._extensions..js (module.js:478:10)

The token referred is the first closing round bracket: debug(() => {return options;});

I’m using node v0.12.7

Replacing all () => {<return here>} with function() {<return here} seems to fix it.

I’m not sure if it would be a good fix, or maybe the problem is related to the node version. If the latest, maybe 1.7.2 should be restricted to higher versions of NodeJs

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:4
  • Comments:8

github_iconTop GitHub Comments

14reactions
nmccreadycommented, Oct 12, 2016

Ugh, yeah your right. I’ll revert the es6 tomorrow. Unpublish 1.7.2 and push 1.7.

Sent from my mobile device

VR,

Nicholas McCready twitter:nmccready email:nmccready@gmail.com github:nmccready

On Oct 11, 2016 10:38 PM, “Gaspar Zaragoza” notifications@github.com wrote:

I’ve this error message after the latest update

//node_modules/lcov-result-merger/node_modules/vinyl-fs/ node_modules/gulp-sourcemaps/index.js:38 debug(() => {return options;}); SyntaxError: Unexpected token ) at exports.runInThisContext (vm.js:73:16) at Module._compile (module.js:443:25) at Object.Module._extensions…js (module.js:478:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Module.require (module.js:365:17) at require (module.js:384:17) at Object.<anonymous> (//node_modules/lcov-result- merger/node_modules/vinyl-fs/lib/src/index.js:8:18) at Module._compile (module.js:460:26) at Object.Module._extensions…js (module.js:478:10)

The token referred is the first closing round bracket: debug(() => {return options;});

I’m using node v0.12.7

Replacing all () => {<return here>} with function() {<return here} seems to fix it.

I’m not sure if it would be a good fix, or maybe the problem is related to the node version. If the latest, maybe 1.7.2 should be restricted to higher versions of NodeJs

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/floridoo/gulp-sourcemaps/issues/236, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjnqa7Hm6lOyF1cbLFPcsuhGmi_hGTtks5qzEgLgaJpZM4KUThu .

4reactions
nmccreadycommented, Oct 12, 2016

Done https://github.com/floridoo/gulp-sourcemaps/releases/tag/v1.7.3

8ecaa7320d0c656514dfc07b15611d682f757818 39e1b3b1ffee13620e6d56fc4c673c04271406ec

Important notes:

debug-fabulous also had to be made node compat 0.X as well as lazy-debug

https://github.com/nmccready/debug-fabulous/commit/696f343617dce122ae03dc95e47050e48e87e3d4

Read more comments on GitHub >

github_iconTop Results From Across the Web

error Unexpected token = after upgrading from RN 0.64.2 to ...
I had this issue after upgrading RN to 65.1. As per my investigation it is caused by an incorrect Node.js version used during...
Read more >
Upgrade 1.7.7.8 (php7.2) to PS1.7.8.6 - ParseError ... - GitHub
Upgrade 1.7.7.8 (php7.2) to PS1.7.8.6 - ParseError unexpected token #28394 ; 1.7.8.6 Affects versions ; Autoupgrade Module: autoupgrade ; BO Category: Back Office ......
Read more >
Unexpected error found when trying to post – YOAST is ...
Out of nowhere, while trying to create a new post, I've started to get the following unexpected error: TypeError: Cannot read property ......
Read more >
Update 1.7.2 | Developer Live Stream | Hunt: Showdown
Join us for the first Developer Live Stream of the year, taking a closer look at Update 1.7.2 !~~~~~~~~~~~~~~~~~~~~~~~~~~~Get Hunt Showdown ...
Read more >
Bug listing with status RESOLVED with resolution OBSOLETE ...
... for mailman admins (new ebuild)" status:RESOLVED resolution:OBSOLETE severity:normal ... Bug:54727 - "gentoo-stats --update fails with error message" ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found