fix: downgrade the driver of sqlite and mariadb to 6.18.0 (#32)#33
fix: downgrade the driver of sqlite and mariadb to 6.18.0 (#32)#33jiashengguo merged 1 commit intomainfrom
Conversation
* fix: downgrade the driver of sqlite and mariadb to 6.18.0 * fix PrismaMariaDb
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 33 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Downgrades Prisma SQLite and MariaDB driver-adapter dependencies to the Prisma 6.x line and updates runtime adapter loading to align with changed adapter export names, along with a patch version bump.
Changes:
- Downgrade
@prisma/adapter-better-sqlite3and@prisma/adapter-mariadbdependency ranges from 7.x to^6.18.0and update the lockfile accordingly. - Update SQLite adapter require logic to support multiple export shapes/names.
- Fix MariaDB adapter symbol name usage (
PrismaMariaDb) and bump package version to0.4.1.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/server.ts | Adjusts adapter module loading to handle adapter export/name differences (SQLite + MariaDB). |
| package.json | Bumps package version and downgrades Prisma adapter dependency ranges to 6.x. |
| pnpm-lock.yaml | Reflects resolved Prisma adapter versions after the dependency changes. |
Files not reviewed (1)
- pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@prisma/adapter-better-sqlite3": "^6.18.0", | ||
| "@prisma/adapter-mariadb": "^6.18.0", |
There was a problem hiding this comment.
The PR title/description says “downgrade … to 6.18.0”, but using a caret range ("^6.18.0") still allows pnpm to resolve newer 6.x versions (the lockfile currently resolves 6.19.2). If the intent is to pin specifically to 6.18.0, change the specifier to an exact version (or at least "~6.18.0") and regenerate the lockfile accordingly; otherwise consider updating the PR description/title to reflect that this is a major downgrade to 6.x, not specifically 6.18.0.
| '@prisma/adapter-better-sqlite3': | ||
| specifier: ^7.3.0 | ||
| version: 7.3.0 | ||
| specifier: ^6.18.0 | ||
| version: 6.19.2 | ||
| '@prisma/adapter-mariadb': | ||
| specifier: ^7.1.0 | ||
| version: 7.2.0 | ||
| specifier: ^6.18.0 | ||
| version: 6.19.2 |
There was a problem hiding this comment.
Lockfile resolves @prisma/adapter-better-sqlite3 and @prisma/adapter-mariadb to 6.19.2 even though the PR states a downgrade “to 6.18.0”. If you really need 6.18.0 specifically, the specifier needs to be pinned (or "~6.18.0") and the lockfile should be regenerated so it resolves to 6.18.x.
| } | ||
| const { PrismaBetterSQLite3 } = require('@prisma/adapter-better-sqlite3') | ||
| const _mod = require('@prisma/adapter-better-sqlite3') | ||
| //Prisma7 renamed PrismaBetterSqlite3 from PrismaBetterSQLite3, support both cases for compatibility |
There was a problem hiding this comment.
Inline comment formatting doesn’t match the surrounding style (missing space after //) and the wording is a bit confusing (“renamed … from …”). For consistency/clarity, adjust to something like “Prisma 7 renamed PrismaBetterSQLite3 to PrismaBetterSqlite3; support both for compatibility”.
| //Prisma7 renamed PrismaBetterSqlite3 from PrismaBetterSQLite3, support both cases for compatibility | |
| // Prisma 7 renamed PrismaBetterSQLite3 to PrismaBetterSqlite3; support both for compatibility |
fix: downgrade the driver of sqlite and mariadb to 6.18.0
fix PrismaMariaDb