You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: