Package Exports

crypto-hash-legacy
crypto-hash-legacy/dist/browser.js
crypto-hash-legacy/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (crypto-hash-legacy) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

crypto-hash-legacy

Forked from crypto-hash

Tiny hashing module that uses the native crypto API in Node.js and the browser BUT with legacy exports

Useful when you want the same hashing API in all environments. My cat calls it isomorphic.

In Node.js it uses require('crypto'), while in the browser it uses window.crypto.

The browser version is only ~300 bytes minified & gzipped.

When used in the browser, it must be in a secure context (HTTPS).

Install

npm install crypto-hash-legacy

Usage

import {sha256} from 'crypto-hash';

console.log(await sha256('🦄'));
//=> '5df82936cbf0864be4b7ba801bee392457fde9e4'

API

sha1(input, options?)

sha256(input, options?)

sha384(input, options?)

sha512(input, options?)

Returns a Promise<string> with a Hex-encoded hash.

In Node.js, the operation is executed using worker_threads. A thread is lazily spawned on the first operation and lives until the end of the program execution. It's unrefed, so it won't keep the process alive.

SHA-1 is insecure and should not be used for anything sensitive.

input

Type: string ArrayBuffer ArrayBufferView

options

Type: object

outputFormat

Type: string
Values: 'hex' | 'buffer'
Default: 'hex'

Setting this to buffer makes it return an ArrayBuffer instead of a string.

hasha - Hashing in Node.js made simple