Error in jsconfig.json

[JoePShoulak]

I updated VS Code and afterward noticed that VS Code was reporting errors in my jsconfig.json file. I usually notice that sort of thing, so I checked another project, and it's reporting the same error (when I don't think it did before).

File 'c:/Users/joeps/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.d.ts' not found. The file is in the program because: Default library for target 'es3'

This error is shown (9 times, for some reason).

Maybe there was a change to the pathing in the latest update?

[antiboredom]

Hi - I'm not getting this but I am also on a mac, and wondering if this might be a bug I introduced in windows only. Can you send me a sample jsconfig.json file?

[JoePShoulak]

Absolutely, it looks like this:

{
  "include": [
    "*.js",
    "**/*.js",
    "c:\\Users\\joeps\\.vscode\\extensions\\samplavigne.p5-vscode-1.2.12\\p5types\\global.d.ts"
  ]
}

[antiboredom]

Thanks! Can you replace all of the double slashes with a single slash (except for the two after “c:”) and let me know if that fixes it?

[JoePShoulak]

I believe that fixes it! No errors!

[antiboredom]

Great. I‘ll try to push a fix in the next day or so. Thanks for posting the issue and your help in debugging it!

[JoePShoulak]

My pleasure! I can't image using p5 in VS Code without the intellisense that your extension provides, this is the least I can do in return!

[JoePShoulak]

Hmm, I may have been wrong. This is an error I'm getting with the corrected pathing:

{
  "include": [
    "*.js",
    "**/*.js",
    "c:\\Users/joeps/.vscode/extensions/samplavigne.p5-vscode-1.2.12/p5types/global.d.ts"
  ]
}

[chanbinna]

I am on Mac and I am having same issue too

[antiboredom]

well, I'm getting the error now too!

[antiboredom]

I think some update to vscode has changed things. Can you both try adding this to your jsconfig.json files:

  "compilerOptions": {
    "target": "es6",
  },

[antiboredom]

Hi - just pushed the changes that I think should fix things - make sure to update the extension (or let it happen automatically) and then let me know if it fixes the issue! Thanks for your patience...

[JoePShoulak]

Looks like that did it for me!

[antiboredom]

Great - closing the issue now…