Khefas
commented
2 days ago Ive got same error here, after audit fix return axios package should be replaced...
npm audit report
axios 0.8.1 - 0.27.2 Severity: moderate Axios Cross-Site Request Forgery Vulnerability - https://github.com/advisories/GHSA-wf5p-g6vw-rhxx No fix available node_modules/axios node_modules/ton-x/node_modules/axios node_modules/ton-x/node_modules/ton/node_modules/axios ton >=7.14.0 Depends on vulnerable versions of axios node_modules/ton node_modules/ton-x/node_modules/ton @ton-community/blueprint * Depends on vulnerable versions of ton Depends on vulnerable versions of ton-x node_modules/@ton-community/blueprint ton-x >=0.1.0 Depends on vulnerable versions of axios Depends on vulnerable versions of ton node_modules/ton-x
4 moderate severity vulnerabilities
To address issues that do not require attention, run: npm audit fix
Some issues need review, and may require choosing a different dependency.
Hi, We clone the latest code and checkout main branch, and after running "npm install", still get following errors. and our node version is "v18.19.1"
Could you please give a help? Thanks alot.
ubuntu ~/liquid-staking-contract$ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: liquid_staking@0.0.1 npm ERR! Found: ton-core@0.49.1 npm ERR! node_modules/ton-core npm ERR! dev ton-core@"^0.49.0" from the root project npm ERR! peer ton-core@">=0.48.0" from @ton-community/blueprint@0.10.0 npm ERR! node_modules/@ton-community/blueprint npm ERR! dev @ton-community/blueprint@"^0.10.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer ton-core@">=0.53.0" from ton@13.9.0 npm ERR! node_modules/ton npm ERR! dev ton@"^13.4.1" from the root project npm ERR! peer ton@">=13.4.1" from @ton-community/blueprint@0.10.0 npm ERR! node_modules/@ton-community/blueprint npm ERR! dev @ton-community/blueprint@"^0.10.0" 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! npm ERR! For a full report see: npm ERR! /home/ubuntu/.npm/_logs/2024-08-13T09_22_28_877Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-08-13T09_22_28_877Z-debug-0.log