Socket
Socket
Sign inDemoInstall

json-rpc-engine

Package Overview
Dependencies
Maintainers
6
Versions
36
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

json-rpc-engine - npm Package Versions

234

6.1.0

Diff

Changelog

Source

[6.1.0] - 2020-11-20

Added

  • Add PendingJsonRpcResponse interface for use in middleware (#75)

Changed

  • Use async/await and try/catch instead of Promise methods everywhere (#74)
    • Consumers may notice improved stack traces on certain platforms.
rekmarks
published 6.0.0 •

Changelog

Source

[6.0.0] - 2020-11-19

Added

  • Add docstrings for public JsonRpcEngine methods (#70)

Changed

  • (BREAKING) Refactor exports (#69)
    • All exports are now named, and available via the package entry point.
    • All default exports have been removed.
  • (BREAKING) Convert asMiddleware to instance method (#69)
    • The asMiddleware export has been removed.
  • (BREAKING) Add runtime typechecks to JsonRpcEngine.handle(), and error responses if they fail (#70)
    • Requests will now error if:
      • The request is not a plain object, or if the method property is not a string. Empty strings are allowed.
      • A next middleware callback is called with a truthy, non-function parameter.
  • Migrate to TypeScript (#69)
  • Hopefully improve stack traces by removing uses of Promise.then and .catch internally (#70)
  • Make some internal JsonRpcEngine methods static (#71)
rekmarks
published 5.4.0 •

Changelog

Source

[5.4.0] - 2020-11-07

Changed

  • Make the TypeScript types not terrible (#66, #67)
rekmarks
published 5.3.0 •

Changelog

Source

[5.3.0] - 2020-07-30

Changed

  • Response object errors no longer include a stack property
rekmarks
published 5.2.0 •

Changelog

Source

[5.2.0] - 2020-07-24

Added

  • Promise signatures for engine.handle (#55)
    • So, in addition to engine.handle(request, callback), you can do e.g. await engine.handle(request).

Changed

  • Remove async and promise-to-callback dependencies
    • These dependencies were used internally for middleware flow control. They have been replaced with Promises and native async/await, which means that some operations are no longer eagerly executed. This change may affect consumers that depend on the eager execution of middleware during request processing, outside of middleware functions and request handlers.
      • In general, it is a bad practice to work with state that depends on middleware execution, while the middleware are executing.
rekmarks
published 5.1.8 •

rekmarks
published 5.1.6 •

danfinlay
published 5.1.5 •

kumavis
published 5.1.4 •

kumavis
published 5.1.3 •

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