ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of Biome and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Biome | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | lint-rules, markdown-support, framework-coverage, css-formatter | unified-api, integrations, sync-reliability, accounting |
| Last editorial update | 5h ago | 7d ago |
| Website | Visit → | — |
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
Merge's weekly cadence is all connector depth: no new categories, no agent surface.
Merge ships a dated digest every week, and for the last three months the contents have been uniform: per-connector mapping fixes, pagination and sync-reliability work, and incremental field coverage across Sage Intacct, NetSuite, SharePoint and QuickBooks Online. The one product-surface change in the window is per-integration customization of the Link setup flow, which lets customers hide auth steps and the Selective Sync screen for specific integrations. Everything else is fidelity work on integrations Merge already supports.
Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.
The rule set is widening along two axes at once: frameworks and file types. Framework rules are now specific enough to argue about Svelte runes rather than generic JavaScript, and CSS handling has pushed into HTML attributes and registered custom properties. The larger move sits in 2.5.8's PR list rather than its changelog — a markdown linter, a markdown rule generator, a markdownlint rule source, a two-phase markdown parser, and a first rule in useTopLevelHeading, none of it documented for users yet.
Markdown linting looks close enough to ready that it should appear in the changelog proper rather than the PR list, most likely as nursery rules in the next minor.
Merge ships a dated digest every week, and for the last three months the contents have been uniform: per-connector mapping fixes, pagination and sync-reliability work, and incremental field coverage across Sage Intacct, NetSuite, SharePoint and QuickBooks Online. The one product-surface change in the window is per-integration customization of the Link setup flow, which lets customers hide auth steps and the Selective Sync screen for specific integrations. Everything else is fidelity work on integrations Merge already supports.
The arc points at depth over breadth. Merge is spending its release budget making existing connectors survive large accounts — big item catalogs, user-defined dimensions, high attachment volumes — rather than adding new verticals. Accounting and File Storage absorb most of each week's entries, with ATS and CRM getting steady but thinner attention, and nothing in the window suggests a change to the unified-API model itself.
Expect the next several digests to continue the Sage Intacct, NetSuite and SharePoint deepening, with further Link-flow configuration options as the main user-visible additions. The entries give no signal either way on whether Merge plans an agent- or MCP-facing surface.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Biome or Merge.
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Biome and Merge are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Biome and Merge are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.