Socket
Socket
Sign inDemoInstall

@aws-sdk/middleware-stack

Package Overview
Dependencies
1
Maintainers
5
Versions
120
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

@aws-sdk/middleware-stack


Version published
Weekly downloads
3.6M
decreased by-7.38%
Maintainers
5
Created
Weekly downloads
 

Package description

What is @aws-sdk/middleware-stack?

@aws-sdk/middleware-stack is a package that provides a mechanism to compose middleware in the AWS SDK for JavaScript. It allows developers to add, remove, and modify middleware in the request/response lifecycle, enabling custom logic to be executed at various stages of the request processing.

What are @aws-sdk/middleware-stack's main functionalities?

Adding Middleware

This feature allows you to add custom middleware to the middleware stack. The middleware can perform actions before and after the request is processed.

const { MiddlewareStack } = require('@aws-sdk/middleware-stack');

const stack = new MiddlewareStack();

const myMiddleware = (next, context) => async (args) => {
  console.log('Before request');
  const result = await next(args);
  console.log('After request');
  return result;
};

stack.add(myMiddleware, {
  step: 'initialize',
  name: 'myMiddleware',
  priority: 'high'
});

// Use the stack in a client
const client = new SomeAWSClient({ middlewareStack: stack });

Removing Middleware

This feature allows you to remove middleware from the middleware stack by specifying its name.

const { MiddlewareStack } = require('@aws-sdk/middleware-stack');

const stack = new MiddlewareStack();

const myMiddleware = (next, context) => async (args) => {
  console.log('Before request');
  const result = await next(args);
  console.log('After request');
  return result;
};

stack.add(myMiddleware, {
  step: 'initialize',
  name: 'myMiddleware',
  priority: 'high'
});

// Remove the middleware
stack.remove('myMiddleware');

Modifying Middleware

This feature allows you to modify existing middleware in the middleware stack by adding a new middleware with the same name and step.

const { MiddlewareStack } = require('@aws-sdk/middleware-stack');

const stack = new MiddlewareStack();

const myMiddleware = (next, context) => async (args) => {
  console.log('Before request');
  const result = await next(args);
  console.log('After request');
  return result;
};

stack.add(myMiddleware, {
  step: 'initialize',
  name: 'myMiddleware',
  priority: 'high'
});

// Modify the middleware
stack.add((next, context) => async (args) => {
  console.log('Modified middleware');
  return next(args);
}, {
  step: 'initialize',
  name: 'myMiddleware',
  priority: 'high'
});

Other packages similar to @aws-sdk/middleware-stack

Changelog

Source

3.266.0 (2023-02-06)

Bug Fixes

  • features-dynamodb: remove testing for error-should-be message (#4409) (a3ed754)
  • middleware-sdk-transcribe-streaming: close sockets on WebSocketHandler.destroy() (#4400) (3a0cc76)

Features

  • client-compute-optimizer: AWS Compute optimizer can now infer if Kafka is running on an instance. (65e7f31)
  • client-customer-profiles: This release deprecates the PartyType and Gender enum data types from the Profile model and replaces them with new PartyTypeString and GenderString attributes, which accept any string of length up to 255. (4e190c7)
  • client-frauddetector: My AWS Service (Amazon Fraud Detector) - This release introduces Cold Start Model Training which optimizes training for small datasets and adds intelligent methods for treating unlabeled data. You can now train Online Fraud Insights or Transaction Fraud Insights models with minimal historical-data. (34dac99)
  • client-mediaconvert: The AWS Elemental MediaConvert SDK has added improved scene change detection capabilities and a bandwidth reduction filter, along with video quality enhancements, to the AVC encoder. (dea6044)
  • client-outposts: Adds OrderType to Order structure. Adds PreviousOrderId and PreviousLineItemId to LineItem structure. Adds new line item status REPLACED. Increases maximum length of pagination token. (312c4e4)
  • clients: update client endpoints as of 2023-02-06 (f023912)
  • protocol-http: add types for field (#4390) (688b866)
  • types: add request and response interfaces (#4389) (6b1be0b)
  • util-stream: create util-stream package (#4402) (91ec1aa)

Readme

Source

@aws-sdk/middleware-stack

NPM version NPM downloads

The package contains an implementation of middleware stack interface. Middleware stack is a structure storing middleware in specified order and resolve these middleware into a single handler.

A middleware stack has five Steps, each of them represents a specific request life cycle:

  • initialize: The input is being prepared. Examples of typical initialization tasks include injecting default options computing derived parameters.

  • serialize: The input is complete and ready to be serialized. Examples of typical serialization tasks include input validation and building an HTTP request from user input.

  • build: The input has been serialized into an HTTP request, but that request may require further modification. Any request alterations will be applied to all retries. Examples of typical build tasks include injecting HTTP headers that describe a stable aspect of the request, such as Content-Length or a body checksum.

  • finalizeRequest: The request is being prepared to be sent over the wire. The request in this stage should already be semantically complete and should therefore only be altered to match the recipient's expectations. Examples of typical finalization tasks include request signing and injecting hop-by-hop headers.

  • deserialize: The response has arrived, the middleware here will deserialize the raw response object to structured response

Adding Middleware

There are two ways to add middleware to a middleware stack. They both add middleware to specified Step but they provide fine-grained location control differently.

Absolute Location

You can add middleware to specified step with:

stack.add(middleware, {
  step: "finalizeRequest",
});

This approach works for most cases. Sometimes you want your middleware to be executed in the front of the Step, you can set the Priority to high. Set the Priority to low then this middleware will be executed at the end of Step:

stack.add(middleware, {
  step: "finalizeRequest",
  priority: "high",
});

If multiple middleware is added to same step with same priority, the order of them is determined by the order of adding them.

Relative Location

In some cases, you might want to execute your middleware before some other known middleware, then you can use addRelativeTo():

stack.add(middleware, {
  step: "finalizeRequest",
  name: "myMiddleware",
});
stack.addRelativeTo(anotherMiddleware, {
  relation: "before", //or 'after'
  toMiddleware: "myMiddleware",
});

Removing Middleware

You can remove middleware by name one at a time:

stack.remove("Middleware1");

If you specify tags for middleware, you can remove multiple middleware at a time according to tag:

stack.add(middleware, {
  step: "finalizeRequest",
  tags: ["final"],
});
stack.removeByTag("final");

FAQs

Last updated on 06 Feb 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

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

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc