vivek1729 commented on issue #39970: URL: https://github.com/apache/arrow/issues/39970#issuecomment-2174562594
@domoritz, @trxcllnt - I did try importing specific classes from `Arrow.dom` in our code but that didn't seem to work either. Can you elaborate more on how to pull in `Arrow.dom` and not `Arrow.node`? Are you referring to the type replacement pattern recommended by @andriy101 ? I finally had some time to create a minimal repro for this typing issue. I've created the repo [apache-arrow-angular-type-issue-repro](https://github.com/vivek1729/apache-arrow-angular-type-issue-repro/tree/master) to illustrate this issue. I simply used the [angular cli tool](https://angular.dev/tools/cli/setup-local#create-a-workspace-and-initial-application) to scaffold a very simple angular web app. The main changes to repro the issue can be found in [app.component.ts](https://github.com/vivek1729/apache-arrow-angular-type-issue-repro/blob/master/src/app/app.component.ts). Here are the repro steps: - Clone the repo - `npm install` at the project repo to install all the dependencies - Uncomment line 12 i.e. the apache-arrow import line in app.component.ts - Run `ng serve` at the project root You'll start seeing build errors of this type as soon as you uncomment the import line for the apache-arrow package:  If you uncomment that line, the ng serve automatically picks up changes and builds without any errors. I think the `setTimeout` example illustrates how the node types are getting pulled into the build with the `apache-arrow` package import. Hope this helps clarify and debug the issue I shared earlier. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
