splide-extension-auto-scroll icon indicating copy to clipboard operation
splide-extension-auto-scroll copied to clipboard

Broken ts-jest dependency

Open axis80 opened this issue 2 years ago • 0 comments

Checks

  • [X] Not a duplicate.
  • [X] Not a question, feature request, or anything other than a bug report directly related to Splide. Use Discussions for these topics: https://github.com/Splidejs/splide/discussions

Version

0.5.3

Description

When I clone this repo and run npm install to install dependencies, it results in the following error messages about a broken ts-jest dependency. I was able to resolve this and get the dependencies to install cleanly using npm update ts-jest. I will submit a PR for this issue momentarily.

npm resolution error report

2023-05-03T16:10:59.829Z

While resolving: [email protected] Found: [email protected] node_modules/babel-jest dev babel-jest@"^29.0.1" from the root project babel-jest@"^29.0.1" from [email protected] node_modules/jest-config jest-config@"^29.0.1" from @jest/[email protected] node_modules/@jest/core @jest/core@"^29.0.1" from [email protected] node_modules/jest dev jest@"^29.0.1" from the root project @jest/core@"^29.0.1" from [email protected] node_modules/jest-cli jest-cli@"^29.0.1" from [email protected] node_modules/jest dev jest@"^29.0.1" from the root project jest-config@"^29.0.1" from [email protected] node_modules/jest-cli jest-cli@"^29.0.1" from [email protected] node_modules/jest dev jest@"^29.0.1" from the root project

Could not resolve dependency: peerOptional babel-jest@"^28.0.0" from [email protected] node_modules/ts-jest dev ts-jest@"next" from the root project

Conflicting peer dependency: [email protected] node_modules/babel-jest peerOptional babel-jest@"^28.0.0" from [email protected] node_modules/ts-jest dev ts-jest@"next" from the root project

Fix the upstream dependency conflict, or retry this command with --force, or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.

Reproduction Link

No response

Steps to Reproduce

  1. Clone the master branch of the repo
  2. Run npm install

Expected Behaviour

I expect npm install to complete without errors.

axis80 avatar May 03 '23 17:05 axis80