Upgrading Factor is easy. Normally it just involves upgrading your packages, but there are sometimes caveats.
Before You Upgrade
- Factor follows the semver standard for releases. All upgrades should be considered non-breaking, unless they are major updates; (and even then changes are typically minor breaking changes.)
- Before you upgrade, you may want to reference the changelog. This may explain any issues or functionality that may change once you've upgraded.
Upgrading with Yarn
Yarn typically does a better job than NPM of maintaining package consistency. However, if you run into issues, we recommend:
Consistent Upgrading with NPM
Updating in Package.json
package.json file is what specifies which version of Factor and its plugins should be installed. You can also manually update versions there if you prefer.
Understanding ^ in versions
Most versions in
package.jsonuse the (^) "caret" marker. This specifies that the package should be upgraded unless the package is a major release. Since major releases are the only "breaking" releases, this is why using the (^) makes sense