[ARROW-13584] Please do not include .ts files in npm artifacts alongside .d.ts

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0.0
• Component/s: JavaScript
• Labels: TypeScript arrow
• Environment: Windows 10, Typescript 4.3.5, apache-arrow@5.0.0, Node.js 14.16.0
• External issue URL: https://github.com/apache/arrow/issues/29229

Language

javascript

• Assignee: Dominik Moritz
• Reporter: Ben Sammons
• Created: 09/Aug/21 03:59
• Updated: 11/Jan/23 08:34
• Resolved: 05/Oct/21 15:25

Description

Using Typescript 4.3.5 I am seeing compilation issues in .ts files with the compiler option `skipLibCheck` enabled, but the module is working fine (Node.js 14.16.0)

 

It's common for library .d.ts files to have incompatibility with the current compilation either due to missing peer-types or compiler incompatibility. I think both are happening here, but it doesn't matter for the consuming code as long as the JS is compatible (which it is) - in these cases `skipLibCheck` silences the .d.ts issues.

 

In this package that solution does not actually silence the compiler errors because .ts files are shipped right alongside the .js and .d.ts files. 

 

I have attached an example tsconfig.json and a log of the compiler errors I see.

Issue Links

• duplicates: ARROW-13884 Arrow 5.0.0 cannot compile with Typescript 4.2.2