canirequire

canirequire › CommonJS › ts-mocha

Is ts-mocha ESM-only? Can you require() it?

Mocha thin wrapper that allows running TypeScript tests with TypeScript runtime (ts-node) to get rid of compilation complexity

Last verified Sep 9, 2026 against ts-mocha@11.1.0. Markdown · JSON

CommonJS CommonJS on paper — require() failed in our runtime test

ts-mocha declares a CommonJS entry only, but require("ts-mocha") failed on every Node.js version in our probe: Error. import "ts-mocha" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

What to do

  1. require("ts-mocha") failed in our probe on every Node.js version (Error); check the package README for peer dependencies or setup before relying on it.
  2. From ES modules use the default import: import tsMocha from "ts-mocha"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for ts-mocha; declare the module yourself if you need them.
Latest
11.1.0 (Feb 20, 2025)
Module format
CommonJS
Last CommonJS version
11.1.0
TypeScript types
None
Node engines
>= 6.X.X
Weekly downloads
453K
License
MIT

Does ts-mocha@11.1.0 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("ts-mocha") from a CommonJS file and import "ts-mocha" from an ES module.

Runtimerequire("ts-mocha")import "ts-mocha"
Node.js 18✗ failsError✗ failsError
Node.js 20✗ failsError✗ failsError
Node.js 22✗ failsError✗ failsError
Node.js 24✗ failsError✗ failsError
Node.js 26✗ failsError✗ failsError
Bun 1.4.0✗ failsError✗ failsError

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import ts-mocha

ES modules (import)

import tsMocha from "ts-mocha";

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)

// require("ts-mocha") failed in our probe on every Node.js version we test (Error); see the runtime table.
const tsMocha = require("ts-mocha");

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 (18 versions; the newest 18 shown).

VersionsFormatFirst published
0.1.1 – 11.1.0CommonJSDec 10, 2016

Frequently asked

Is ts-mocha ESM-only?

ts-mocha@11.1.0 declares a CommonJS entry, but require() fails at runtime. ts-mocha declares a CommonJS entry only, but require("ts-mocha") failed on every Node.js version in our probe: Error. import "ts-mocha" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

Can I require ts-mocha?

Not in practice. ts-mocha declares a CommonJS entry, but require("ts-mocha") failed on every Node.js version in our probe: Error. Check the package README for peer dependencies or setup before relying on it.

Can I import ts-mocha with ES module syntax?

Yes. import tsMocha from "ts-mocha" 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 ts-mocha work in Bun?

Importing ts-mocha failed in Bun 1.4.0 on Sep 9, 2026.

Does ts-mocha ship TypeScript types?

No. ts-mocha ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity