Hey 
We just upgraded the peer dependencies of ic-js and oisy-wallet-signer from the good old AgentJS stack (@dfinity/agent, @dfinity/principal, etc.) to the shiny new multi-entrypoint package @icp-sdk/core that was announced in this forum post.
What does this mean?
This is mostly a structural change, no behavior changes are expected.
However, since you’ll have to pull this peer dependency (or npm will do it automatically), we marked these as major releases to make the update loud and clear.
Updated packages 
:
@dfinity/ckbtc: v5.0.0@dfinity/cketh: v5.0.0@dfinity/cmc: v7.0.0@dfinity/ic-management: v8.0.0@dfinity/ledger-icp: v7.0.0@dfinity/ledger-icrc: v5.0.0@dfinity/nns: v11.0.0@dfinity/sns: v5.0.0@dfinity/utils: v4.0.0@dfinity/zod-schemas: v3.0.0@dfinity/oisy-wallet-signer: v2.0.0
Battle-tested
As always, we first migrated OISY and NNS dapp to these new packages to ensure quality before offically releasing. That’s why, we could recommend updating your imports to the @icp-sdk/core sub-path exports as well (migration guide).
If I may share my opinion, I think it’s a really neat pattern and, for what it’s worth, I’ve also started migrating the Juno ecosystem, so as far as I’m concerned: this is the way 
.
Coming next
We also plan to ship the ic-js canisters library in the same multiple-entrypoint style in the near future. It’s actually already published on npm 
, but we’ll formally announce it once the documentation is finished.
That said, if you like to be adventurous and want to take an early look, you can already try the @icp-sdk/canisters library.
Questions?
Drop them below, happy to help or answer anything that’s unclear.