Hi, @vadjs! Thank you for submitting this and the corresponding PR. 🙇

Admittedly, I'm not seeing the initial value in changing dependencies to peer dependencies - the idea of the dependencies is that we want these listed packages to be run when npm install is run. With peerDependencies, it appears that NPM will not attempt to install peer dependencies when doing npm install. This is because NPM expects these dependencies to be provided by other dependencies.

Since this is a public framework widely available for use, I think the preference would be to enforce the dependencies with the dependencies key rather than peerDependencies. Also, some of the dependencies require pinned or specific versions to ensure compatibility with Bolt JS, which peerDependencies would not enforce as it would support overriding package versions as you mentioned.

With that being said, I would love to get your thoughts on this and see if there's a specific use case I've been missing!