canirequire › CommonJS › typed-array-byte-offset
Is typed-array-byte-offset ESM-only? Can you require() it?
Robustly get the byte offset of a Typed Array
Last verified Sep 9, 2026 against typed-array-byte-offset@1.0.4. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
typed-array-byte-offset ships CommonJS only. require("typed-array-byte-offset") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "typed-array-byte-offset" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
What to do
- require("typed-array-byte-offset") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4.
- From ES modules use the default import: import typedArrayByteOffset from "typed-array-byte-offset"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does typed-array-byte-offset@1.0.4 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("typed-array-byte-offset") from a CommonJS file and import "typed-array-byte-offset" from an ES module.
| Runtime | require("typed-array-byte-offset") | import "typed-array-byte-offset" |
|---|---|---|
| Node.js 18 | ✓ works | ✓ works |
| Node.js 20 | ✓ works | ✓ works |
| Node.js 22 | ✓ works | ✓ works |
| Node.js 24 | ✓ works | ✓ works |
| Node.js 26 | ✓ works | ✓ works |
| Bun 1.4.0 | ✓ works | ✓ works |
How to import typed-array-byte-offset
ES modules (import)
import typedArrayByteOffset from "typed-array-byte-offset";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
const typedArrayByteOffset = require("typed-array-byte-offset");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (5 versions; the newest 5 shown).
| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.0.4 | CommonJS | Jun 6, 2023 |
Frequently asked
Is typed-array-byte-offset ESM-only?
typed-array-byte-offset@1.0.4 is a CommonJS package. typed-array-byte-offset ships CommonJS only. require("typed-array-byte-offset") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.4. import "typed-array-byte-offset" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.
Can I import typed-array-byte-offset with ES module syntax?
Yes. import typedArrayByteOffset from "typed-array-byte-offset" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does typed-array-byte-offset work in Bun?
Yes. import "typed-array-byte-offset" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does typed-array-byte-offset ship TypeScript types?
Yes. typed-array-byte-offset bundles its own type declarations; no @types package is needed.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- @aws-sdk/nested-clients 3.997.44Dual
- @humanfs/core 0.19.2ESM-only
- leven 4.1.0ESM-only
- unist-util-is 6.0.1ESM-only
- lz-string 1.5.0CommonJS
- unist-util-visit-parents 6.0.2ESM-only
- string.prototype.matchall 4.1.0CommonJS
- is-weakset 2.0.4CommonJS