JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
There's a step called analyzeDependencies which is just a method in the Rome compiler that does some single-file static analysis. It's super cachable and includes stuff like if it uses top level await, where are imports used for the first time (cycle detection) etc
You could encode some information in there, such as if the module didn't have any side effects, only exported types etc. Then you can reunify those artifacts later when constructing the actual dependency graph.
Could you use this step to encode a list of imports/exports to later do dead code elimitation of unused exports?
Yeah, that information is already collected. It's used currently to validate the existence of imports. It's also used to "resolve" complete locations when building a flat bundle. This is the current analyzeDependencies interfacehttps://gist.github.com/sebmck/33ad6649edcb3e8f19a641e16eee1a86 …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
i was just curious if Rome did some kind of pre-analysis of dependencies before building the graph