Now Highstate only supports local backend deployment which is also bound to the local library.
The local library means that all instances of all projects use the same set of components/entities defined by packages installed in the nodejs project where Highstate is launched. This local library also includes all user-defined library packages defined in the monorepo.
In order to support other deployment types (like self-hosting Highstate on own server, or even managed cloud installation) we obviously need to virtualize library and enable users to create sets of packages (with versions pinned) which will be used by their projects. Each of such set is called virtual library and is the subject of this feature.
Now Highstate only supports local backend deployment which is also bound to the local library.
The local library means that all instances of all projects use the same set of components/entities defined by packages installed in the nodejs project where Highstate is launched. This local library also includes all user-defined library packages defined in the monorepo.
In order to support other deployment types (like self-hosting Highstate on own server, or even managed cloud installation) we obviously need to virtualize library and enable users to create sets of packages (with versions pinned) which will be used by their projects. Each of such set is called virtual library and is the subject of this feature.