Project structure used to be, like, a big blob of sadness with everything in the same git repo; now, each component is in its own repository, and they get published to crates.io automagically on version tagged commits.
The main repo, seax, has the command-line app for invoking the compiler and running binaries and stuff. It's probably the least well-developed component, I haven't put a lot of work into it yet. It depends on pretty much everything else.
seax_util is utility stuff that pretty much everything else depends on. It's got the VM's instruction and data types (which were just moved here moved from the VM crate), stuff for encoding and decoding bytecode files, and some reusable stuff for compilers, including traits for AST nodes and a symbol table implementation. Eventually I'd like to write multiple compilers targeting the VM (I'd love some kind of ML, or a toy Haskell...), so that code will eventually get used in multiple places, I hope.