search

amagovpt / monitor-server

monitor-server is part of the Portuguese Observatory of Web Accessibility
2 stars 6 forks source link

Dependencies cannot be satisfied #6

Open thomasfischer-his opened 2 years ago

thomasfischer-his commented 2 years ago

When running npm install, it seems like the dependencies cannot be satisfied due to a version conflict:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: monitor-server@0.1.0
npm ERR! Found: typeorm@0.2.45
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"^0.2.41" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typeorm@"^0.3.0" from @nestjs/typeorm@8.1.4
npm ERR! node_modules/@nestjs/typeorm
npm ERR!   @nestjs/typeorm@"^8.0.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /root/.npm/eresolve-report.txt for a full report.

From what I see is that on one side typeorm 0.2.41 is pulled in directly via package.json (requirement "typeorm": "^0.2.41"), but on the other side the dependency "@nestjs/typeorm": "^8.0.2" pulls in @nestjs/typeorm 8.1.4 which in its package.json has a dependency on typeorm 0.3.6 ("typeorm": "0.3.6").

Can someone please check which version numbers can be changed/increased in order to get this software to work again?

AntonioEstriga commented 2 years ago

Hi, the problem should be fixed on the master branch. If your purpose is just to run accessibility evaluations, I think you should checkout https://github.com/qualweb/core. It´s the automatic accessibility evaluator used in this project.