Bug: JSON AST view is not updated when the source changes after an error

[fasttime]

What browser did you use to see problem?

Chrome and Firefox

What did you do?

In Code Explorer I chose the JavaScript language and switched to JSON AST view.

In the source panel on the left, I entered a bigint, e.g. 2n. Then I deleted it again.

The panel on the right shows an error because the AST is not serializable, which is fine, but the error remains even if the source is modified to remove the unserializable bigint.

Example

What did you expect to happen?

The error in the right panel should disappear when the source is edited and the AST becomes serializable.

What actually happened?

The error remains even when the source is changed.

Participation

• I am willing to submit a pull request for this issue.

AI acknowledgment

• I did not use AI to generate this issue report.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

Additional comments

No response

[DMartens]

I am able to reproduce this.
The problem seems to be that we stringify any AST here.
I think we should guard against a potential thrown error from JSON.stringify,
but should we add a dependency for the serialisation or use the replacer argument of JSON.stringify?
JSON.stringify throws in two cases:

• circular references
• BigInt values

As such I think we should just replace the BigInt values as circular references should not happen with the current languages (and would be caught in the added error handler).