What you need to know: Bubble’s plugin API v4

Bubble is transitioning to Node 18, impacting server-side actions in plugins. Existing functions will now require results as Promises. Understand the key methods affected and see how code might evolve in this post

What you need to know: Bubble’s plugin API v4
Do not index
Do not index
Platform changes – they're as inevitable as your morning coffee. If you've built a Bubble plugin or if you're in the midst of crafting one with server-side actions, a shift by the end of the year might make your plugin obsolete. Here's the low-down:

The change

Bubble is transitioning to Node 18 from an older version. Node 18 doesn't support the Fibers extension. This means that the existing server-side actions API, which previously allowed direct function results, will now require results as Promises.

Key methods affected

Snapshot of the affected methods from Bubble’s plugin announcement documentation
Snapshot of the affected methods from Bubble’s plugin announcement documentation
 

What it looks like

For context, here's a side-by-side comparison of how server-side action code may evolve from the old version to the new:
notion image
 
 
For those hungry for every nitty-gritty detail, here's Bubble's full guide and a forum post to quench that thirst.
Stay bubbly 🫧
 
 

We build and manage software integrations for SaaS companies

Focus on your business, we'll handle integrations

Book an intro call →

Written by

Lola
Lola

Lola is the founder of Lunch Pail Labs. She enjoys discussing product, SaaS integrations, and running a business. Feel free to connect with her on Twitter or LinkedIn.