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
I have verified that the bug I'm about to report hasn't been filed before.
What version of drizzle-orm are you using?
0.39.1
What version of drizzle-kit are you using?
0.30.4
Other packages
No response
Describe the Bug
We were integrating @sentry/node into the project that uses drizzle-orm, and developing using vite dev server. This issue was encountered during development.
We followed Sentry's documentation to integrate instrumentation. We are not using any monorepo setup.
After bundling and building the code for production, the issues goes away even the Sentry instrumentation is present.
The build is working now after I moved the operators to import from drizzle-orm/sql. Not sure if this will work permenantly since the problem seems to be intermittent.
import { SQL, sql } from "drizzle-orm";
import { inArray, and, eq } from "drizzle-orm/sql";
Thank you @bensenescu for providing a workaround. It would still be great if the Drizzle team can provide insights on why this is happening and hopefully a proper solution from either the Sentry node package or Drizzle ORM.
Report hasn't been filed before.
What version of
drizzle-orm
are you using?0.39.1
What version of
drizzle-kit
are you using?0.30.4
Other packages
No response
Describe the Bug
We were integrating
@sentry/node
into the project that usesdrizzle-orm
, and developing using vite dev server. This issue was encountered during development.We followed Sentry's documentation to integrate instrumentation. We are not using any monorepo setup.
After bundling and building the code for production, the issues goes away even the Sentry instrumentation is present.
Base project setup with Drizzle, the bundler and builder: https://github.com/xanthous-tech/hono-astro-remix-template
I can try to provide a repro on a branch.
This is related in #3726 , but it is unresolved, so I re-opened it.
The text was updated successfully, but these errors were encountered: