evanw / evanw/node-source-map-support
SyntaxError: Unexpected token z in JSON at position 0
- Lingua principale
- JavaScript
- Stelle
- 2.2k
- Fork
- 223
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
I have the following situation:
* I start Karma with `node --require coffeescript/register' since my Karma config is in CoffeeScript
* Karma loads ts-node to support TypeScript modules
* I have a custom Karma preprocessor for compiling CoffeeScript, since karma-coffee-preprocessor doesn't support CoffeeScript 2.
* I configure CoffeeScript to transpile the resulting JS code with Babel
* I use Babel's preset-env
* Babel loads a plugin, plugin-proposal-async-generator-functions, which uses @babel/template which creates a stack trace by throwing and catching an Error (inside a function called `extendedTrace`).
* When this happens, source-map-support's `prepareStackTrace` method is called, since source-map-support is used by ts-node.
* source-map-support encounters coffeescript.js in the call stack (since the Error is thrown inside Babel which is invoked from CoffeeScript).
* coffeescript.js contains code for emitting source maps, so it contains code that matches the regular expression used by `retrieveSourceMapURL`.
* `retrieveSourceMapURL` extracts the following source map from coffeescript.js: "zw(u�"
* This string is passed to source-map which tries to parse it as JSON in `parseSourceMapInput`.
* At this point, bad things happen. :-)
I created a git repo that demonstrates the problem: https://github.com/provegard/sourcemap-bug
Clone it, run `npm install` and then `npm test`. It produces the following output:
```
undefined:1
zw(u�
^
SyntaxError: Unexpected token z in JSON at position 0
at JSON.parse ()
at Object.parseSourceMapInput (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\node_modules\source-map\lib\util.js:433:15)
at new SourceMapConsumer (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\node_modules\source-map\lib\source-map-consumer.js:17:22)
at mapSourcePosition (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\source-map-support.js:190:14)
at wrapCallSite (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\source-map-support.js:358:20)
at C:\kod\projects\sourcemap-bug\node_modules\source-map-support\source-map-support.js:399:26
at Array.map ()
at Function.prepareStackTrace (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\source-map-support.js:398:30)
at prepareStackTrace (internal/errors.js:30:29)
at process.emit (C:\kod\projects\sourcemap-bug\node_modules\source-map-support\source-map-support.js:457:52)
at process._fatalException (internal/process/execution.js:146:25)
```
If I modify retrieveSourceMapURL to print `lastMatch`, I get:
```
[
'//# sourceMappingURL=data:application/json;base64,${encoded}`;',
'data:application/json;base64,${encoded}`;',
undefined,
index: 8757,
```
Versions:
* Node v12.5.0
* npm 6.9.2
* source-map-support: 0.5.13
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia eseguendo con npm test la riproduzione collegata di sourcemap-bug, quindi esamina retrieveSourceMapURL e parseSourceMapInput in source-map-support.js. Traccia come viene estratto il match di coffeescript.js e passato a source-map; il lavoro è completato quando la riproduzione non genera più il JSON SyntaxError e le source map valide continuano a funzionare.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- coffeescript, javascript, node.js
- Ambito
- devtools
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100