@noble/hashes - npm Package Compare versions

Comparing version 0.4.2 to 0.4.3

package.json

		{
		"name": "@noble/hashes",
		"version": "0.4.2",
		"version": "0.4.3",
		"description": "Fast 0-dependency JS implementation of SHA2, SHA3, RIPEMD, BLAKE2/3, HMAC, HKDF, PBKDF2, Scrypt",
		@@ -68,5 +68,5 @@ "directories": {
		"import": "./lib/esm/cryptoBrowser.js",
		"default": "./lib/crypto.js"
		"default": "./lib/cryptoBrowser.js"
		},
		"import": "./lib/esm/cryptoNode.js",
		"import": "./lib/esm/crypto.js",
		"default": "./lib/crypto.js"
		@@ -73,0 +73,0 @@ },

README.md

		@@ -38,3 +38,3 @@ # noble-hashes ![Node CI](https://github.com/paulmillr/noble-hashes/workflows/Node%20CI/badge.svg) [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)

		The library does not have an entry point. It allows you to select specific primitives and drop everything else. If you only want to use sha256, just use the library with rollup or other bundlers. This is done to make your bundles tiny.
		The library does not have an entry point. It allows you to select specific primitives and drop everything else. If you only want to use sha256, just use the library with rollup or other bundlers. This is done to make your bundles tiny. We support ECMAScript modules (ESM).

		@@ -49,2 +49,5 @@ ```js

		// ESM version inside `esm` directory
		import { sha256 } from '@noble/hashes/lib/esm/sha256';

		// sha384 is here, because it uses same internals as sha512
		@@ -51,0 +54,0 @@ const { sha512, sha512_256, sha384 } = require('@noble/hashes/lib/sha512');

New alerts