Update @worldware/msg-react so its declared dependency on @worldware/msg requires 0.11.0 (semver range ^0.11.0).
User story
As a msg-react consumer (and as a maintainer), I want @worldware/msg-react to peer-depend on @worldware/msg@^0.11.0, so apps align with the current msg release and avoid resolving an older incompatible peer.
What to change
package.json peerDependencies["@worldware/msg"] → ^0.11.0package.json devDependencies["@worldware/msg"] → ^0.11.0 (keep local/CI tooling on the same major/minor floor as the peer)- Refresh
package-lock.json via npm install so the lockfile resolves @worldware/msg@0.11.0 (or compatible)
Acceptance criteria
- Peer and dev ranges both declare
^0.11.0
- Lockfile installs a 0.11.x
@worldware/msg
npm test, npx tsc --noEmit, and npm run build still pass
Out of scope
- API or component behavior changes unrelated to the dependency bump
- Publishing a new msg-react release (unless release automation already covers it on merge to
main)
Update
@worldware/msg-reactso its declared dependency on@worldware/msgrequires 0.11.0 (semver range^0.11.0).User story
As a msg-react consumer (and as a maintainer), I want
@worldware/msg-reactto peer-depend on@worldware/msg@^0.11.0, so apps align with the current msg release and avoid resolving an older incompatible peer.What to change
package.jsonpeerDependencies["@worldware/msg"]→^0.11.0package.jsondevDependencies["@worldware/msg"]→^0.11.0(keep local/CI tooling on the same major/minor floor as the peer)package-lock.jsonvianpm installso the lockfile resolves@worldware/msg@0.11.0(or compatible)Acceptance criteria
^0.11.0@worldware/msgnpm test,npx tsc --noEmit, andnpm run buildstill passOut of scope
main)