- feat!: deprecate node12. ([d85ca33](https://github.com/aws/aws-sdk-js-crypto-helpers/commit/d85ca33d1b98e2acdeb5dd8981a369630f69addf))

### BREAKING CHANGES

- Remove node12 from CI (#543)

[4.0.0](https://github.com/aws/aws-sdk-js-crypto-helpers/compare/v3.0.0...v4.0.0) (2023-02-20)

# @aws-crypto/random-source-browser

Access to a secure random source in a browser.
`Math.random` is not acceptable for cryptographic operations.
This module exports a consistent interface for modern browsers
and IE11.

## Usage

```
import {randomValues, randomValuesOnly} from '@aws-crypto/random-source-browser'

const seedData2 = await randomValues(16);
const seedData1 = await randomValuesOnly(16);

```

## randomValues vs randomValuesOnly

Some browsers only implement `crypto.getRandomValues` and not `crypto.subtle`.
If you need to have access to both, you should use `randomValues`. But if
you want to use some cryptographic fallback like MSRCrypto `randomValuesOnly`
is the preferred function.

## Test

`npm test`


Access to a secure random source in a browser. `Math.random` is not acceptable for cryptographic operations. This module exports a consistent interface for modern browsers and IE11.