Skip to content

Conversation

@sifisatz
Copy link
Contributor

Update dependencies: @faker-js/faker to 9.2.0, @anatine/graphql-codegen-zod to 0.4.1, @anatine/graphql-zod-validation to 0.9.1,

…gen-zod to 0.4.1, @anatine/graphql-zod-validation to 0.9.1,
@nx-cloud
Copy link

nx-cloud bot commented Nov 26, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 1dc014c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 2 targets

Sent with 💌 from NxCloud.

@Brian-McBride Brian-McBride merged commit 1b4925b into anatine:main Jan 20, 2025
2 checks passed
@kyletolle
Copy link

I'm trying to include this zod-mock package in my project, but am having trouble because of the faker version 8 limit conflicting with the faker 9.x we're using.

This PR addresses that issue, I am pretty sure, but it does not appear to have been released yet. Any chance of there being a release soon with this change?

For reference, here's an example of the error I'm currently seeing.

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @faker-js/[email protected]
npm error node_modules/@faker-js/faker
npm error   @faker-js/faker@"^9.4.0" from [email protected]
npm error   path/to/project
npm error     [email protected]
npm error     node_modules/project
npm error       workspace path/to/project from the root project
npm error
npm error Could not resolve dependency:
npm error peer @faker-js/faker@"^7.0.0 || ^8.0.0" from @anatine/[email protected]
npm error node_modules/@anatine/zod-mock
npm error   @anatine/zod-mock@"^3.13.5" from [email protected]
npm error   path/to/project
npm error     [email protected]
npm error     node_modules/project
npm error       workspace path/to/project from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

@kyletolle
Copy link

Until a release is done, I'll be able to work around this by adding an override section to my package.json

  "overrides": {
    "@anatine/zod-mock": {
      "@faker-js/faker": "^9.4.0"
    }
  },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants