Langchain does not build

[hannibalov]

Checked other resources

• I added a very descriptive title to this question.
• I searched the LangChain documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.

Commit to Help

• I commit to help with one of those options 👆

Example Code

No code

Description

I'm trying to build a custom agent in javascript, to run DAX queries for Power BI. There is an equivalent in python, so I tried following the guideline to contribute: https://js.langchain.com/docs/contributing . I forked the project and cloned in into my machine, but the project doesn't build. I ran yarn and yarn build in {project}/langchain and {project}/langchain-community, but I always get errors:

➤ YN0009: │ @raycast/api@npm:1.55.2 [cedfb] couldn't be built successfully (exit code 127, logs can be found here: C:\Users\Rod\AppData\Local\Temp\xfs-537fbbc2\build.log)
➤ YN0000: └ Completed in 14s 372ms
➤ YN0000: Failed with errors in 18s 883ms

This is the content of the log:
/bin/bash: C:UsersRodDocumentsprojectscreativedatalangchainjsnode_modules@raycastapibinray: No such file or directory
973216e77b70f200a722ff4a73b59af2d11eba76f066ff0cb6bf241520fdaaf445b1c28dace86f7ee05986599ec#npm:1.55.2)

Script name: postinstall

for some reason there are no directory symbols in the path

yarn build obviously fails

System Info

