[Snyk] Upgrade @prisma/client from 4.7.1 to 4.16.2 #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @prisma/client from 4.7.1 to 4.16.2. See this package in npm: https://www.npmjs.com/package/@prisma/client See this project in Snyk: https://app.snyk.io/org/alirezanqp/project/09cb2949-4425-45d7-b0e2-550d8ac5012a?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @prisma/client from 4.7.1 to 4.16.2.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: @prisma/client
Today, we are issuing the
4.16.2patch release.Fixes in Prisma Client
$allModels: { $allOperations }sets query type toneverundefinedexplicitly passed toselect/includeToday, we are issuing the
4.16.1patch release.Fixes in Prisma Client
$extendin factory function whencompilerOptions.compositeistrueRead more
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
For this release, we focused on fixing bugs and making smaller quality-of-life improvements.
Support for custom arguments for
prisma db seedThis release adds support for defining and passing arbitrary arguments to
prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to theprisma db seedcommand. A few example use-cases include, but are not limited to:Here is an example
seed.tsfile that defines custom arguments for seeding different data in different environments:import { parseArgs } from "node:util";
const options = {
environment: { type: 'string', },
}
async function main() {
const { values: { environment } } = parseArgs({ options })
switch (environment) {
case "development":
/** do something for development /
break;
case "test":
/* do something for test environment */
break;
default:
break;
}
}
main()
You can then provide the
environmentargument when executing the seed script as follows:Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.
Improved error messages when Query Engine file is not found
This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:
We hope these error messages are helpful while debugging your application.
Prisma VS Code extension improvements
In this release, we made a few improvements to our VS Code extension:
Updated the file system watcher that is responsible for restarting the TypeScript server when
prisma generateis run to ensure the types are in syncNote:
4.15.0or higherAdded Quick Fixes action for unique identifiers for MongoDB to add the
@ map("_id")attribute function when it’s missing on an identifier fieldScreen.Recording.2023-05-17.at.19.22.20.mov
Screen.Recording.2023-05-17.at.19.22.20.mov
Support for renaming symbols for composite types and views
type-symbol-rename.mov
type-symbol-rename.mov
Fixes and improvements
Prisma Client
Error: write EPIPEon WSL <-> Windowsprisma generateis blocked byquery-engine-rhel-openssl-1.0.xopening in Notepad on Windowsnode_modules(from another platform) leads to platform engine not being presentoutputQuery engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.xCannot find name '$PrismaModel'due to featureextendedWhereUniquewith preview featurefieldReferenceDatevalues silently turn intonullsfieldReferenceis not working with enumsPrisma Migrate
prisma db seedto the seed commandLanguage tools (e.g. VS Code)
@ map("_id")annotationCredits
Huge thanks to @ RobertCraigie, @ KhooHaoYit, @ art049, @ luxaritas, @ mrazauskas, @ maxmartynov, @ haneenmahd for helping!
📺 Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.
The stream takes place on YouTube on Thursday, June 1 at 5 pm Berlin | 8 am San Francisco.
Today, we are issuing the
4.14.1patch release.Fix in Prisma Client
Read more