All modules exposed in @coremedia/studio-client.client-core-impl and @coremedia/studio-client.cap-rest-client-impl have been merged into @coremedia/studio-client.client-core and @coremedia/studio-client.cap-rest-client respectively keeping the path within the corresponding package intact. Please change usages (e.g. dependencies, imports) accordingly.

Examples

Old dependencies in package.json (assuming the migration to the catalog protocol has already been done):

{
  "dependencies": {
    ...
    "@coremedia/studio-client.cap-rest-client-impl": "catalog:,
    "@coremedia/studio-client.client-core": "catalog:",
    "@coremedia/studio-client.client-core-impl": "catalog:",
    ...
  }
}

New dependencies in package.json:

{
  "dependencies": {
    ...
    "@coremedia/studio-client.cap-rest-client": "catalog:,
    "@coremedia/studio-client.client-core": "catalog:",
    ...
  }
}

Old imports in example.ts

...
import { RemoteJobBase } from "@coremedia/studio-client.cap-rest-client-impl";
import { RemoteBean, ValueExpression } from "@coremedia/studio-client.client-core";
import { RemoteBeanImpl } from "@coremedia/studio-client.client-core-impl";
...

New imports in example.ts

...
import { RemoteJobBase } from "@coremedia/studio-client.cap-rest-client";
import { RemoteBean, RemoteBeanImpl, ValueExpression } from "@coremedia/studio-client.client-core";
...

Backward compatibility

When importing modules from their old location you will get the same import as when directly importing from the now location. This not only applies to code build inside the studio-client workspace but also applies to plugins and other precompiled code. This compatibility layer will be maintained for the whole CMCC13 lifecycle and removed afterwards.

This task is still marked as breaking as all blueprint packages have been adjusted accordingly.

(CMS-27952)