└─ langchain@workspace:langchain
├─ Version: 0.1.31
│
└─ Dependencies
├─ @anthropic-ai/sdk@npm:^0.9.1 → npm:0.9.1
├─ @aws-sdk/client-s3@npm:^3.310.0 → npm:3.310.0
├─ @aws-sdk/client-sagemaker-runtime@npm:^3.414.0 → npm:3.427.0
├─ @aws-sdk/client-sfn@npm:^3.362.0 → npm:3.362.0
├─ @aws-sdk/credential-provider-node@npm:^3.388.0 → npm:3.388.0
├─ @aws-sdk/types@npm:^3.357.0 → npm:3.378.0
├─ @azure/storage-blob@npm:^12.15.0 → npm:12.15.0
├─ @cloudflare/workers-types@npm:^4.20230922.0 → npm:4.20230922.0
├─ @faker-js/faker@npm:^7.6.0 → npm:7.6.0
├─ @gomomento/sdk-core@npm:^1.51.1 → npm:1.51.1
├─ @gomomento/sdk@npm:^1.51.1 → npm:1.51.1
├─ @google-ai/generativelanguage@npm:^0.2.1 → npm:0.2.1
├─ @google-cloud/storage@npm:^7.7.0 → npm:7.7.0
├─ @jest/globals@npm:^29.5.0 → npm:29.5.0
├─ @langchain/core@~0.1.44 → workspace:langchain-core
├─ @langchain/openai@~0.0.26 → workspace:libs/langchain-openai
├─ @langchain/scripts@~0.0 → workspace:libs/langchain-scripts
├─ @notionhq/client@npm:^2.2.10 → npm:2.2.10
├─ @pinecone-database/pinecone@npm:^1.1.0 → npm:1.1.0
├─ @supabase/supabase-js@npm:^2.10.0 → npm:2.10.0
├─ @tsconfig/recommended@npm:^1.0.2 → npm:1.0.2
├─ @types/d3-dsv@npm:^2 → npm:2.0.3
├─ @types/decamelize@npm:^1.2.0 → npm:1.2.0
├─ @types/handlebars@npm:^4.1.0 → npm:4.1.0
├─ @types/html-to-text@npm:^9 → npm:9.0.0
├─ @types/js-yaml@npm:^4 → npm:4.0.5
├─ @types/jsdom@npm:^21.1.1 → npm:21.1.1
├─ @types/pdf-parse@npm:^1.1.1 → npm:1.1.1
├─ @types/uuid@npm:^9 → npm:9.0.1
├─ @types/ws@npm:^8 → npm:8.5.8
├─ @vercel/kv@npm:^0.2.3 → npm:0.2.3
├─ apify-client@npm:^2.7.1 → npm:2.7.1
├─ assemblyai@npm:^4.0.0 → npm:4.0.0
├─ axios@npm:^0.26.0 → npm:0.26.1
├─ binary-extensions@npm:^2.2.0 → npm:2.2.0
├─ cheerio@npm:^1.0.0-rc.12 → npm:1.0.0-rc.12
├─ chromadb@npm:^1.5.3 → npm:1.5.3
├─ couchbase@npm:^4.3.0 → npm:4.3.0
├─ d3-dsv@npm:^2.0.0 → npm:2.0.0
├─ dotenv@npm:^16.0.3 → npm:16.0.3
├─ dpdm@patch:dpdm@npm%3A3.12.0#./.yarn/patches/dpdm-npm-3.12.0-0dfdd8e3b8.patch::locator=langchainjs%40workspace%3A. → patch:dpdm@npm%3A3.12.0#./.yarn/patches/dpdm-npm-3.12.0-0dfdd8e3b8.patch::version=3.12.0&hash=2406a8&locator=langchainjs%40workspace%3A.
├─ epub2@npm:^3.0.1 → npm:3.0.1
├─ eslint-plugin-no-instanceof@npm:^1.0.1 → npm:1.0.1
├─ eslint@npm:^8.33.0 → npm:8.35.0
├─ fast-xml-parser@npm:^4.2.7 → npm:4.2.7
├─ google-auth-library@npm:^8.9.0 → npm:8.9.0
├─ handlebars@npm:^4.7.8 → npm:4.7.8
├─ html-to-text@npm:^9.0.5 → npm:9.0.5
├─ ignore@npm:^5.2.0 → npm:5.2.4
├─ ioredis@npm:^5.3.2 → npm:5.3.2
├─ jest-environment-node@npm:^29.6.4 → npm:29.6.4
├─ js-tiktoken@npm:^1.0.7 → npm:1.0.7
├─ js-yaml@npm:^4.1.0 → npm:4.1.0
├─ jsonpointer@npm:^5.0.1 → npm:5.0.1
├─ langchainhub@npm:~0.0.8 → npm:0.0.8
├─ langsmith@npm:~0.1.7 → npm:0.1.7
├─ mammoth@npm:^1.5.1 → npm:1.5.1
├─ ml-distance@npm:^4.0.0 → npm:4.0.0
├─ node-llama-cpp@npm:2.7.3 → npm:2.7.3
├─ notion-to-md@npm:^3.1.0 → npm:3.1.0
├─ officeparser@npm:^4.0.4 → npm:4.0.4
├─ openai@npm:^4.32.1 → npm:4.32.1
├─ openapi-types@npm:^12.1.3 → npm:12.1.3
├─ p-retry@npm:4 → npm:4.6.2
├─ pdf-parse@npm:1.1.1 → npm:1.1.1
├─ peggy@npm:^3.0.2 → npm:3.0.2
├─ playwright@npm:^1.32.1 → npm:1.32.1
├─ prettier@npm:^2.8.3 → npm:2.8.4
├─ puppeteer@npm:^19.7.2 → npm:19.7.2
├─ pyodide@npm:^0.24.1 → npm:0.24.1
├─ redis@npm:^4.6.6 → npm:4.6.6
├─ release-it@npm:^15.10.1 → npm:15.10.1
├─ rimraf@npm:^5.0.1 → npm:5.0.1
├─ rollup@npm:^3.19.1 → npm:3.19.1
├─ sonix-speech-recognition@npm:^2.1.1 → npm:2.1.1
├─ srt-parser-2@npm:^1.2.3 → npm:1.2.3
├─ typescript@patch:typescript@~5.1.6#~builtin<compat/typescript> → patch:typescript@npm%3A5.1.6#~builtin<compat/typescript>::version=5.1.6&hash=1f5320
├─ uuid@npm:^9.0.0 → npm:9.0.0
├─ weaviate-ts-client@npm:^2.0.0 → npm:2.0.0
├─ web-auth-library@npm:^1.0.3 → npm:1.0.3
├─ wikipedia@npm:^2.1.2 → npm:2.1.2
├─ yaml@npm:^2.2.1 → npm:2.2.1
├─ youtube-transcript@npm:^1.0.6 → npm:1.0.6
├─ youtubei.js@npm:^9.1.0 → npm:9.1.0
├─ zod@npm:^3.22.4 → npm:3.22.4
├─ @langchain/community@~0.0.41 → workspace:libs/langchain-community [5e167]
├─ @swc/core@npm:^1.3.90 → npm:1.3.90 [6dbfd]
├─ @swc/jest@npm:^0.2.29 → npm:0.2.29 [6dbfd]
├─ @typescript-eslint/eslint-plugin@npm:^5.58.0 → npm:5.58.0 [cedfb]
├─ @typescript-eslint/parser@npm:^5.58.0 → npm:5.58.0 [cedfb]
├─ @xata.io/client@npm:^0.28.0 → npm:0.28.0 [cedfb]
├─ convex@npm:^1.3.1 → npm:1.3.1 [cedfb]
├─ eslint-config-airbnb-base@npm:^15.0.0 → npm:15.0.0 [cedfb]
├─ eslint-config-prettier@npm:^8.6.0 → npm:8.7.0 [6dbfd]
├─ eslint-plugin-import@npm:^2.27.5 → npm:2.27.5 [cedfb]
├─ eslint-plugin-jest@npm:^27.6.0 → npm:27.6.0 [cedfb]
├─ eslint-plugin-prettier@npm:^4.2.1 → npm:4.2.1 [6dbfd]
├─ jest@npm:^29.5.0 → npm:29.5.0 [6dbfd]
├─ jsdom@npm:^22.1.0 → npm:22.1.0 [cedfb]
├─ mongodb@npm:^5.2.0 → npm:5.2.0 [cedfb]
├─ ts-jest@npm:^29.1.0 → npm:29.1.0 [6dbfd]
├─ typeorm@npm:^0.3.12 → npm:0.3.12 [5e167]
└─ zod-to-json-schema@npm:^3.22.3 → npm:3.22.3 [221f6]
windows
node v20.9.0
yarn 3.4.1

