Search for a command to run...
Series
Undocumented Atlassian Forge behaviour that passes lint, passes deploy, and breaks anyway.
Key takeaways END STATE: the subpath import type-checks, verified across TypeScript 5.9.2, 6.0.3 and 7.0.2, with a config that also survives forge deploy. Use bundler. On TypeScript 6 and 7 it is a g
Key takeaways END STATE: you can look at any route`` call that throws and say which of the two causes it is, then fix it — verified by a probe you run locally with no deploy. There is one rule with t
Key takeaways @forge/bridge throws at IMPORT time, not call time. A handler that imports a poisoned module and never calls it still fails, which I measured as HTTP 424 on a live site. The error strin
Key takeaways FAIL_IF_EXISTS exists from @forge/kvs 1.3.0 (2026-02-03) and is atomic — one winner in twelve concurrent writes, eleven KEY_CONFLICT at HTTP 409. Adding ttl to that call does not make a
Forge Custom UI apps run inside iframes. That iframe has no knowledge of the host Confluence theme unless you explicitly ask for it. If you skip this step, your app renders as a bright white rectangle
I built a Forge major-version predictor on a guess, and it took a review to find the answer inside my own commit Key takeaways END STATE: a predictor that PARSES two manifests and reports every docum
