TypeScript tsconfig unable to parse comments

[risingBirdSong]

🐛 bug report

Description of the problem

import a project from my github (great feature!) that has a tsconfig complete with comments. But it looks like coding sandbox can't parse the comments.

Error -> We weren't able to parse: '/tsconfig.json': Parse error on line 2:
...erOptions": { /* Basic Options */
----------------------^
Expecting 'STRING', '}', got 'undefined'

How has this issue affected you? What are you trying to accomplish?

would like to be able to keep the comments, they're useful and are part of my repo. Fixing this will making importing from github repo more seamless.

Link to sandbox: link (optional)

(not the original repo but a simplified one only to demonstrate the problem)
https://codesandbox.io/s/fragrant-darkness-8zu6f?file=/tsconfig.json

Your Environment

| Software | Name/Version |
Windows 10 Home Version 2004 Build 19041
| Browser |
Same error in Microsoft Edge and Google Chrome

[risingBirdSong]

I didn't ever consider that the json that tsc --init produces isn't standard json but a special type called jsonc, c for comments. This jsonc file will fail a json validator and fails on codingsandbox.

https://www.reddit.com/r/typescript/comments/8na5vb/tsconfigjson_isnt_strict_json_what_now/

Here's a nice tool that will convert from jsonc to json
https://komkom.github.io/

It'd be nice for codingsandbox to automatically check for jsonc in tsconfig and either be able to handle jsonc out of the box, or convert to regular json. This would be good for users who are importing their projects from github. I would guess many users like myself bootstrap their ts with tsc --init which produces the jsonc.

[github-actions]

This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed.

[github-actions]

This issue has been automatically closed because there wasn't any activity after the previous notice or the stale label wasn't removed.