[dosubot[bot]]

Based on the error message you provided, it seems like the issue is related to the bash command not being recognized on your Windows system. The @raycast/api package's postinstall script might be using bash which is not natively available on Windows.

A similar issue was encountered and resolved in the past. You can refer to the issue here. The solution was to use a Unix-like environment on the Windows system, such as Git Bash, Cygwin, or Windows Subsystem for Linux (WSL). This would allow you to run bash commands.

Alternatively, you could try installing the bash command on your system by installing Git for Windows from https://gitforwindows.org/. During the installation, there will be an option called "Select Components". Make sure to check "Git Bash Here". After the installation, you should be able to use the bash command in the command prompt.

Regarding the path formatting issue, it's a common problem when developing on Windows, as Windows uses backslashes (\) for file paths, whereas Unix-based systems (like Linux and macOS) use forward slashes (/). The error message shows the path without any separators, which indicates that the backslashes might be getting stripped or not properly interpreted.

To resolve this issue, consider the following steps:

1. Ensure Cross-Platform Compatibility in Scripts: If you have scripts that construct file paths, make sure they use path.join() or path.resolve() from Node.js's path module, as these methods automatically handle path separators according to the operating system. For example, use path.join('node_modules', '@raycast', 'api', 'bin', 'ray') to construct paths.

2. Check Environment Variables: Sometimes, paths in environment variables might be incorrectly formatted. Ensure that any paths in your environment variables use the correct separators for Windows.

3. Use Cross-Env Tools: For npm scripts in your package.json, consider using tools like cross-env to set environment variables in a cross-platform compatible way.

4. Modify Shell Configuration: If you're using a Unix-like shell on Windows (e.g., Git Bash, Cygwin), there might be configuration options to better handle Windows paths. Check the documentation for your shell.

5. Check External Tool Configurations: If the issue arises from an external tool (like a bundler or compiler), check its documentation for Windows-specific configurations. Some tools require specific settings or plugins to handle Windows paths correctly.

6. Manually Adjust the Path: As a last resort, if a specific path is causing issues, you might manually adjust it in the configuration or script causing the problem. This is not an ideal solution, as it reduces portability and maintainability of your code.

Please try the suggested solutions and let me know if the issue persists.

Sources

• Yarn build failed with @raycast/api
• libs/langchain-scripts/src/build.ts

About Dosu

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.

[hannibalov]

That's correct! yarn works in bash, but not in windows default terminal. However, now I have an error when I run yarn build:

[Error: EBUSY: resource busy or locked, unlink 'C:\Users\Rod\Documents\projects\creativedata\langchainjs\libs\langchain-scripts.turbo\turbo-build.log'] {
errno: -4082,
code: 'EBUSY',
syscall: 'unlink',
path: 'C:\Users\Rod\Documents\projects\creativedata\langchainjs\libs\langchain-scripts\.turbo\turbo-build.log'
}

[MJDeligan]

I faced the same kind of issue using Windows. I've switched to WSL (not in a mounted directory) which works without issue. If that's an option for you, I recommend it.