Root UI and json imports

[MrWook]

Hey,

I recently tested Sonda with one of my larger projects using Nuxt and noticed a couple of things that could enhance the experience:

Root View for Bundled Files:
Other analytic tools often have a root view where all bundled files are displayed together, typically sorted from left to right by size. This makes it easier to quickly identify large files and focus on optimizing them. With Sonda, I had to manually click through each of my 56 files, which was time-consuming. A similar overview in Sonda would be incredibly helpful.

Unassigned Parts and JSON Imports:
I noticed several [unassigned] parts in the analysis, and after comparing the output with Nuxt’s native analyzer, it seems these might correspond to .json imports. Including the filename or file extension for these [unassigned] parts would make it easier to identify them and understand their impact.

[filipsobol]

Hi, thanks for the feedback.

I'm working on a complete UI redesign and “Root View for Bundled Files” is already done. There will be many other improvements that will make inspecting large builds much easier. If all goes well, the 0.8.0 release will be massive.

Sonda works by inspecting source maps, and [unassigned] means that a particular part of the bundle doesn't have any mappings to the original code. This is described in the documentation, which also mentions how to investigate it further. I'm curious if these parts are JSON imports, code comments, or something else.