WASM troubleshooting docs closes #2286 (#2291)

This commit is contained in:
James Hodgkinson 2023-11-05 10:32:39 +10:00 committed by GitHub
parent b9d47fe8f7
commit ffafb32389
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 20 additions and 2 deletions

View file

@ -18,4 +18,5 @@ The Swagger UI is available at `/docs/swagger-ui` on your server (ie, if your or
The OpenAPI schema is similarly available at `/docs/v1/openapi.json`.
You can download the schema file using `kanidm api download-schema <filename>` - it defaults to `./kanidm-openapi.json`.
You can download the schema file using `kanidm api download-schema <filename>` - it defaults to
`./kanidm-openapi.json`.

View file

@ -114,3 +114,21 @@ When a service like sudo, sshd, su etc. wants to authenticate someone, it opens
that service, then performs authentication according to the modules defined in the pam.d config. For
example, if you run `ls -al /etc/pam.d /usr/etc/pam.d` in SUSE, you can see the services and their
respective pam.d config.
## Troubleshooting builds
### WASM Build failures due to "Error: Not able to find or install a local wasm-bindgen."
This seems to relate to a version mismatch error in `wasm-pack` as seen in
[this thread in the wasm-pack repository](https://github.com/rustwasm/wasm-pack/issues/1138).
Try reinstalling `wasm-bindgen-cli` by running the following (the `--force` is important):
```shell
cargo install --force wasm-bindgen-cli
```
Or reinstalling `wasm-pack` similarly.
If that doesn't work, try running the build with the `RUST_LOG=debug` environment variable to
investigate further.

View file

@ -58,7 +58,6 @@ cargo install cargo-udeps
- [ ] publish `kanidm_proto`
- [ ] publish `sketching`
<!-- - [ ] publish `kanidmd/kanidm` -->
- [ ] publish `kanidm_utils_users`
- [ ] publish `kanidm_lib_file_permissions`
- [ ] publish `kanidm_client`