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

Conflict while npm install latest langchain #4337

Closed
avk-saas opened this issue Feb 8, 2024 · 4 comments
Closed

Conflict while npm install latest langchain #4337

avk-saas opened this issue Feb 8, 2024 · 4 comments
Assignees
Labels
auto:bug Related to a bug, vulnerability, unexpected error with an existing feature

Comments

@avk-saas
Copy link

avk-saas commented Feb 8, 2024

npm install langchain gives dependancy conflict with replicate and puppeteer...these version have to be upgraded

Copy link

dosubot bot commented Feb 8, 2024

🤖

Hey there @avk-saas! 🚀 Nice to see you back. Hope you're doing awesome!

Based on the similar issues found in the langchainjs repository, it seems like the dependency conflict you're experiencing might be due to the version of cohere-ai installed in your project. Here are the steps you can follow to resolve this:

  1. Uninstall the current version of cohere-ai in your project:
npm uninstall cohere-ai
  1. Install the version of cohere-ai required by langchain:
npm install [email protected]
  1. Uninstall the current version of langchain in your project:
npm uninstall langchain
  1. Install the new version of langchain:
npm install langchain

If the issue persists, you can also try running:

npm install langchain --with-legacy-peer-deps

This command will ignore the peer dependencies and install langchain anyway.

Alternatively, you can use yarn or pnpm which may handle peer dependencies differently.

Additionally, a new version of chromadb has been released, which you can try installing:

npm install chromadb

This should resolve the dependency tree issue.

If the issue still persists, it might be due to other conflicting dependencies in your project. In this case, you might need to update your dependencies to the versions required by LangChain 0.0.144.

Please let me know if this helps or if you need further assistance.

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot dosubot bot added the auto:bug Related to a bug, vulnerability, unexpected error with an existing feature label Feb 8, 2024
@woutersteven
Copy link

Also having this issue, subscribing to the thread.

@jacoblee93
Copy link
Collaborator

For now can you use --with-legacy-peer-deps or yarn/pnpm?

We should start splitting more of these packages out/loosening restrictions too.

@jacoblee93 jacoblee93 self-assigned this Feb 17, 2024
@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label May 18, 2024
Copy link

dosubot bot commented May 18, 2024

Hi, @avk-saas,

I'm helping the langchainjs team manage their backlog and am marking this issue as stale. It seems like the issue involves a conflict when trying to install the latest version of langchain using npm, specifically relating to dependency conflicts with replicate and puppeteer. The comments suggest steps to resolve the conflict, including uninstalling and reinstalling specific versions of dependencies, using --with-legacy-peer-deps with npm, or trying alternative package managers like yarn or pnpm. Additionally, there's a suggestion to install a new version of chromadb to resolve the dependency tree issue. Other users have also reported experiencing the same issue and are following the thread for updates.

Could you please confirm if this issue is still relevant to the latest version of the langchainjs repository? If it is, please let the langchainjs team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days. Thank you!

@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto:bug Related to a bug, vulnerability, unexpected error with an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants