build(deps): bump @aws-sdk/shared-ini-file-loader from 0.1.0-preview.1 to 3.0.0

[dependabot]

Bumps @aws-sdk/shared-ini-file-loader from 0.1.0-preview.1 to 3.0.0.

Release notes

Sourced from @​aws-sdk/shared-ini-file-loader's releases.

v3.0.0

3.0.0 (2020-12-15)

What’s New

Modular Packages

AWS SDK for Javascript v2 publishes a single npm package that supports all the AWS services. This makes it easy to use multiple services in a project at the cost of a large dependency when only using a handful of services or operations. In resource constrained environment such as mobile devices, having separate packages for each service client allows optimizing the dependency. The AWS SDK for Javascript v3 provides such modular packages. We have also split up the core parts of the SDK so that service clients only pull in what they need. For example, a service that sends responses in JSON will no longer need to also have an XML parser as a dependency.

Here’s a quick example comparing v2 and v3 of the AWS SDK for Javascript. In v2, the S3 client can be created using single monolithic package:

const AWS = require("aws-sdk");
const s3Client = new AWS.S3({});
await s3Client.createBucket(params);

In v3, the service clients are prefixed with client- followed by service name. So you can create the modular S3 client by importing @aws-sdk/client-s3:

const { S3 } = require("@aws-sdk/client-s3");
const s3Client = new S3({});
await s3Client.createBucket(params);

The blog post on modular packages in AWS SDK for JavaScript provides details on other modular packages in the SDK and shows an example of performance improvement due to bundle size reduction.

Middleware Stack

Version 2 of the SDK allows modifying a request throughout multiple stages of a request’s lifecycle by attaching event listeners to a request. It can be difficult to debug what went wrong during a request’s lifecycle using event listeners.

In version 3, we’ve switched to using a middleware stack to control the lifecycle of an operation call. This gives us several benefits: each middleware in the stack calls the next middleware after making any changes to the request object. This makes debugging issues in the stack much easier since you can see exactly which middleware was called leading up to an error.

Here’s an example of adding a custom header using middleware:

const { S3 } = require("@aws-sdk/client-s3");
const client = new S3({ region: "us-west-2" });`
client.middlewareStack.add(
(next, context) => async (args) => {
args.request.headers["x-amz-meta-foo"] = "bar";
const result = next(args);
// result.response contains data returned from next middleware.
return result;
},
{
step: "build",
</tr></table>

... (truncated)

Changelog

Sourced from @​aws-sdk/shared-ini-file-loader's changelog.

3.0.0 (2020-12-15)

Features

• bump version to 3.0.0 (#1793) (d8475f8)

1.0.0-rc.9 (2020-12-11)

Bug Fixes

• shared-ini-file-loader: ignore prohibited profile name (#1764) (a209082)

1.0.0-rc.8 (2020-12-05)

Note: Version bump only for package @​aws-sdk/shared-ini-file-loader

1.0.0-rc.3 (2020-10-27)

Note: Version bump only for package @​aws-sdk/shared-ini-file-loader

1.0.0-rc.2 (2020-10-22)

Note: Version bump only for package @​aws-sdk/shared-ini-file-loader

1.0.0-rc.1 (2020-10-19)

Features

... (truncated)

Commits

• 2c3e06c Publish v3.0.0
• d8475f8 feat: bump version to 3.0.0 (#1793)
• 62a6f5c Publish v1.0.0-rc.9
• a209082 fix(shared-ini-file-loader): ignore prohibited profile name (#1764)
• acf1b04 Publish v1.0.0-rc.8
• 113cc4d chore(deps-dev): bump typescript to ~4.1.2 (#1735)
• e72d03b Publish v1.0.0-rc.3
• d64e07e chore(package.json): add repository field for each package (#1611)
• 19f3fea chore(package.json): add homepage for each package (#1608)
• 1660cc9 Publish v1.0.0-rc.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.