pkger is very slow for large repos, even though including just one file

[tian000]

I am working in a large monorepo, and would like to run pkger to package just 1 config file. The go.mod file is at the repo root. It takes around 5 minutes because I think it is scanning all the folders to grab folder metadata. Is there a way to make pkger faster for packaging just 1 file in a very large repo?

[aeneasr]

We're experiencing the same issue

[lagren]

We are also experiencing this in our monorepo. It is structured as a single go module and contain 204 packages/folders. Seems like each folder takes 0.5s to process which makes this really slow.

[tuhao1020]

Is there any solution to imporove this problem?

[sagikazarmark]

I opened #128 with this issue in mind. I've looked into it, but pkger depends heavily on go list and modules, which makes it easy to use, but less suitable for large projects I guess.