hardfist
hardfist
@jtsorlinis try `RSPACK_PROFILE=TRACE=layer=logger rspack build`
> Can't see any errors even with trace enabled, it seems to just stop and then timeout. Not sure if the logs will help. > > I've attached the last...
> Hi [@hardfist](https://github.com/hardfist), > > Trying with `RSPACK_PROFILE=OVERVIEW` seems to produce very similar levels of logging as `RSPACK_PROFILE=TRACE` > > In other news, the build hangs and times out consistently...
@benjdlambert does deadlock happens in backstage? if it's open source I can debug in your repo, honestly it's not easy to debug deadlock problems right now, we're still investigating better...
thanks it maybe related to performance regression, block_on fs binding will cause huge performance regression I think the biggest blocker now is rspack_resolver doesn't use async_fs, which cause it has...
> yeah, I also suspect the performance regression, but cannot prove it. I actually tried it before and revert cause huge performance regression introduced, you can test it in project...
> I'm afraid we cannot merge this PR now, because compiler.inputFileSystem has been set by default. that's easy, you can just ignore the inputFileSystem in the rust side, it's actually...
> I disabled `inputFileSystem` on the js side in this PR. > > I also created another branch and cherry-picked the refactor commits. maybe #8654 is exactly what you expect....
It seems we(Rspack) can make a rspack plugin which calls deno_resolver to make it work