build(deps): Bump zod-validation-error from 2.1.0 to 3.0.3

[dependabot[bot]]

Bumps zod-validation-error from 2.1.0 to 3.0.3.

Release notes

Sourced from zod-validation-error's releases.

v3.0.3

Patch Changes

• 2f1ef27: Bundle code as a single index.js (cjs) or index.mjs (esm) file. Restore exports configuration in package.json.

v3.0.2

Patch Changes

• 24b773c: Revert package.json exports causing dependant projects to fail

v3.0.1

Patch Changes

• 3382fbc: 1. Fix issue with ErrorOptions not being found in earlier to es2022 typescript configs. 2. Add exports definition to package.json to help bundlers (e.g. rollup) identify the right module to use.

v3.0.0

Major Changes

• deb4639: BREAKING CHANGE: Refactor ValidationError to accept ErrorOptions as second parameter.

  What changed?

  Previously, ValidationError accepted Array<ZodIssue> as 2nd parameter. Now, it accepts ErrorOptions which contains a cause property. If cause is a ZodError then it will extract the attached issues and expose them over error.details.

  Why?

  This change allows us to use ValidationError like a native JavaScript Error. For example, we can now do:

  import { ValidationError } from 'zod-validation-error';
  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 pass ErrorOptions as a 2nd parameter.

  import { ValidationError } from 'zod-validation-error';
  // before
  const err = new ValidationError('Something went wrong', zodError.issues);
  // after
  const err = new ValidationError('Something went wrong', { cause: zodError });
  

... (truncated)

Changelog

Sourced from zod-validation-error's changelog.

3.0.3

Patch Changes

• 2f1ef27: Bundle code as a single index.js (cjs) or index.mjs (esm) file. Restore exports configuration in package.json.

3.0.2

Patch Changes

• 24b773c: Revert package.json exports causing dependant projects to fail

3.0.1

Patch Changes

• 3382fbc: 1. Fix issue with ErrorOptions not being found in earlier to es2022 typescript configs. 2. Add exports definition to package.json to help bundlers (e.g. rollup) identify the right module to use.

3.0.0

Major Changes

• deb4639: BREAKING CHANGE: Refactor ValidationError to accept ErrorOptions as second parameter.

  What changed?

  Previously, ValidationError accepted Array<ZodIssue> as 2nd parameter. Now, it accepts ErrorOptions which contains a cause property. If cause is a ZodError then it will extract the attached issues and expose them over error.details.

  Why?

  This change allows us to use ValidationError like a native JavaScript Error. For example, we can now do:

  import { ValidationError } from 'zod-validation-error';
  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 pass ErrorOptions as a 2nd parameter.

  import { ValidationError } from 'zod-validation-error';
  // before
  

... (truncated)

Commits

• fe99863 chore: bump version to 3.0.3
• f5f5ccc chore: version packages
• 2f1ef27 chore: add changesets
• c980b54 chore: restore id-length eslint rule
• 33eb84b chore: do not exclude test files from type-checking
• 66c1973 feat: add simple deno test to CI workflow
• c2a10cb refactor: force use of import extensions to make the code deno-compat
• 7d72bef chore: upgrade nodejs version to v20 and github actions to latest
• 4274fbb chore: explicitly define authors and contributors in package.json
• f1d5786 feat: adopt tsup for producing the dist files + switch to mjs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #53.