deno compile tree-shaking
hey. when using
specifically, if i perform an import such as
deno compiledeno compile to produce a single binary, is there any tree-shaking performed?specifically, if i perform an import such as
import * as yaml from "@std/yaml";import * as yaml from "@std/yaml"; and then only use yaml.parseyaml.parse and yaml.stringifyyaml.stringify from the module, will the end bundle include the rest of the module, or only those two plus any dependencies?
