Consider scraping off the AST

[PaulRBerg]

Problem

Including the ast field (Abstract Syntax Tree) in the contract artifacts leads to large NPM package sizes, i.e., 4.7mB for @sablier/v2-core. And it's also an issue of noise - the AST in the LockupDynamic artifact makes up for ~21k lines from a total of 26k lines in the JSON.

On the flip side, the AST may be useful for static analysis and developer tooling support (since tools could reconstruct the original code by walking up the AST).

No good solution comes to mind, so I suggest keeping ast as is for the time being. It's also the past of least resistance because we wouldn't have to modify the prepare-artifacts.sh script. However, we can circle back on this topic if it turns out to be a problem for integrators (e.g. if the large number of lines in the JSON impairs the DX).

External Conversations

• ChatGPT
• Foundry Support

Package Size Comparison

Package	Version	Size
@sablier/v2-core	1.0.0-rc.0	4.7mB
@uniswap/v3-core	1.0.1	426kB
@ethers	6.6.2	11.7mB

[PaulRBerg]

Closing due to competing priorities.