When viewing packages in BrowserAssist, I see "Direct Dependencies" and "All dependencies". Should I aim to fill in the latter, or is former enough? Trying to not clutter my folder too much and would prefer the former if not an issue - any insight would be appreciated. Thank you.
-
Hi Guest!
We have posted a new VaM2 dev log on Patreon, starting a monthly cadence of written progress updates between Beta releases. Highlights include the new Gizmos System, Selection Carousel, and Modes System with Context-Specific Editing. Beta1.2 is 15 of 21 items complete.
Read the full post on Patreon, or follow progress on the public Trello roadmap.
Solved Do we need "all dependencies" vs. only "direct dependencies"?
- Thread starter sdb
- Start date
Solution
- Joined
- Jun 1, 2020
- Messages
- 2,719
- Solutions
- 98
- Reactions
It is not enough : )
Unless you know exactly if a dependency does not need the sub-dependency, it's highly likely you will need them if you load the content from that specific dependency at some point.
But this is a situation you can test yourself. No one here can tell you what you wanna keep or what you don't wanna keep. Test the direct, if buggy, then grab all.
Unless you know exactly if a dependency does not need the sub-dependency, it's highly likely you will need them if you load the content from that specific dependency at some point.
But this is a situation you can test yourself. No one here can tell you what you wanna keep or what you don't wanna keep. Test the direct, if buggy, then grab all.
Upvote
0
Solution
