remove JSON5 dependency

[adhami3310]

The only reason we have as far as I can tell is NaN, Infinity, and -Infinity would not be parsed by JavaScript JSON.parse.

One potential solution is to make it such that the backend sends special strings for those values, that the frontend reinterpret those as their correct equivalence.

[ParagGhatage]

@adhami3310 ,
I think I can implement it, but it will take some time to check and make sure everything works correctly.
Could you please assign this to me?

[adhami3310]

@ParagGhatage well, there are structural issues right now, we would have to decide on what to sacrifice, this isn't so much of a technical issue as much as a discussion about what's the best approach

[ParagGhatage]

@ParagGhatage well, there are structural issues right now, we would have to decide on what to sacrifice, this isn't so much of a technical issue as much as a discussion about what's the best approach

@adhami3310 , Definitely - this is a big change and a core part of how Reflex functions.
I’d love to be part of the discussion.

I can prepare a short .md outlining how the data flow and components would work if we remove JSON5, along with possible approaches and trade-offs.
We can discuss the approaches mentioned in the file, tradeoffs, and once we align on a direction and finalize the end-to-end flow, I can start implementing.
Should I go ahead and create the .md proposal?

[linear]

ENG-9194

[masenf]

fixed by #6339