Handling large, sensitive JSON files fully in the browser. What edge cases should I watch for?
by•
I’m building JsonExport, a JSON to Excel/CSV converter that runs entirely in the browser.
The main motivation was privacy and scale. I kept running into tools that required uploading sensitive logs or customer data, or that completely fell apart once nested JSON or larger files were involved.
I decided to go fully client-side using streaming parsers and Web Workers, which has worked surprisingly well so far, even with very large files.
I’m curious. For those of you who work with messy or sensitive JSON:
What usually breaks first in tools like this?
Are there edge cases you’ve been burned by before?
Anything you would expect but rarely see done right?
Not here to pitch. Genuinely looking for feedback before launch.
13 views
Replies
Good day, guys!
Project Lead here.
We have an hour or so until launch time. Can't wait to hear from you all.
In the meantime, if you would like to contribute to the development of this product, you can follow up on the Github link.
Yeah, it's 100 percent Open Source.
Let's get this party started, fixing your messy JSON data.
You will never have to worry about what you would do with that Salesforce JSON data that looks like gibberish.