typescript why. typescript how.
0 Boosts
0 Likes
fediverse_user
@fediverse_user
·
activity timestamp
2 yr. ago
@jonny I’ve had that happen to me before. It thinks one “Kysely<any>” is not the same thing as the other “Kysely<any>”. Why, though… no idea. Are there two different definitions of “Kysely” somewhere?
@jonny whaaaat
I’d guess the problem is inside the promise piece that’s collapsed to “…” except that there’s two more “x is not assignable to x” in that screenshot too besides what you highlighted
@maco it was from private attributes, two versions of kysely installed, one for the dialect and one for the main package, so i just needed to make it a peer dependency in the dialect. always learning something new with typescript lol