search

googlearchive / web-push-encryption

[Deprecated] Encryption Utilities for Web Push protocol
Apache License 2.0
84 stars 23 forks source link

'web-push-encryption' is not in the npm registry #20

Closed owencm closed 8 years ago

owencm commented 8 years ago

Weirdly I'm getting an error that this package doesn't exist in the NPM registry... Any ideas?

ikornaselur commented 8 years ago

While the solution would be to have the package published (or fix the readme if it's published under another name), what I've done so far was just to install it directly from Github.

npm install github:googlechrome/push-encryption-node --save

The package might change name based on #16 though, so I guess we should keep an eye out for when it's finally published into the NPM registry.

wibblymat commented 8 years ago

It's possible I never actually published it :s

Will check, and publish if not. On Fri, 1 Apr 2016, 11:33 Axel Örn Sigurðsson, notifications@github.com wrote:

While the solution would be to have the package published (or fix the readme if it's published under another name), what I've done so far was just to install it directly from Github.

npm install github:googlechrome/push-encryption-node --save

The package might change name based on #16 https://github.com/GoogleChrome/push-encryption-node/issues/16 though, so I guess we should keep an eye out for when it's finally published into the NPM registry.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/GoogleChrome/push-encryption-node/issues/20#issuecomment-204342759

wibblymat commented 8 years ago

Definitely published now, sorry about that!

On Fri, 1 Apr 2016 at 11:46 Mat Scales mscales@google.com wrote:

It's possible I never actually published it :s

Will check, and publish if not. On Fri, 1 Apr 2016, 11:33 Axel Örn Sigurðsson, notifications@github.com wrote:

While the solution would be to have the package published (or fix the readme if it's published under another name), what I've done so far was just to install it directly from Github.

npm install github:googlechrome/push-encryption-node --save

The package might change name based on #16 https://github.com/GoogleChrome/push-encryption-node/issues/16 though, so I guess we should keep an eye out for when it's finally published into the NPM registry.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/GoogleChrome/push-encryption-node/issues/20#issuecomment-204342759