How can I publish my own langchain clone package #1936
Replies: 1 comment
-
Answer generated by a 🤖 AnswerI understand that you're trying to publish your own version of LangChain, but you're encountering configuration errors. When you try to publish under the original name, you're blocked because that namespace is already taken. However, when you attempt to change the name, you're still running into issues. Here's a potential solution to your problem: First, you need to modify the
{
"name": "myusername-langchain",
...
}
After you've made these changes, you should be able to publish your package to npm without encountering namespace issues. You can do this by running If you're still experiencing build and publish errors after changing the This is just one potential solution to your problem. If you find it helpful and believe it could be useful to others, I encourage you to make a pull request to update the documentation. This way, other users who encounter the same issue can benefit from your experience. SourcesThis response is meant to be useful, save you time, and share context. 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. |
Beta Was this translation helpful? Give feedback.
-
I need certain functions to be exported and I already did that and tested it via
npm link
now I just need to publish the custom langchain package. But when I try to I constantly run into configuration errors.When I leave the npm name as langchain I can get all the way up to the publishing step where of course it gets blocked because langchain already has the namespace. But when I try to change the npm name I run into build and publish errors. How should I go about publishing a copy of langchain? Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions