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.
Error: Line 1: Unexpected token
See original GitHub issueHi, i’m receiving this error on linux ubuntu machine instead in local Mac works perfectly. What can be the issue?
Thanks, Fabio
/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/EspreeFacade.ts:100
throw new Error(Line ${position.line}: ${errorMessage}\n${formattedPointer} ${formattedCodeSlice});
^
Error: Line 1: Unexpected token <
…<html>… at Function.value (/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/EspreeFac ade.ts💯15) at Function.value (/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/EspreeFac ade.ts:44:65) at e.value (/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/JavaScriptObfusc ator.ts:154:34) at e.value (/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/JavaScriptObfusc ator.ts:135:55) at Function.value (/srv/src/node_modules/javascript-obfuscator/dist/webpack:/JavaScriptObfuscator/src/JavaScrip tObfuscatorFacade.ts:27:85) at IncomingMessage.chres.on (/srv/src/app.js:193:66) at emitNone (events.js:111:20) at IncomingMessage.emit (events.js:208:7) at endReadableNT (_stream_readable.js:1055:12) at _combinedTickCallback (internal/process/next_tick.js:138:11)
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry my issue was related to an wasm file
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.