You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This morning, I am going through my weekly process of updating dependencies on my projects. Of those projects, one uses the Pubnub Chat SDK.
This morning, running npm outdated indicated a release of @pubnub/chat (v0.9.1). After updating the package, I experienced various errors from webpack related to transitive dependencies (crypto) webpack v5 no longer automatically bundles. Taking the advised steps to define a "fallback" for webpack did not work:
Upon looking closer into the 0.9.1 release of the JS Chat SDK, I noticed that the metadata on npmjs.org/packages/@pubnub/chat now points to this repo, rather than github.com/pubnub/js-chat repo:
The text was updated successfully, but these errors were encountered:
This morning, I am going through my weekly process of updating dependencies on my projects. Of those projects, one uses the Pubnub Chat SDK.
This morning, running
npm outdated
indicated a release of@pubnub/chat
(v0.9.1
). After updating the package, I experienced various errors from webpack related to transitive dependencies (crypto
) webpack v5 no longer automatically bundles. Taking the advised steps to define a "fallback" for webpack did not work:Upon looking closer into the
0.9.1
release of the JS Chat SDK, I noticed that the metadata on npmjs.org/packages/@pubnub/chat now points to this repo, rather than github.com/pubnub/js-chat repo:The text was updated successfully, but these errors were encountered: