too_easy Comments - Convex Community

too_easy

Posts Comments

CCConvex Community

•Created by too_easy on 4/29/2025 in #support-community

Any way to populate convex environment variables via 3rd part

Or to sync env variables with vercel somehow?

4 replies

CCConvex Community

•Created by too_easy on 4/10/2025 in #support-community

CONVEX_SITE_URL undefined in functions?

@Nicolas figured out that env.CONVEX_SITE_URL becomes undefined when using ctx.runQuery(api.getUrl). However, using useQuery(api.getUrl) - i.e. using the function directly via the client it is defined as it should be. Using a function via another function it seems to become undefined. Repro:

export const getTest = query({
  handler: async (ctx) => {
    console.log({
      URL: process.env.CONVEX_CLOUD_URL,
      SITE: process.env.CONVEX_SITE_URL,
    });

    return {
      URL: process.env.CONVEX_CLOUD_URL,
      SITE: process.env.CONVEX_SITE_URL,
    };
  },
});

export const getTest = query({
  handler: async (ctx) => {
    console.log({
      URL: process.env.CONVEX_CLOUD_URL,
      SITE: process.env.CONVEX_SITE_URL,
    });

    return {
      URL: process.env.CONVEX_CLOUD_URL,
      SITE: process.env.CONVEX_SITE_URL,
    };
  },
});

This logs and returns correctly when doing either on frontend:

convexReactClient.query(api.getTest, {})

convexReactClient.query(api.getTest, {})

const {} = useQuery(api.getTest, {})

const {} = useQuery(api.getTest, {})

However doing this in convex backend:

const someOtherQuery = getTest = query({
  handler: async (ctx) => {
    const envVars = await ctx.runQuery(api.getTest, {});
    console.log(envVars) // {URL: undefined, SITE: undefined}
  }
});

const someOtherQuery = getTest = query({
  handler: async (ctx) => {
    const envVars = await ctx.runQuery(api.getTest, {});
    console.log(envVars) // {URL: undefined, SITE: undefined}
  }
});

Logs and returns undefined - so assuming some issue with propagation of env variables with ctx transfer between functions?

5 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

this we haven't shipped

Meaning you will ship object sync at some point? Yeah I guess you could say optimistic updates is the key, less the offline-first requirement. So just to confirm, if 2 users write to the same document, those writes happen sequentially, and its then last write wins?

65 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

I don't see how acid transactions alone solve the problem of timing

65 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

Nah offline isn't that important tbh, just that users are able to make conflic free collabs

65 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

Yeah tbh I ran into this problem pretty quick with Yjs, hence the switch to Loro, because you can shallow snapshot and cull unused history effectively. But yeah, what you're saying totally makes sense, in that case what's a solution for complex collaborative structures using convex? - I'm not talking a simple text document, but a collaboration use case with multiple collaborative datastructures.

65 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

Correct me if I'm wrong but doing something like in nodejs environment:

const snapshot = await ctx.runQuery(api.getSnapshot);

// do some thing with Loro

await ctx.runMutation(api.updateSnapshot)

const snapshot = await ctx.runQuery(api.getSnapshot);

// do some thing with Loro

await ctx.runMutation(api.updateSnapshot)

Assuming getSnapshot reads a point in time, Loro changes that snapshot as a binary / bytes / buffer, then calls an update snapshot - isn't there a chance another call was made simultaneously in between and that data was overwritten? I guess if the crdt is doing its job then its probably fine for it to be overwritten as the client could just request the updates be made again?

22 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

What's everyone's general thoughts on automerge re performance and devx etc..?

65 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

Does that mean its sorta a wont do? Should I scrap Loro, picking a conflict resolution system is business critical for us, need to make a call soonish. Would prefer to use Loro than Yjs - might have to even use automerge lol

65 replies

CCConvex Community

•Created by mikeysee on 1/17/2024 in #support-community

Error while trying to use Loro CRDTs (Uncaught ReferenceError: FinalizationRegistry is not defined)

@ballingt @sujayakar any updates on using Loro ☝️ ?

65 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

The problem with putting the crdt lib in node actions is that its possible for overwrites to happen

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

Looking at this from the other way, because I can't seem to find a nice wasm loading function for loro like automerge - Is there anyway to get acid transactions while using node environment actions?

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

The convex compile/upload error I get literally says "top level await is not supported"

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

Pretty sure the wasm part is fine and the error comes from how the wasm library is instantiated (using a top level await) which is happening in js land, not wasm land. Loro runs fine in the convex "use node" environment - so I don't see why it couldn't run in the convex native v8 environment - perhaps it is because one is using commonJS and the other is using esm?

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

top level await is what I need, pretty sure I read somewhere that wasm is supported on the convex v8 runtime already right? If so, its just the top level await that is breaking things

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

Need it in convex backend tbh - the server is a central authority that can merge updates neatly via transactions. If it was left to client (or even actions) theres a chance updates get overwritten rather than merged

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

Yjs would work fine inside mutations/queries but its causes other issues with how large the update history gets over time..

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

I.e. have it work in mutations/queries rather than actions

22 replies

CCConvex Community

•Created by too_easy on 2/18/2025 in #support-community

possible support for top level await from npm packages

I'd really like to have it work on the convex V8 runtime not the node runtime so that I can make use of acid transaction

22 replies