Yunfei He
Yunfei He
> Bundler API page is empty currently, so it's meaningless until someone can write a guidance, then we can have the page back. Yes. We could do this. > We...
I think this one is solved. Errors returned from rust or caught in Js would be displayed as it is. --- edited looks like there are much to be improved
> > looks like there are much to be improved > > Would you clarify this? I reopen it becuase of reqeust I saw in https://github.com/rolldown/rolldown/issues/2734. It seemed it was...
Notes: - Try remove the outer `Arc` in `Arc` Refs: - https://github.com/rolldown/rolldown/pull/5058
After investigation, let me clarify the issues - Calling `close` doesn't free the memory that's taken by `BundleOutput`. This's expected, because the `Bundler` doesn't have connections with returned `BundleOutput`. -...
Yes, similar. Because only `BundleOutput` has this problem. We gonna have an experimental API like ``` import { freeExternalMemory } from 'rolldown/experimental' const result = await rolldown.build({}); freeExternalMemory(result) result.xxx //...
Change priority to p3, because rolldown did release memory, but the timing is decided by the Nodejs's GC. We already provide a manual API for handling such scenario, not an...
> > but the timing is decided by the Nodejs's GC > > That was not my experience in the repro I provided though. In the repro, I explicitly call...
Block by oxc's solution on how identifying the same ast node between two visit.
Sometimes I miss javascript, you could add almost anything on a object/struct and get it back :).