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
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:
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
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:
For those hungry for every nitty-gritty detail, here's Bubble's full guide and a forum post to quench that thirst.
Expand Your Integration Library, Without the Distractions.
Your time is valuable. We'll help you launch plugins, add-ons, and extensions, for your users that make interacting with your product a delight. Let's chat and explore how you can grow your integration library without sidetracking your team.
Lola is the founder of Lunch Pail Labs and the curator of the Integrations Directory. She enjoys discussing low-code, integrations, and running a solo business. Feel free to connect with her on Twitter or LinkedIn.