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

Can't update to replicate@1.0.1 in my app because dependencies and peerDependancies of langchain-community register replicate@^0.29.4 #7118

Open
5 tasks done
XStarlink opened this issue Oct 30, 2024 · 2 comments
Labels
auto:bug Related to a bug, vulnerability, unexpected error with an existing feature

Comments

@XStarlink
Copy link

Checked other resources

  • I added a very descriptive title to this issue.
  • I searched the LangChain.js documentation with the integrated search.
  • I used the GitHub search to find a similar question and didn't find it.
  • I am sure that this is a bug in LangChain.js rather than my code.
  • The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code

No code needed

Error Message and Stack Trace (if applicable)

No response

Description

Hello,
I'm encountering an issue while trying to update to replicate@1.0.1 in my application. The current dependencies and peerDependencies are registering replicate@^0.29.4, which prevents the update.

Steps to Reproduce

Attempt to update replicate to version 1.0.1 using npm or yarn.
Notice the error related to conflicting versions.

Expected Behavior

I expect to be able to update to replicate@1.0.1 without any dependency conflicts.

Thank you!

System Info

Mac 15.1.0
Node v20.15.0

@dosubot dosubot bot added the auto:bug Related to a bug, vulnerability, unexpected error with an existing feature label Oct 30, 2024
@jacoblee93
Copy link
Collaborator

Hey apologies - we can and should loosen this

@XStarlink
Copy link
Author

XStarlink commented Nov 6, 2024

Thanks @jacoblee93!

Just wanted to point out that in replicate v1.0.0, there's a significant change in the replicate.run() method behavior. It now directly returns the file instead of requiring an additional fetch for the image result (as documented in their release notes).

This change might impact the langchain-community package integration, as it represents a breaking change in how the results are handled.

Thanks for looking into this!

Edit: After checking, I couldn't find any usage of replicate.run() in langchain-community, so this breaking change shouldn't actually affect the package.

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

2 participants