swagger-api / swagger-api/swagger-editor
Building and running an image locally fails on first step
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.5k
- Forks
- 2.4k
- Avg merge
- 17h 15m
- Merged PRs (30d)
- 18
Description
Building and running an image locally fails on first step
Following the instructions in README.md for building and running an image locally fails, but I did a simple git clone before starting the process.
$ git clone https://github.com/swagger-api/swagger-editor.git
Cloning into 'swagger-editor'...
remote: Enumerating objects: 64560, done.
remote: Counting objects: 100% (536/536), done.
remote: Compressing objects: 100% (249/249), done.
remote: Total 64560 (delta 477), reused 287 (delta 287), pack-reused 64024 (from 4)
Receiving objects: 100% (64560/64560), 2.34 GiB | 12.25 MiB/s, done.
Resolving deltas: 100% (41645/41645), done.
# downlaoding 2.34 GiB, OK!
my@pc-work:~/path/XYZ$ cd swagger-editor
my@pc-work:~/path/XYZ/swagger-editor$ npm install
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @cfaester/enzyme-adapter-react-18@0.8.0
npm error Found: enzyme@3.3.0
npm error node_modules/enzyme
npm error dev enzyme@"=3.3.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer enzyme@"^3.11.0" from @cfaester/enzyme-adapter-react-18@0.8.0
npm error node_modules/@cfaester/enzyme-adapter-react-18
npm error dev @cfaester/enzyme-adapter-react-18@"^0.8.0" from the root project
npm error
npm error Conflicting peer dependency: enzyme@3.11.0
npm error node_modules/enzyme
npm error peer enzyme@"^3.11.0" from @cfaester/enzyme-adapter-react-18@0.8.0
npm error node_modules/@cfaester/enzyme-adapter-react-18
npm error dev @cfaester/enzyme-adapter-react-18@"^0.8.0" 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.
npm error
npm error
npm error For a full report see:
npm error /home/my/.npm/_logs/2025-10-13T12_34_03_531Z-eresolve-report.txt
# notice
npm error A complete log of this run can be found in: /home/my/.npm/_logs/2025-10-13T12_34_03_531Z-debug-0.log
System: Linux, Ubuntu 20
- npm v10.9.2
- node.js v22.15.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the README.md instructions for building and running an image locally and reproducing the initial npm install failure with the reported Node.js and npm versions. Inspect the project's dependency declarations for the enzyme and @cfaester/enzyme-adapter-react-18 conflict; done means a fresh clone can complete the documented setup without this resolution error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100