You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, deploying to both aws lambda and vercel throwing same prisma client not generated yet error even though everything works fine locally.
my project folder structure places prisma folder which contains the schema.prisma file in the root folder.
stack trace:
" File \"/var/lang/lib/python3.13/importlib/__init__.py\", line 88, in import_module\n return _bootstrap._gcd_import(name[level:], package, level)\n",
" File \"<frozen importlib._bootstrap>\", line 1387, in _gcd_import\n",
" File \"<frozen importlib._bootstrap>\", line 1360, in _find_and_load\n",
" File \"<frozen importlib._bootstrap>\", line 1331, in _find_and_load_unlocked\n",
" File \"<frozen importlib._bootstrap>\", line 935, in _load_unlocked\n",
" File \"<frozen importlib._bootstrap_external>\", line 1022, in exec_module\n",
" File \"<frozen importlib._bootstrap>\", line 488, in _call_with_frames_removed\n",
" File \"/var/task/main.py\", line 2, in <module>\n from app.routers import transactions\n",
" File \"/var/task/app/routers/transactions.py\", line 2, in <module>\n from ..controllers.transactions.get_transactions import get_Transactions\n",
" File \"/var/task/app/controllers/transactions/get_transactions.py\", line 1, in <module>\n from prisma import Prisma\n",
" File \"<frozen importlib._bootstrap>\", line 1412, in _handle_fromlist\n",
" File \"/opt/python/prisma/__init__.py\", line 53, in __getattr__\n raise RuntimeError(\n"
]
Note: It's not the transactions controller or route that is the problem if I put any route as first in order of route calls from the index file, that is what will appear in the stack trace.
Everything is fine locally but production fails. Thanks in advance
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My set up is quite simple:
However, deploying to both aws lambda and vercel throwing same prisma client not generated yet error even though everything works fine locally.
my project folder structure places prisma folder which contains the schema.prisma file in the root folder.
stack trace:
Note: It's not the transactions controller or route that is the problem if I put any route as first in order of route calls from the index file, that is what will appear in the stack trace.
Everything is fine locally but production fails. Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions