💻 Who wants a VS Code extension for developing Bubble plugins?

Bask is available in Alpha

:partying_face: Announcing the release of Bask, a VS Code extension for streamlining Bubble plugin development! The alpha version is officially available on the VS Code Extension Marketplace for a small group of early Bubblers to try today. As mentioned before, Bask is a paid extension (at $9/mo or $85/yr) but our first 8 users will get Bask 30% off for life. Because of this early stage of release, our first subscriptions come with a 14 day free trial (this will be reduced to a 7 day trial for future subscriptions) so you can play with it, provide feedback and get upgrades / patch fixes before having to put any real money down.

How it looks today

How to get started

Grab a monthly subscription with promo-code ALPHASQUAD and then DM for next steps (onboarding is manual for now but promise it will be streamlined in the future). Then, if you haven’t done so already, check out our latest documentation here.

Things to note about the Alpha

This is new software and as such it has it’s rough edges. We haven’t seen any issues with Bask accidentally publishing new Plugin versions or doing something that was irreversible, but accidental things still come up, so we do recommend that folks choosing to use Bask at this stage do so with new Plugins or Plugins that are not currently in production. All that said, I’ll be on high alert to triage and fix bugs as quickly as I can. Please report those in this thread.

What feature should I add next?

There’s a few features I could add so I need your help picking which ones to pursue. Please respond to the poll, if you could have only one of these, which would it be?

  • Dashboard that goes into more detailed plugin installation / revenue data than what Bubble’s native reports provide.
  • Unit testing framework for automated plugin test reporting.
  • AI copilot that’s tuned / prompt-primed for developing Bubble plugins (GPT3.5/GPT4).
  • Something else (reply with your feature request below).
0 voters
5 Likes

My boy is on Windows XP :skull:
Screenshot_1

Seriously though this look great. I only make little plugin actions so I get by with the terrible UX but this looks amazing for the users with bigger plugins

4 Likes

Lol - Win7 actually. Have been waiting to wrap this project up before going to 10 because Zues knows I didn’t need another side quest.

1 Like

A week out from my announcement, just want to say thank you so much to all our early adopters! I’ve received good feedback and pushed updates resolving a host of issues for MacOS users. If you haven’t done so already, please update to version 0.6.12 to get those :slight_smile:

Moving forward, I do have a few more fixes to push out for MacOS users (a notable one related to Bask failing after system sleep) which I’m working on today. And after that, I’ll be rolling out sign in support for Bubble accounts using 2FA. As for our next new feature, I’m still collecting feedback on that to determine what to make - details to come!

Finally, we still have 4 spots available for alpha users so do check out here if interested in getting started.

2 Likes

New update :slight_smile: Just released a fix for the MacOS issue mentioned above (the one related to Bask failing after system sleep). Please update Bask to v0.6.13 to see these changes.

Working on adding 2FA support next.

1 Like

New update :slight_smile: Please update Bask to v0.7.2 for the following improvements:

  • Added ability to build / bundle Common JS source files (those ending in .js) as well as ESM source files (those ending in .mjs). Solves a core pain point of yours, @AliFarahat (and @dorilama if I’m recalling correctly).
  • Automatically rebuild all relevant plugin files when build.mjs is updated and Bask Build & Push is enabled.

Compatibility with 2FA’d Bubble accounts coming next (I promise!)

1 Like

I both applaud this and cringe at the same time. Its not your fault, Bubble is just doing things for Bubble plugin developers completely opposite to the intent of the web.

Hopefully they will come out with a standards compliant service for plugin developers so that things like your VSCode extension can be run much more smoothly.

1 Like

Having issues setting it up. Great concept, but not ideal for the price if it’s not working as intended.

So… When I try to use any of the commands, I’ll keep getting this error:
Cursor_9iSTBGETev

And when I do a fresh install, and reload, the browser will open up with the following puppeteer code that doesn’t actually launch, it just goes into the search bar of whatever default browser I’m using (in my case, Edge).

