🚀 Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more
Socket
DemoInstallSign in
Socket

one-webcrypto

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

one-webcrypto - npm Package Compare versions

Comparing version

to
1.0.1

browser.mjs

6

package.json
{
"name": "one-webcrypto",
"version": "1.0.0",
"version": "1.0.1",
"description": "Import the webcrypto API as a single module in both nodejs and browsers.",

@@ -9,6 +9,6 @@ "repository": "https://github.com/fission-suite/one-webcrypto",

"types": "index.d.ts",
"main": "browser.cjs",
"main": "dynamic.cjs",
"exports": {
".": {
"browser": "./browser.cjs",
"browser": "./browser.mjs",
"import": "./node.mjs",

@@ -15,0 +15,0 @@ "require": "./node.cjs"

@@ -58,2 +58,4 @@ # one-webcrypto

So if your environment doesn't support that, it _may_ or _may not_ work.
We know that this setup works (*should work*) with

@@ -64,8 +66,9 @@ * NodeJS 15+ (thus also e.g. mocha)

* Vite
* SvelteKit
* Snowpack
We know that this setup can have issues with
* Jest with the jdom environment
* [none known, yet?]
If you have **any experience** (whether it supports the claims above or not), **please create an issue**.
The idea is to help each other out in these crazy bundler times and document what works and what doesn't. :)