[Snyk] Upgrade zod-validation-error from 3.0.0 to 3.3.0 #5
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.
Snyk has created this PR to upgrade zod-validation-error from 3.0.0 to 3.3.0.
ℹ️ 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.
The recommended version is 6 versions ahead of your current version.
The recommended version was released on 3 months ago.
Release notes
Package name: zod-validation-error
Minor Changes
66f5b5d: Match
ZodError
via heuristics instead of relying oninstanceof
.Why? Because we want to ensure that zod-validation-error works smoothly even when multiple versions of zod have been installed in the same project.
Minor Changes
fromError
API which is a less strict version offromZodError
fromZodError
and throw dev-friendlyTypeError
suggesting usage offromError
insteadMinor Changes
Patch Changes
Patch Changes
Patch Changes
Major Changes
deb4639: BREAKING CHANGE: Refactor
ValidationError
to acceptErrorOptions
as second parameter.What changed?
Previously,
ValidationError
acceptedArray<ZodIssue>
as 2nd parameter. Now, it acceptsErrorOptions
which contains acause
property. Ifcause
is aZodError
then it will extract the attached issues and expose them overerror.details
.Why?
This change allows us to use
ValidationError
like a native JavaScript Error. For example, we can now do:try {
// attempt to do something that might throw an error
} catch (err) {
throw new ValidationError('Something went deeply wrong', { cause: err });
}
How can you update your code?
If you are using
ValidationError
directly, then you need to update your code to passErrorOptions
as a 2nd parameter.// before
const err = new ValidationError('Something went wrong', zodError.issues);
// after
const err = new ValidationError('Something went wrong', { cause: zodError });
If you were never using
ValidationError
directly, then you don't need to do anything.Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: