The idea behind is that, if set to true, the oc-client will be compiled and served from the registry, and it will include all the templates registered on the registry (the ones you add on the templates option of your config). So when calling your-registry/oc-client/client.js, you will get a client with the templates your registry has registered. It has the penalty of not being accessed through CDN, but you can put one in front of the endpoint if you wanted
This adds a new option for the registry config
compileClient?: booleanThe idea behind is that, if set to true, the oc-client will be compiled and served from the registry, and it will include all the templates registered on the registry (the ones you add on the
templatesoption of your config). So when calling your-registry/oc-client/client.js, you will get a client with the templates your registry has registered. It has the penalty of not being accessed through CDN, but you can put one in front of the endpoint if you wanted