Alchemy Beta 84 Splits Providers Into Packages
Alchemy 2.0.0-beta.84 makes a breaking monorepo change by moving every cloud and vendor provider into its own package. The release also enables cross-cloud bindings, smaller bundles, faster SDKs, and more scalable plan/apply operations.
This is a painful migration with a strong architectural payoff: Alchemy is becoming a genuinely modular infrastructure platform instead of one oversized package.
- –Provider-specific installs should reduce dependency and bundle overhead for focused deployments
- –Cross-cloud bindings let Workers, Lambdas, and other hosts interact across AWS, Cloudflare, and GCP
- –Distilled SDK improvements claim 5–100× lower per-call overhead and substantially smaller imports
- –Existing projects must update dependencies, imports, state commands, and some runtime assumptions
- –The beta label makes the breaking change defensible, but teams should pin versions and budget migration testing
DISCOVERED
1h ago
2026-10-26
PUBLISHED
2h ago
2026-10-26
RELEVANCE
AUTHOR
samgoodwin89