Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ENOENT: no such file or directory during install

Open
#468 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
tooling

Research direction

Start by reproducing the warning with pnpm install and inspect the apache-arrow package path named in the error, especially bin/arrow2csv.cjs. Trace why the package manager tries to create the arrow2csv bin for @duckdb/duckdb-wasm; done means installation completes without the reported ENOENT warnings.

Written by the indexing model from the issue text.

Description

Describe the bug, including details regarding any error messages, version, and platform.

I'm not sure what this dependency is, but it's in my dependency graph somehow, and is now responsible for a couple of warnings at the end of our pnpm install:

10:11:40  [WARN] Failed to create bin at /home/jenkins/workspace/Geiger/geiger-audit-deps/common/temp/node_modules/.pnpm/@[email protected]/node_modules/@duckdb/duckdb-wasm/node_modules/.bin/arrow2csv. ENOENT: no such file or directory, open '/home/jenkins/workspace/Geiger/geiger-audit-deps/common/temp/node_modules/.pnpm/[email protected]/node_modules/apache-arrow/bin/arrow2csv.cjs'
10:11:40  [WARN] Failed to create bin at /home/jenkins/workspace/Geiger/geiger-audit-deps/common/temp/node_modules/.pnpm/[email protected]/node_modules/apache-arrow/node_modules/.bin/arrow2csv. ENOENT: no such file or directory, open '/home/jenkins/workspace/Geiger/geiger-audit-deps/common/temp/node_modules/.pnpm/[email protected]/node_modules/apache-arrow/bin/arrow2csv.cjs'
Dominant language
TypeScript
Stars
112
Forks
23
Avg merge
1d 10h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-js

All issues in apache/arrow-js

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.