Forge and package dependencies
· 4 min read
In order to optimize Forge use, teams should avoid creating libraries from Forge components and should ensure that the components are kept up to date.
TL;DR
- Never set Forge as a dependency of a package. Set Forge as a peer dependency only.
- Always keep Forge within the same major version in all your apps and packages.
It's worth noting that this concept applies to any package that you want as a dependency of your library, but you want to allow for the consumer/dependent to control the version for compatibility with multiple versions of the library in question.