Unity Packages: From WTF to FTW With Needle Tools
summary
Needle runs ~23 packages (agency has ~40) and relies on registries (Unity ~250 public, OpenUPM ~1800). Built a package tools extension that shows editable vs immutable packages, adds changelog checks and publisher helpers, and an installer with ~50,000 installs. Runs a mirror that syncs Unity registry packages to GitHub so changes are diffable (Addressables forked 39 times). Uses Verdaccio-based registries, supports NPM/JWT auth via credential UI, offers hybrid packages for asset-store shipping and a package playground using file: package references across multiple Unity versions.
AI-written summary · about
chapters (22)
- 0:00Unity packages intro
- 1:18Unity packages 2018 changes
- 3:47Package structure basics
- 6:13Project manifest & lock files
- 7:18Making packages editable
- 10:07First custom package
- 12:35Needle Tools for packages
- 15:46How Unity package system works under the hood
- 18:16Registry metadata & versions
- 20:23Needle’s package mirror
- 25:39Publishing packages
- 27:24Setting up your own package registry
- 31:20Install from registries & Git
- 35:14Hybrid packages bridge
- 37:27Package installer service
- 40:17Registry auth for private packages
- 41:39Hybrid package benefits
- 43:26Test packages across Unity
- 48:04Production package composition
- 54:28Managing dependencies
- 56:18Dependency graph visualization
- 1:00:15Summary & Q&A
related talks
46mUnity Tech for Indies
45mTop 10 Unity Assets That Every Project Should Use
55mLet's Make Unity Great Again
51mEmpowering Design: The Tools and Pipelines of Unpacking
56mUnity for the enterprise developer
43mScaling Indie - Making Bigger Games With Unity
33mVersion control for game developers
55mSo You're Trying to Support a Medium Sized Studio....