-
-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: DrizzleSQLiteAdapter type error breaks build #1664
Comments
This is probably because you're using an older version of Drizzle, and that's unfortunately what happens when we built stuff on top off pre-1.0 libraries. It's only a type issue right? |
@pilcrowonpaper here I managed to find my older lock file version (it wasn't on git, duh) and reinstalled deps, now it works. Drizzle version changed from 0.31.2 to 0.31.4. Not sure if it was causing the issue (didn't found anything breaking in their Changelog). here's a diff
|
Same problem here after upgrading Downgrading back to |
I should probably reopen this, so @pilcrowonpaper could decide on closing by himself. |
Probably related as downgrading from isPrimaryKey: any;
isAutoincrement: any;
hasRuntimeDefault: any;
generated: any; |
This is the base type for columns in
And the type definition for the adapter is
So yep it's just some extra fields that don't exist on Looking at the constraints in |
id: text("id").primaryKey(),
userId: text("user_id")
.notNull()
.references(() => user.id, {
onDelete: "cascade"
}),
expiresAt: integer("expires_at").notNull(),
}) i fixed this by removing notNull() from id, (with latest drizzle-orm and latest adapter |
Package
@lucia-auth/session-drizzle
Describe the bug
Not sure which exactly package started to cause the issue, since I had none before, but after I removed lock file, the error appeared:
I have no idea what is happening here, and how to fix it. Tried to lock older versions, still error.
Using next, drizzle, turso/libsql
The text was updated successfully, but these errors were encountered: