Introducing component-level API versioning for LWC in Winter '24, allowing for backward compatibility, new functionality, and improvements in the framework. API versioning enables components to coexist on the same page and gives component authors the ability to choose different versions for different components.
Table of contents
The problem of versioningEnter API versioningThe impact of API versioningHow to upgrade your component API versionWhich version of LWC should I use for my Jest and local tests?SummaryResourcesAbout the authorsSort: