Obelisk 0.37 adds native JavaScript, hot deployments, and built‑in cron
What’s new
Obelisk 0.37 ships first‑class JavaScript support for activities, workflows, and webhook endpoints — all running inside a fine‑grained permission sandbox. It has been reported that previous JS support compiled code into WASM (via ComponentizeJS and the StarlingMonkey engine), producing 10 MB+ binaries and requiring a Node.js build pipeline; 0.37 replaces that with a native JS runtime built into Obelisk so components can be plain .js files with no bundler or WASM toolchain. The release also documents distinct JS APIs for side‑effectful activities, deterministic workflows (with durable sleep and join sets), and async webhooks that can spawn and query child executions.
Deployments, cron, and observability
Alongside the runtime, Obelisk introduces a Deployment concept that supports hot redeploy and fine‑grained network permissions (you can declare allowed outbound hosts per activity), plus built‑in cron scheduling. Parallel executions are visible in the Web UI trace view and determinism is enforced by the platform rather than by banning features from user code. Expect a smoother developer loop — push a .js, hot‑redeploy, and watch the trace — and clearer operational controls for timezone‑less cron jobs.
Why it matters
For teams who've been wrestling with WASM toolchains, big binaries, and Node build steps, this feels like progress. Developer ergonomics get a clear win: smaller artifacts, fewer build stages, and familiar JavaScript without sacrificing observability or control. Could Obelisk’s move nudge more serverless and orchestration projects back toward embedding full runtimes instead of relying solely on WASM? Developers will be watching — and many will likely breathe a sigh of relief.
Comments