Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install fails on Linux #379

Open
7 tasks done
tomleo opened this issue Mar 30, 2022 · 1 comment
Open
7 tasks done

Install fails on Linux #379

tomleo opened this issue Mar 30, 2022 · 1 comment

Comments

@tomleo
Copy link

tomleo commented Mar 30, 2022

  • System Information

    • Ubuntu 20.04.4 LTS
    • Node version: v16.13.1
  • Describe the bug

tom@orbital[~/hacking/learn-sql/sql-fundamentals] (master) $ npm install --no-optional
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @mikeworks/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/ts-node
npm ERR!   dev ts-node@"5.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer ts-node@"^3.3.0" from [email protected]
npm ERR! node_modules/db-migrate-plugin-typescript
npm ERR!   dev db-migrate-plugin-typescript@"2.0.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! See /home/tom/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tom/.npm/_logs/2022-03-30T01_59_10_114Z-debug-0.log
  • To Reproduce
    Steps to reproduce the behavior:
  1. Clone the repo
  2. Run npm install --no-optional
  3. See error
  • Expected behavior
    npm install to work

  • Additional context (optional)
    I have nodenv on my machine, so I can switch to a different version of node if required.

@tomleo
Copy link
Author

tomleo commented Apr 7, 2022

Furthermore if I knew the exact node.js, npm, and OS combo that will work with this repo, I could set this project up in a docker container, without that I'm guessing the issue is 4-year-old dependencies are the source of issue here.

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

No branches or pull requests

1 participant