Version mismatch possible when using react wrapper

[craquet]

The react wrapper currently references the base package like this:

"@kit-data-manager/pid-component": "*"

This matches the recommendation of the stencil documentation. This makes it possible that the version of the react wrapper and the version of the stencil package drift apart, leading to broken builds. In my case, I was trying to install an older version of the react wrapper (assuming it would install the matching pid component base), which lead to me having react wrapper v0.1.6 and pid component v0.2.2. This broke the build because some imports in the react wrapper were no longer available in the pid component.

It would be ideal if we could pin the version number of the pid component in the react wrapper dependencies to an exact version, however it seems like this is not possible easily. For example, react wrapper v0.2.2 should depend strictly on pid component v0.2.2:

"@kit-data-manager/pid-component": "0.2.2"

If you also don't have a quick idea to solve this, I might add a small script to adapt the version number during build

[maximiliani]

You're right. This is definitely a problem. In any case, we have to sync it with somesy for correct MD. Could this be done in the CI, when creating a new release tag? Maybe this could be useful.