next13-pocketbase-demo VS js-sdk

I've got a note-posting app that is failing intermittently in Firefox. I suspect the problem is related to my use of async/await because it works when I enable debugging in Firefox and step through the calls slowly. I've never worked with Next.js or any web frameworks, and I still need to learn how to use the debugging console effectively, so I'm struggling to understand it on my own. Could someone explain the problem to me or help me rewrite the function?

The Pocketbase JS SDK allows for the creation of custom auth stores for more fine-grained control. In this tutorial, however, we will follow a similar approach to @supabase/ssr, which involves two functions:

I thought i might be related to this issue, but adding pb.autoCancellation(false); didn't change anything. The try catch block below doesn't produce any messages in the console either.

if you're using pocketbase there's a JS SDK https://github.com/pocketbase/js-sdk

Check out the jsdk for pocketbase and sveltekit it have the solution you looking for : https://www.npmjs.com/package/pocketbase

So I wanted to start tinkering with Svelte and decided I wanted to mess with Pocketbase as a backend to try something new. I set everything up alright, and I'm using the Pocketbase Javascript SDK to authenticate / fetch data.

next we deal with the front-edn by using the provided javascript sdk

Well PocketBase has a framework agnostic js sdk (https://github.com/pocketbase/js-sdk) so you can use it with any frontend framework you feel comfortable. Our small internal tool is a static single page application that just make requests to the server and I haven't stumble on any issue yet.

There is already a JavaScript SDK (https://github.com/pocketbase/js-sdk) that works both in the browser and node.

Dart SDK (targeting mainly Flutter) is also on the way.

Unfortunately I'm not very uptodate with Android (Kotlin) or iOS (Swift) development and therefore community contributions are more than welcomed.