284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
35 lines
1.4 KiB
Markdown
35 lines
1.4 KiB
Markdown
# service-proxy Component Template
|
||
|
||
This project was generated with `alga component create`. It targets the Alga extension runner
|
||
using the WebAssembly Component Model and [`componentize-js`](https://github.com/bytecodealliance/componentize-js).
|
||
|
||
## Available scripts
|
||
|
||
- `npm run build` – transpile TypeScript to ESM and produce a `.wasm` component under `dist/`.
|
||
- `npm run clean` – remove build artifacts.
|
||
|
||
## Project structure
|
||
|
||
- `src/` – TypeScript sources implementing the `handler` export defined in `wit/extension-runner.wit`.
|
||
- `src/types.ts` – convenience copies of the WIT data structures for use in TypeScript.
|
||
- `wit/extension-runner.wit` – WIT world definitions describing the host capabilities exposed by the runner.
|
||
- `dist/` – build output (`dist/js` for the intermediate JS bundle, `dist/component.wasm` for the component artifact).
|
||
|
||
## Building
|
||
|
||
```bash
|
||
npm install
|
||
npm run build
|
||
```
|
||
|
||
The final component artifact will be written to `dist/component.wasm`. This file, along with the
|
||
generated metadata in `dist/component.json`, should be packaged and uploaded via the Alga registry.
|
||
|
||
## Next steps
|
||
|
||
- Implement your business logic inside `src/handler.ts`.
|
||
- Use the generated helpers in `src/ui-proxy.ts` to interact with host proxy routes instead of storing secrets client-side.
|
||
- Add tests (e.g., using Vitest) that exercise your handler logic.
|
||
- When ready, run `npm run build` and use `alga pack`/`alga publish` to distribute the component.
|
||
|