Bubble remains the primary plugin store. Keep actions/, elements/, api/,
html_headers.html, meta_data.json and shared_tech_params.json in their export layout;
never rename existing opaque IDs. New element AAu coexists with legacy AAp.
Handwritten code lives in TypeScript: src/, scripts/, test/ and the root test configs.
Node runs scripts with native type stripping; tsc --noEmit checks them all. A separate browser
config keeps Node globals out of src/ and the browser harness. Bubble callbacks
remain generated JavaScript for editor sync; the legacy AAp export stays unchanged.
Edit TypeScript in src/, then run corepack yarn build and commit the generated callbacks and
header. The header loads the pinned official Uppy 6.0.5 ESM/CSS CDN bundle, whose core 6.3.0,
Dashboard 6.0.2 and Transloadit 6.0.1 match the typed npm dependencies. Upgrade these together;
Dependabot cannot choose the corresponding CDN release for you. Only our glue is minified into
the header; no vendored Uppy bundle needs reviewing. Apps must allow releases.transloadit.com
and Transloadit's API/upload/result hosts through their CSP/network policy.
corepack yarn check runs Biome, TypeScript, Vitest with enforced coverage, and deterministic
build verification. corepack yarn fix formats source. corepack yarn test:browser exercises the
actual generated header and callbacks in Chromium, through Bubble-shaped canvas/state/event APIs.
Install Chromium once with corepack yarn playwright install chromium. Unit tests cover lifecycle,
signature byte preservation, progress/results, failures, reset, multiple updates and legacy uploads.
Use the opentest key from node-sdk as process environment only, without editing or copying .env:
corepack yarn build
BUBBLE_REAL_API=1 node --env-file="$HOME/code/node-sdk/.env" node_modules/@playwright/test/cli.js testThis mounts the built element, selects a generated non-customer PNG, performs a signed tus upload,
waits for a real /image/resize result, and downloads it. It creates a billable test Assembly but
no persistent Template. The local signer keeps the Auth Secret in Node; only signed params reach
the browser. Traces and request payload recording are disabled to keep credentials out of artifacts.
CI requires BUBBLE_E2E_TRANSLOADIT_KEY and BUBBLE_E2E_TRANSLOADIT_SECRET as Actions secrets
(and Dependabot secrets for dependency PRs). The test receives them as TRANSLOADIT_KEY and
TRANSLOADIT_SECRET. Internal PRs fail clearly when missing; fork PRs run unit/browser checks only.
Add a user-facing Changeset with corepack yarn changeset. On main, Changesets opens a version PR
that updates package.json and CHANGELOG.md. Before merging, close and reopen it as a maintainer
if CI is absent: GitHub does not trigger PR workflows for GITHUB_TOKEN writes. Wait for its checks
to pass. Merge the version PR, then download that commit's
bubble-candidate-<sha> artifact from Release candidate Actions. The archive and SHA-256 file
contain only Bubble's export. Locally, corepack yarn release:prepare produces the same handoff.
Candidates are built on main only when no Changesets remain pending; use the version PR's commit for publication.
Changesets versions are repository candidates; record Bubble's separately assigned published
version in the release notes. There is deliberately no automatic Bubble deploy or user migration.
- In a clean checkout of the reviewed/merged commit, run
corepack yarn install --immutable,corepack yarn check, thencorepack yarn release:prepare. Verify the archive SHA-256 before handing it off. Keep the prior published version available for rollback. - Log in to the existing plugin editor.
Under Version → GitHub, synchronize the existing repository after the PR is merged. Bubble
pulls the export; resolve any editor/GitHub conflicts before continuing. Do not create a new plugin.
If synchronization is unavailable, the archive maps directly to tabs: Shared HTML header and
shared keys, General metadata, Elements (
AApandAAu) and Actions (AAF). Paste complete function expressions from the matching generated.jsfiles; declare fields/states/events exactly as in theirparams.json. Do not replace the old element or action IDs. - Check Shared → HTML header uses the current
html_headers.html, and confirm the new Transloadit Uploader fields/states/events appear. Keep jQuery disabled; the uploader supports both DOM and Bubble's jQuery-style canvas wrapper without depending on jQuery. - In the plugin editor's test-app setting, choose a disposable Bubble app, then Go to test app to install/refresh this development plugin. Add the new element and an authenticated backend signer; bind its returned params/signature strings. Never expose the Auth Secret to the page.
- In editor and run mode, test Template ID and Instructions; inline Dashboard and button; valid upload to completed result URLs; expired signature; type/size restriction; cancel/reset; a second upload; two instances; and page navigation away during upload. Verify existing VideoWrapper and open-action workflows. Repeat at desktop and 390px; check browser errors/network and CORS on any legacy notification URL. Confirm both result URLs and Bubble workflow events, not screenshots alone.
- Only after that pass, deploy from Version, selecting the appropriate change type and copying the Changeset release notes. Verify the marketplace listing opens while signed out, install the published version in the test app, and repeat an upload. Update README with its verified URL and record the published Bubble version, repository commit and test evidence on #1. Then close #1. If anything fails, keep the current published version and fix the candidate; if already deployed, restore its saved export and publish a corrective version from the editor.
Bubble's GitHub integration explains synchronization; publishing is a separate editor action. These login-dependent steps remain unexecuted by CI.
Tooling follows transloadit/zapier's commits from 2026-10-14 through 2026-10-21: Yarn 4, Biome,
TypeScript, Vitest, tests of the actual built artifact, Changesets, PR CI and weekly grouped updates.
We preserve legacy IDs like Zapier preserves saved Zap contracts. Bubble has no Zapier-style CLI
upload/promote/migrate, so releases produce an export and explicit human handoff. The official CDN
keeps the export small; a future custom bundle can reduce unused Uppy plugins if download size matters.
Uppy's errorReporting: false only disables request-level reports in the pinned version. Its
plugin error handler still sends messages, browser user agent and client identification to
transloaditstatus.com/client_error, including validation failures; this is not a telemetry opt-out.
Uploads retain the original one-file limit. Multi-file batches need separate result aggregation and
partial-retry handling; exposing a larger limit before those exist can silently lose processed results.