It is fun to develop and experience virtual worlds at home. Eventually though, you want the world to see your world. To do that, we need to package and publish our app. In the course of development, upgrades to React may come along; before publishing, you will need to decide whether you need to "code freeze" and ship with a stable version, or upgrade to a new version. This is a design decision.
At some point, you will need to upgrade, and you will need to publish. This chapter will explain how to do both as well as how to organize your code and check your dryer, and your code, for lint. We will cover these topics here:
- Types of upgrades: Rip and Replace or "Facelift" upgrade, or "Upgrade in place"
- How to ensure that proper versions of your components are present
- Development versus non-development versions, components, and libraries
- Distribution licenses
- Linking and embedding VR content
- Publishing to common web hosts and Content Delivery...