-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestions for Browser Extension Manifest V3 #287
Comments
@alaadaff Sorry for the late reply. How can I reproduce the problem you are facing? |
I'm using the following instructions to browserify the library: https://www.mobilefish.com/developer/nodejs/nodejs_quickguide_browserify_bip32_utils.html Below is a screenshot of the manifest.json. I'm calling the new CipherSuite object in my extension's background.js. Also, when I try instead to not use the global module name above and instead import { CipherSuite } from the bundled hpke_browser.js I'm receiving an error that the bundled file does not provide an export named "CipherSuite". On the other hand the browserified hpke_browser.js works perfectly when loaded into a single html file as shown below. But unfortunately with browser extensions we cant load scripts directly in an html page. |
The hpke_browser.js can also be generated by using ebuild.
It can be used as follows: import { Kem, Kdf, Aead, CipherSuite } from './hpke_browser.js';
// ... See https://github.com/dajiaji/hpke-js/blob/main/test/runtimes/browsers/pages/index.html |
Anyone has used browserify with this hpke-js library for loading into a Chrome browser extension V3? @dajiaji
I'm running into a problem where I can't import {CipherSuite, KemId, KdfId, etc.} into a browser extension's background.js getting an error that the module does not provide an export named "CipherSuite, ..etc"
The text was updated successfully, but these errors were encountered: