Unexpected token / in JSON at position 128

Question

Unexpected token / in JSON at position 128

Closed this issue 7 years ago · 8 comments

Use case:
Right click on the component and generate component test
Result:
Unexpected token / in JSON at position 128

Answer 1 · 2017-11-14T23:20:49.000Z

Please include the component (remove anything not needed to reproduce the error).

On Nov 14, 2017 4:18 PM, "nirolivier" ***@***.***> wrote: Use case: Right click on the component and generate component test Result: Unexpected token / in JSON at position 128 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#20>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AED31tLFJBY9okxhKoZ3UB3eQTM37OYGks5s2h-8gaJpZM4QeJkI> .

Answer 2 · 2017-11-16T18:56:01.000Z

Hello,
Please, find the attachments below.
Environment:

visual studio code v 1.18.0
Node 7.9.0
arch: ia32
Thanks,

login.component.ts.zip
login.zip

Answer 3 · 2017-11-16T21:24:59.000Z

I can't repro it =(

This seems related to #21 - My best guess is that it's an encoding or an invisible character. Try what I suggested there and let me know.

Answer 4 · 2017-11-17T20:22:34.000Z

I think it's an issue with package.json or tslint.json (where the formatting rules are read). Can you attach both files?

Answer 5 · 2017-11-21T13:57:10.000Z

I am getting the same thing but on line 764. Would love to be able to use this extension! My package.json and tslint are all valid JSON.

Answer 6 · 2017-11-21T14:04:41.000Z

Please attach the json files anyway, It's the only place I can think of which can cause the error.

…

On Tue, Nov 21, 2017 at 6:57 AM, Joshua Godi ***@***.***> wrote: I am getting the same thing but on line 764. Would love to be able to use this extension! My package.json and tslint are all valid JSON. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AED31uzcP2js5ixd5kQJglRIb4tqkqTXks5s4ta2gaJpZM4QeJkI> .

Answer 7 · 2017-12-01T13:52:20.000Z

I had this issue as well. I noticed that I had put comments in the tslint.json file. Once I removed them it worked again.

Answer 8 · 2017-12-01T17:15:18.000Z

This is fixed on v0.18.1
Thanks @kpaxton