-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
wasm binary? #365
Comments
I wonder if this would be possible to get working with the current state of WASI. Compiling to WASM, as I understand, is the easy part. Getting it to launch external processes (certutil) less so. Update: until this is implemented, I don’t think there’s a way to make this work: WebAssembly/WASI#414 |
thanks for looking into this, it does look like we have to wait on upstream changes before this is possible |
When trying to compile to WASM I'm getting the following errors:
Command run: GOOS=js GOARCH=wasm go build -ldflags "-X main.Version=$(git describe --tags)" -o mkcert.wasm Anyone knows what would be the problem? I'm not familiar with these type of Go compilation errors, the variables seems to be defined, but it throws undefined errors nonetheless, maybe a |
Is there any chance of compiling this code to a wasm binary that can be imported into nodejs and deno projects? I want to use
mkcert
to generate localhost certificates for a local web app package, but it will require end users to installmkcert
themselves, and run commands. Ifmkcert
were usable as a wasm binary (literally just expose the command line interface as a function in js) then local web apps could ship with mkcert as a dependency and install the root CA and generate the localhost certs themselves as part of the initialization process.An example of what initializing mkcert as a wasm module might look like:
The text was updated successfully, but these errors were encountered: