fix(ses): Do not bundle modules for use as modules
MODIFY
packages/ses/package.json
packages/ses/package.json
"types": "./index.d.ts",
"exports": {
".": {
- "import": "./dist/ses.umd.js",
+ "import": "./index.js",
"require": "./dist/ses.cjs"
},
"./lockdown": {
- "import": "./dist/ses.umd.js",
+ "import": "./index.js",
"require": "./dist/ses.cjs"
},
"./package.json": "./package.json"
"lint:types": "tsc -p jsconfig.json",
"prepublish": "yarn run clean && yarn build",
"qt": "ava",
- "test": "yarn build && ava",
+ "test": "ava",
"test:platform-compatability": "node test/package/test.cjs"
},
"devDependencies": {

MODIFY
packages/ses/package.json.md
packages/ses/package.json.md
@@ -98,6 +98,9 @@ The variations differ only in file name extension.
Node.js and other tools will use this file when importing `ses` as an ESM.
(JavaScript module).
+We have in the past experimented with using the precompiled bundle of SES here
+(`./dist/ses.cjs`), but found that this interacted poorly with Endo,
+because an Endo bundle contains symbols that SES censors.
## "require": "./dist/ses.cjs",

fix(ses): Do not bundle modules for use as modules