Back to Explore

inspect-js/typed-array-byte-offset

GitHub
2 watchersOpen source

Last release:

typed-array-byte-offset is a small JavaScript utility that returns the byte offset of a Typed Array, or false if the input is not a Typed Array. It is designed to work robustly across realms and engines, including when a Typed Array’s byteOffset property has been overridden.

Project status

  • The repository appears quiet and likely in maintenance mode, with the last upstream push on 2024-12-19, which is well over a year ago relative to 2026-06-09.
  • The update cadence is sporadic, with several tags in 2023-2024 and then no further updates after v1.0.4 (2024-12-19).

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.0.4

    Release v1.0.4 makes no stated API or behavior changes in the provided release notes (none were supplied). The diff shows mostly TypeScript typing refactors, internal test/workflow additions, and several dependency version bumps that could indirectly affect behavior.

  • v1.0.3

    v1.0.3 is a small patch release focused on removing reliance on the `__proto__` accessor when determining TypedArray `byteOffset` behavior. The runtime logic was adjusted to use a `Reflect.getPrototypeOf` polyfill approach instead, while most other changes are dev/CI related.

  • v1.0.2

    Release v1.0.2 was published on 2024-02-20, but no release notes were provided by the publisher. As a result, there is insufficient information to identify new features, breaking changes, bug fixes, security updates, or dependency changes from the provided data.

  • v1.0.1

    Release v1.0.1 contains a small refactor in the main entry file and a set of dependency updates. No release notes were provided, so changes are inferred directly from the code diff and package metadata.

  • v1.0.0

    Release v1.0.0 was published on 2023-06-06, but no release notes were provided by the publisher. As a result, the change log does not list new features, bug fixes, security updates, or migration steps, so developer impact cannot be determined from the provided documentation.