Bug: Javascript SDK Functions | .create | Table Object Passed as Query Bind Issue

[SoulThread2597]

Describe the bug

Im running SurrealDB 3.0.0 with SurrealDB's npm package version 2.0.0-beta.2.

My question is in regards to create function that is provided. In this beta version the second argument of data is removed, and is instead replace with .content(..) after the create is called. There is no documentation that i have found that explains this but based on logic and reasoning, thats what ive assumed. I continuously keep getting this error Cannot execute CREATE statement using value: { }. Ive tried many different ways of setting it up, and im just lost what its complaining about. If someone could give me an example of it being correct and working and/or clarify that this is an actual bug, that would be great.

Steps to reproduce

Create a table called test in your database and setup the access tokens and connection system and assign the database connection to the variable called 'database'.

An example of what isn't working:

const test = await database.create(new RecordId('test', "temp")).content({
    test:"test"
});

Expected behaviour

I expect it to create a record with the id 'temp' on table 'test' with the following data:

• test: "test"

SurrealDB version

SurrealDB 3.0.0

JavaScript SDK version

2.0.0-beta.2

Contact Details

contact@soulthread.dev

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct (repository /surrealdb.js)

• I agree to follow this project's Code of Conduct

[SoulThread2597]

So an addition to this issue that ive discovered. For context, my project is a website, nextjs to be specific. Putting the code in the instrumentation.ts file makes it work fine, however accessing database through global (global.database for the above code) is where the issue is stemming from it seems. so instead, it would be the following in lets say an api route

export async function GET(request: NextRequest) {
  try {
    const temp = await global.database.create(new RecordId('test', "temp"))
      .content({
        test:"test"
      });

    return NextResponse.json({ message: 'Test endpoint is working', temp })
  } catch (error) {
    console.error('Error in GET /api/test:', error)
    return NextResponse.json({ error: 'Internal Server Error' }, { status: 500 })
  }
}

Edit: It seems to actually be a query issue, however im still unsure on why it works in instrumentation.ts and not an api route. It has something to with the table object. An example query with its bindings that it throws out is

const temp = await global.database.query("CREATE $bind__30 CONTENT $bind__31", { 
  bind__30: new Table('test'), 
  bind__31: { 
    test: 'test' 
  } 
})