As the title states, I believe the Bubble-created plugins should be open sourced so that others can fork and improve them. That is all.
3 Likes
They should make their plugins kind of open-source, I agree on that.
For a moment I thought you were talking about all bubble plugins, apologies.
The main issue is Bubble plugins, for most of them, are not “really” plugins. They don’t use plugin editor to create them. A lot of them should also be natively integrated to Bubble like API Connector (that should have is own tab), RTE, multiselect dropdown…
Because they are not real plugins and they probably use some stuff that are not publicly available (there’s a lot of thing that Bubble plugins can do that we cannot do in Plugins builder)… so I don’t think it’s possible for Bubble to make them open source.
6 Likes
Yeah, they’re basically built-in to the editor themselves. Not built the same way as contributor plugins.
1 Like
I’ve always thought that the source was available at some point in time because how else would any one ever have figured out the “p” prefix custom type naming convention to bind return objects to plug-in types?
Yes, I’ve noticed this too
they were snooping API calls, most likely. I forget the name of the tool for that
1 Like
Yes I suggested this as well on another post. I highly agree!
If only they introduced a way for us to build the plugins natively through code with typesafe capabilities. Then things would get interesting.
Creator of Bask here.
The “p ” prefix thing can be introspected in the Chrome devtools network tab when Bubble saves API initializations in the bubble plugin editor.
As for developing with Typescript, Bask has a build mode that I think could work with TypeScript. If not, I’m pretty sure I could push an update to get it to work. We already allow devs to build bundles using esbuild… would just be a question of ensuring we’re recognizing/loading typescript files correctly.
Let me know if you want to explore this further/be willing to test the capability.
2 Likes
Aaa I see. I always wondered how on earth any one figured that out 
1 Like
For a short period of time (less than hour) 2 or 3 years ago, those plugin codes were accessible through the “See Plugin Code” button.
It was nice until it lasted.
2 Likes
Sorry for the noob question here but I must ask, as it’s been on my mind for a while. If the plugin code isn’t accessible, how do we know it’s safe? E.g., not sending data somewhere or doing something else malicious.
Bubble’s plugin code is just as safe as the rest of their application/platform. If you’re concerned Bubble’s plugins aren’t safe, you’re in the wrong forum.
As for 3rd party plugins - I do believe those are ripe for exploiting users. I imagine Bubble does some level of checking it for overt hackery but, I think there is a lot that people could slip into these that could make it onto the marketplace. The worst I’ve seen (which isn’t that bad) is people tracking plugin usage… this could be engineered to hoover up user data that users otherwise wouldn’t want stored in a database somewhere. There’s a chance I’m wrong.
2 Likes
Why plugins, ? make whole bubble opensource, and if you think they can’t make it opensource, they CAN but will never do that, all because of money.
Don’t say opensource Don’t make money.
Appreciate the reply and thanks for the concern, but I’m in the right forum. Was referring to third party plugins.
3 Likes
Bubble, like any business needs to make money to keep improving the platform and payback the investors. They aren’t obligated to opensource anything. Its a private business.
But I do agree with the OP that it would be a great idea to opensource Bubble published plugins for educational purposes.
So when did I said to not charge users ?
Yes they aren’t obligated but if they wish they can.
I never said that it’s a government business.
Looks like this person is a bubble founder disguised in another account 