chore: prettier --write **/*.{ts,md,json}

Author: trivikr

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,5 @@
-*Issue #, if available:*
-
-*Description of changes:*
+_Issue #, if available:_
 
+_Description of changes:_
 
 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

CODE_OF_CONDUCT.md

@@ -1,4 +1,5 @@
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
 [email protected] with any additional questions or comments.

CONTRIBUTING.md

@@ -1,29 +1,28 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional 
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
 documentation, we greatly value feedback and contributions from our community.
 
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary 
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
 information to effectively respond to your bug report or contribution.
 
-
 ## Reporting Bugs/Feature Requests
 
 We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check [existing open](https://github.com/aws/aws-sdk-js-crypto-helpers/issues), or [recently closed](https://github.com/aws/aws-sdk-js-crypto-helpers/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already 
+When filing an issue, please check [existing open](https://github.com/aws/aws-sdk-js-crypto-helpers/issues), or [recently closed](https://github.com/aws/aws-sdk-js-crypto-helpers/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already
 reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
-* A reproducible test case or series of steps
-* The version of our code being used
-* Any modifications you've made relevant to the bug
-* Anything unusual about your environment or deployment
-
+- A reproducible test case or series of steps
+- The version of our code being used
+- Any modifications you've made relevant to the bug
+- Anything unusual about your environment or deployment
 
 ## Contributing via Pull Requests
+
 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
 
-1. You are working against the latest source on the *master* branch.
+1. You are working against the latest source on the _master_ branch.
 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
 3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
 
@@ -36,23 +35,22 @@ To send us a pull request, please:
 5. Send us a pull request, answering any default questions in the pull request interface.
 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
-GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
-
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws/aws-sdk-js-crypto-helpers/labels/help%20wanted) issues is a great place to start. 
 
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws/aws-sdk-js-crypto-helpers/labels/help%20wanted) issues is a great place to start.
 
 ## Code of Conduct
-This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
-[email protected] with any additional questions or comments.
 
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+[email protected] with any additional questions or comments.
 
 ## Security issue notifications
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
 
 ## Licensing
 

README.md

@@ -1,60 +1,71 @@
 ## AWS SDK JS Crypto Helpers
+
 AWS Cryptographic Helpers for Javascript and Node.js
 
 ## Scope
+
 This repository collects cryptographic helper packages. We have designed it to gather packages that implement simple primitives for the browser or Node.js. More information about AWS Crypto Tools can be found [here](https://docs.aws.amazon.com/aws-crypto-tools/index.html?id=docs_gateway#lang/en_us)
 
 ## Project Status
+
 This project is still in its early stages. Please send us your feedback. We might make breaking changes in future releases while the SDK is still in developer preview.
 
 ## Getting started
+
 Let’s walk through setting up a project that requires a cryptographically secure random value. The following steps use npm as an example. They assume you have node.js and npm already installed.
-1.	Create a new node.js project.
-2.	In the project, run: `npm install --save @aws-crypto/random-source-node@preview`
-3.	Create a new file called index.js, require the function, and then use it to get a random value.
+
+1. Create a new node.js project.
+2. In the project, run: `npm install --save @aws-crypto/random-source-node@preview`
+3. Create a new file called index.js, require the function, and then use it to get a random value.
+
 ```javascript
-const {randomValues} = require('@aws-crypto/random-source-node')
+const { randomValues } = require("@aws-crypto/random-source-node");
 async function example() {
-    try {
-    const rand = await randomValues(32)
-    console.log(rand.length)
+  try {
+    const rand = await randomValues(32);
+    console.log(rand.length);
   } catch (err) {
-    console.error(err)
+    console.error(err);
   }
 }
 example();
 ```
 
 ## Crypto Helper Package Index
+
 Each package has readme details.
 
-* [crc32](packages/crc32)
-* [ie11-detection](packages/ie11-detection)
-* [random-source-browser](packages/random-source-browser)
-* [random-source-node](packages/random-source-node)
-* [random-source-universal](packages/random-source-universal)
-* [sha256-browser](packages/sha256-browser)
-* [sha256-js](packages/sha256-js)
-* [sha256-universal](packages/sha256-universal)
-* [supports-web-crypto](packages/supports-web-crypto)
+- [crc32](packages/crc32)
+- [ie11-detection](packages/ie11-detection)
+- [random-source-browser](packages/random-source-browser)
+- [random-source-node](packages/random-source-node)
+- [random-source-universal](packages/random-source-universal)
+- [sha256-browser](packages/sha256-browser)
+- [sha256-js](packages/sha256-js)
+- [sha256-universal](packages/sha256-universal)
+- [supports-web-crypto](packages/supports-web-crypto)
 
 ## Testing
+
 To run the tests in every package.
+
 ```
 npm install
 npm run bootstrap
 npm test
 ```
 
 ## Feedback
-We welcome your feedback! If you have comments, questions, or suggestions, open a GitHub issue. 
+
+We welcome your feedback! If you have comments, questions, or suggestions, open a GitHub issue.
 We are actively monitoring issues and will respond to feedback as we prepare for our GA launch.
 
 ## Contributing
+
 We welcome your contributions! To fix a problem, or add to an existing package: create a pull request.
 You must submit all pull requests under the Apache 2.0 license. They will be reviewed by a team member prior to merging.
 We would appreciate, but do not require, unit tests for all significant contributions. See [Contributing](CONTRIBUTING.md) for more information.
 
 ## License
 
-This library is licensed under the Apache 2.0 License. 
+This library is licensed under the Apache 2.0 License.

lerna.json

@@ -1,22 +1,12 @@
 {
   "lerna": "2.11.0",
-  "packages": [
-    "packages/*"
-  ],
+  "packages": ["packages/*"],
   "version": "independent",
   "command": {
     "bootstrap": {
-      "nohoist": [
-        "@types/*",
-        "typedoc",
-        "karma*"
-      ]
+      "nohoist": ["@types/*", "typedoc", "karma*"]
     }
   },
   "hoist": true,
-  "nohoist": [
-    "@types/*",
-    "typedoc",
-    "karma*"
-  ]
+  "nohoist": ["@types/*", "typedoc", "karma*"]
 }