Unexpected output and possible memory leak

[Ravenstine]

It seems strange for these functions to be maintaining state and producing output that isn't expected from the given input.

For instance, manipulation of a string value results in the original input code when printed:

It appears that code is being kept in memory with seemingly no way to clear it and the span ranges used for each node are simply incremented:

So the only way I've figured out to properly print a manipulated AST is to manually increment all the start & end values:

Is this expected? I'm seeing this using deno 1.13.0.

[chrisdevereux]

Same here. I don't know the internals of swc at all, but wonder if this is related to the compiler instance being cached in swc_wasm/lib.rs