This is what it looks like:
--allow-pre-commit-input --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=Translate,AcceptCHFrame,MediaRouter,OptimizationHints,Prerender2 --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-search-engine-choice-screen --disable-sync --enable-automation --enable-blink-features=IdleDetection --enable-features=NetworkServiceInProcess2 --export-tagged-pdf --force-color-profile=srgb --metrics-recording-only --no-first-run --password-store=basic --use-mock-keychain --headless=new --hide-scrollbars --mute-audio about:blank --autoplay-policy=user-gesture-required --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-update --disable-default-apps --disable-dev-shm-usage --disable-domain-reliability --disable-extensions --disable-features=AudioServiceOutOfProcess --disable-hang-monitor --disable-ipc-flooding-protection --disable-notifications --disable-offer-store-unmasked-wallet-cards --disable-popup-blocking --disable-print-preview --disable-prompt-on-repost --disable-renderer-backgrounding --disable-setuid-sandbox --disable-speech-api --disable-sync --hide-scrollbars --ignore-gpu-blacklist --metrics-recording-only --mute-audio --no-default-browser-check --no-first-run --no-pings --no-sandbox --no-zygote --password-store=basic --use-gl=swiftshader --use-mock-keychain --single-process --remote-debugging-port=0 --user-data-dir=C:\*****************.

This is not allowing me to utilize any of the commands available. I have entered in my registration key, but it won’t allow me to login to my Bubble account.

I have signed up for the trial, thinking it was going to be functional… but it’s okay, cause not all good things start off easy which I understand. I’ll keep my trial up for a few days until you reach back, hoping we can figure out what’s going on!

P.S. Followed your “install guide” as much as I could.

Hey GhostCodes, sorry to hear about those installation issues :frowning: That said, I’m confident we can work through them to get you up and running fairly soon. I haven’t seen our other users experience this so perhaps it’s something related to edge being your default web browser. Looking at our code now to see if I can fix it with the info provided but will DM you with any debugging questions - thank you!

Sweet! Thanks. If it helps, I am using a modded VSCode, and Edge is always going to be my primary browser. Another thing was I noticed you used puppeteer to launch the page. Not sure if it works unless it’s installed on my system, but it wasn’t installed for me so that could also be another reason why it didn’t run right.

Just released a patch for you - v0.8.11. May take a moment for you to see it on your end as Microsoft fully deploys the update but when you do, please let me know how the installation goes. Since you mentioned you’re running a non-standard version of VSCode, our patch may still fail. If it comes to that, then I’d be happy to dig in more while acknowledging the possibility there may be a fundamental incompatibility with your mod. But let’s see first before making conclusions! :crossed_fingers:

Fully reinstalled, reloaded… and this still happens:
Cursor_fQqHowzAud

I’ll try again later, maybe I need to just try a fresh install of everything? IDK.

I want to help you improve this as it’s very appealing.

There’s three login touchpoints in Bask:

  1. Supplying Email-Password to sign into Bubble
  2. Supplying 2fa code (if you have that enabled) to finish signing into Bubble
  3. Supplying Email-Password to get an Auth Token so Bask can fetch your plugins via API from bubble.io

It looks like Bask is failing on that last touchpoint and perhaps is not raising the opportunity for you to re-enter your login credentials (although it’s not clear from what I’ve gathered that you’ve entered your email-password incorrectly). All said, I don’t believe a fresh install is the solution.

Since you’ve mentioned interest to help debug this, I’m going to take 20 minutes to review our codebase and then DM you looking for a time we can video chat to review your error. Thank you for your patience on this one :slight_smile:

I never was prompted to use option 1 or 2 unfortunately. And thank you.

1 Like

Oh, really!? Then that’s likely the issue. Let me take a look at that.

… as an addendum, I want to circle back to what you said earlier about “making a fresh install of everything”… I did just notice that alert in your modded VS Coded installation indicating that your “Cursor installation appears to be corrupt…”. So if by reinstall you meant to install a non-modded version of VS Code, then perhaps that is the solution. Going out on a limb but because I haven’t seen this issue with any of our existing users and because I see that other extensions aren’t working correctly for you, would you be willing to reinstall a standard version of VS code? If nothing else, that would help me rule that out as a factor in the error. Please let me know.

The corrupt version is a bug. It’s nothing. Maybe if I had a look at the source I could figure it out, I’m pretty handy in those realms. Shoot me a DM if you want to dig further.

@zelus_pudding I’m having the same issue (never prompted for bubble credentials, Error fetching Bubble auth token), a standard install of VS code. Where do you keep the creds, can’t we just provide them in a config file or smth?

And chrome is my default browser as well