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

[JS] Build on Vercel for @apache-arrow/ts fails

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

Start in ipc/reader.ts at line 116 and inspect the return type expected from streamAdapters.toDOMStream. Run npm run build to reproduce the TypeScript error, then verify that the package builds successfully for a Vercel deployment without the implicit-any failure.

Written by the indexing model from the issue text.

Description

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

When trying to deploy an application to Vercel containing @apache-arrow/ts, I receive the following error message:

22:25:40.719 |  
22:25:40.719 | ./node_modules/@apache-arrow/ts/ipc/reader.ts:116:12
22:25:40.719 | Type error: 'toDOMStream' implicitly has return type 'any' because it does not have a return type annotation and is referenced directly or indirectly in one of its return expressions.
22:25:40.719 |  
22:25:40.719 | 114 \|         return (<AsyncIterableIterator<RecordBatch<T>>>this._impl)[Symbol.asyncIterator]();
22:25:40.719 | 115 \|     }
22:25:40.719 | > 116 \|     public toDOMStream() {
22:25:40.719 | \|            ^
22:25:40.719 | 117 \|         return streamAdapters.toDOMStream<RecordBatch<T>>(
22:25:40.720 | 118 \|             (this.isSync()
22:25:40.720 | 119 \|                 ? { [Symbol.iterator]: () => this } as Iterable<RecordBatch<T>>
22:25:41.308 | Error: Command "npm run build" exited with 1

I'm unsure how I can fix this personally. Thanks for any hints!

Component(s)

JavaScript

Dominant language
TypeScript
Stars
112
Forks
23
Avg merge
17h 55m
Merged PRs (30d)
10

Contributor guide

Open the contributing guide

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.