New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

pusher-platform-node

Package Overview
Dependencies
Maintainers
1
Versions
25
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

pusher-platform-node - npm Package Versions

23

0.15.0

Diff

Changelog

Source

0.15.0 - 2018-10-31

Changes

  • useQueryString is now an optional property of RequestOptions and defaults to false
  • The npm package has been tidied up to only include what is required
  • Removed body-parser as a dependency as it's not required
pusherapp
published 0.14.1 •

pusherapp
published 0.14.0 •

Changelog

Source

0.14.0 - 2018-09-18

Changes

  • Breaking: An instance of SDKInfo is now required when instantiating an instance of BaseClient. This can either be directly provided to the BaseClient and then the base client provided to an instance of Instance in the client key or the options object that Instances initializer takes, or you can provide the SDKInfo instance to the Instance initializer in the sdkInfo key of its options parameter
  • Removed defaulting to generating a JWT with the su: true claim if no JWT is provided to a call to request
pusherapp
published 0.13.2 •

Changelog

Source

0.13.2 - 2018-08-17

Additions

  • RequestOption now exposes a useQuerystring attribute that can be used to specify if query-string library should be used to parse query string
pusherapp
published 0.13.1 •

Changelog

Source

0.13.1 - 2018-07-25

Changes

  • Bump verion of jsonwebtoken
pusherapp
published 0.13.0 •

Changelog

Source

0.13.0 - 2018-04-19

Additions

  • authenticateWithRefreshToken has been added if you want to support the refresh_token grant type and return refresh tokens as part of the authentication process

Changes

  • authenticate no longer returns a refresh_token and no longer accepts the refresh_token grant type
  • Calls to authenticate and authenticateWithRefreshToken always return an AuthenticationResponse that looks like this:
{
  status: number;
  headers: Headers;
  body: TokenResponse | ErrorBody;
}

where:

  • status is the suggested HTTP response status code,
  • headers are the suggested response headers,
  • body holds either the token payload or an appropriate error payload.

Here is an example of the expected usage, simplified for brevity:

app.post('/', function (req, res) {
  const authPayload = pusher.authenticate(req.body, {});
  res.status(authPayload.status).send(authPayload.body);
});
pusherapp
published 0.12.1 •

Changelog

Source

0.12.1 - 2018-04-05

Fixes

  • Issuer check in refresh token validation now checks that the issuer starts with api_keys/, not keys/
pusherapp
published 0.12.0 •

Changelog

Source

0.12.0 - 2018-03-29

Changes

  • grant_type is now required in AuthenticatePayload
  • AuthenticatePayload is now exported from index.js
pusherapp
published 0.11.1 •

Changelog

Source

0.11.1 - 2018-01-26

Changes

  • Tokens now use instance claim instead of app claim
pusherapp
published 0.11.0 •

Changelog

Source

0.11.0 - 2018-01-26

Changes

  • Added support for custom token expiry with a tokenExpiry key in AuthenticateOptions
  • Removed all mention of tokenLeeway
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc