Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

dyno

Package Overview
Dependencies
Maintainers
30
Versions
56
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dyno - npm Package Versions

23
6

1.4.1

Diff

mcwhittemore
published 1.4.0 •

Changelog

Source

v1.4.0

  • updates aws-sdk dependency to 2.x to help reduce the weight of the aws-sdk in your bundle
tcql
published 1.3.0 •

Changelog

Source

v1.3.0

  • updates aws-sdk dependency to v2.7+ from v2.1+
yhahn
published 1.2.1 •

Changelog

Source

v1.2.1

  • fixes a bug where certain errors were not handled correctly by .batchWriteAll()
mcwhittemore
published 1.2.0 •

Changelog

Source

v1.2.0

  • adds .batchGetAll() and .batchWriteAll() methods
  • adds autopagination to .query() and .scan() methods via a Pages parameter.
  • fixes a bug in the cli which prevented export --> import roundtrips
rclark
published 1.1.0 •

Changelog

Source

v1.1.0

  • adds dyno.putStream(), a writable stream to batch individual records into BatchWriteItem requests
  • bug fixes in cli
rclark
published 1.0.1 •

Changelog

Source

v1.0.1

  • fixes a bug in converting JavaScript arrays to DynamoDB Sets if the first item in the array is falsy (e.g 0)
rclark
published 1.0.0 •

Changelog

Source

v1.0.0

The overarching goal is to prefer to utilize the aws-sdk commands where possible, inheriting their bug fixes, updates, and documentation. Some aspects of dyno's API are really nice (e.g. .getItem(key) instead of .getItem({ Key: key })), but having documentation that we don't have to maintain is arguably better.

generally speaking

... the big changes are:

  • "dyno-style" function arguments, conditions, and options go away. Instead all function arguments are as described for the aws-sdk's document client.
  • dyno navigates the differences between the aws-sdk's regular client and document client for you behind the scenes.
  • with the exception of explicit stream functions, none of the function calls fan out into multiple HTTP requests. It doesn't handle pagination, it doesn't split large batch requests into a series of acceptably-sized requests, and it doesn't attempt to retry errors. Configuring when and how errors are retried becomes the client's responsibility using aws-sdk's mechanisms.

breaking changes

  • client configuration requires you to provide a table name
  • dyno.getItems renamed to dyno.batchGetItem, as a passthrough to aws-sdk.
    • no longer accepts an array of keys and optional options object. See aws-sdk docs for parameters
    • does not allow you to request more than 100 items per function call
    • does not provide a readable stream of response records
  • dyno.deleteItems and dyno.putItems replaced by dyno.batchWriteItem, a passthrough to aws-sdk.
    • no longer accepts an array of items to put / keys to delete and optional options object. See aws-sdk docs for parameters
    • does not allow you to write > 25 items or 16 MB per function call
  • dyno.deleteItem becomes a passthrough to aws-sdk. No longer accepts a key and optional options object. See aws-sdk docs for parameters
  • dyno.getItem becomes a passthrough to aws-sdk. No longer accepts a key and optional options object. See aws-sdk docs for parameters
  • dyno.putItem becomes a passthrough to aws-sdk. No longer accepts a record and optional options object. See aws-sdk docs for parameters
  • dyno.updateItem becomes a passthrough to aws-sdk. No longer accepts a key, "dyno-style" update definition and optional options object. See aws-sdk docs for parameters
  • dyno.query becomes a passthrough to aws-sdk.
    • no longer accepts the "dyno-style" query conditions and optional options object. See aws-sdk docs for parameters
    • does not paginate through the reponse for you. Pagination can be accomplished manually or via aws-sdk's functions.
    • does not provide a readable stream of response records
  • dyno.scan becomes a passthrough to aws-sdk.
    • no longer accepts an optional options object. [aws-sdk docs for parameters](See http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/DocumentClient.html#scan-property)
    • does not paginate through the response for you. Pagination can be accomplished manually or via aws-sdk's functions
    • does not provide a readable stream of response records
  • drops dyno.estimateSize
  • drops all kinesis-related functionality

new functions

  • dyno.queryStream provides a readable stream of query responses. Parameters passed to the function are identical to dyno.query, but the function returns a readable stream that will paginate through results as you read from it.
  • dyno.scanStream provides a readable stream of scan responses. Parameters passed to the function are identical to dyno.scan, but the function returns a readable stream that will paginate through results as you read from it.
  • dyno.batchWriteItemRequests provides an array of AWS.Request objects representing BatchWriteItem requests. Parameters passed to the function are identical to dyno.batchWriteItem, except that there is no size/count limit to the number or write requests you may provide.
  • dyno.batchGetItemRequests provides an array of AWS.Request objects representing BatchGetItem requests. Parameters passed to the function are identical to dyno.batchGetItem, except that there is no size/count limit to the number or get requests you may provide.
rclark
published 1.0.0-beta.3 •

rclark
published 1.0.0-beta.2 •

23
6
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