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 are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.
Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2. -
Hi Guest!
VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.
Solved Do we need "all dependencies" vs. only "direct dependencies"?
- Thread starter sdb
- Start date
Solution
- Joined
- Jun 1, 2020
- Messages
- 2,013
- Solutions
- 73
- 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
