Arnaud
7d290c5b1f
visibleToViewer() referenced userFollows as a Drizzle column proxy inside db.query.recipes.findFirst's where — the relational query builder rewrites embedded column refs to the outer query's own table alias regardless of which table they actually belong to, same gotcha already documented and worked around in recipes/page.tsx's search filter. That silently produced SQL referencing a column that doesn't exist on recipes, breaking every recipe page load since 0.41.0. Fixed by using a literal user_follows identifier instead, matching the established workaround. v0.44.1
24 lines
632 B
JSON
24 lines
632 B
JSON
{
|
|
"name": "epicure",
|
|
"version": "0.44.1",
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "pnpm --filter web dev",
|
|
"build": "pnpm --filter web build",
|
|
"lint": "pnpm -r lint",
|
|
"typecheck": "pnpm -r typecheck",
|
|
"db:generate": "pnpm --filter @epicure/db generate",
|
|
"db:migrate": "pnpm --filter @epicure/db migrate",
|
|
"db:seed": "pnpm --filter @epicure/db seed",
|
|
"db:backfill-usernames": "pnpm --filter @epicure/db backfill-usernames",
|
|
"db:studio": "pnpm --filter @epicure/db studio"
|
|
},
|
|
"devDependencies": {
|
|
"typescript": "^5.8.3"
|
|
},
|
|
"engines": {
|
|
"node": ">=22",
|
|
"pnpm": ">=11"
|
|
}
|
|
}
|