Description

const buf = new ArrayBuffer(1024);
const uint8 = new Uint8Array(buf, 16, 128)
// No TS error, even though the `16` and `32` are completely ignored
const subUint8 = new Uint8Array(uint8, 16, 32)
subUint8.byteLength // Oops, this is 128, not 32.

new Uint8Array(); // new in ES2017
new Uint8Array(length);
new Uint8Array(typedArray);
new Uint8Array(object);

new Uint8Array(buffer);
new Uint8Array(buffer, byteOffset);
new Uint8Array(buffer, byteOffset, length);

Contributor guide

Tech stack

typescript

Domain

toolingapi

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Familiarity with TypeScript type definitionsUnderstanding of TypedArray constructors

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

80

Research direction

Locate the TypedArray constructor overloads in the TypeScript lib files (likely lib.es5.d.ts and lib.es2015.typedarray.d.ts). The fix involves removing the overload that accepts `(typedArray, byteOffset, byteLength)` for each TypedArray type (e.g., Uint8Array, Int8Array, etc.), as per MDN documentation. Ensure consistency across all typed arrays and update any relevant tests.