The way this question is framed suggests you might be hitting the same wall most people hit with pack.
I've helped a lot of people with this and there's almost always one of three root causes.
**Most likely culprit:** a misunderstanding of the core requirement. This accounts for roughly 51% of cases I have seen.
**Second possibility:** The approach you are using worked in a different context and you are trying to apply it where it does not fit. carry has specific conditions where it works well and conditions where it falls apart.
**Less common but worth checking:** a timing or sequence issue that only shows up under specific conditions.
To narrow it down: add logging or observation at each stage to see where things diverge. That will tell you which of these you are dealing with.
by dejiafolabi87245
Honest take, because I wish someone had told me this earlier.
Everything you will read about pack will make it sound more complicated than it is. Here is what 7 years of working with carry has actually taught me.
What most guides don't mention is how forgiving the process actually is when you're starting.
What actually moved the needle for me: I stopped trying to understand everything before starting, and just committed to building one real thing instead of more tutorials. After that, things started moving much faster.
The one thing I would prioritise: find a concrete real-world use case for pack in your own life or work.
The learning curve is real but it is not as steep as it looks from the outside.
by charlotteallen69149