canirequire

canirequire › CommonJS › run-sequence

Is run-sequence ESM-only? Can you require() it?

Run a series of dependent gulp tasks in order

Last verified Sep 9, 2026 against run-sequence@2.2.1. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

run-sequence ships CommonJS only. require("run-sequence") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8.0. import "run-sequence" 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

  1. require("run-sequence") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8.0.
  2. From ES modules use the default import: import runSequence from "run-sequence"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: npm install -D @types/run-sequence
Latest
2.2.1 (Jan 3, 2018)
Module format
CommonJS
Last CommonJS version
2.2.1
TypeScript types
@types/run-sequence
Node engines
>= 0.8.0
Weekly downloads
95K
License
MIT

Does run-sequence@2.2.1 actually load? Runtime test results

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

Runtimerequire("run-sequence")import "run-sequence"
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 run-sequence

ES modules (import)

import runSequence from "run-sequence";

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 runSequence = require("run-sequence");

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

VersionsFormatFirst published
0.3.1 – 2.2.1CommonJSJan 23, 2014

Frequently asked

Is run-sequence ESM-only?

run-sequence@2.2.1 is a CommonJS package. run-sequence ships CommonJS only. require("run-sequence") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 0.8.0. import "run-sequence" 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 run-sequence with ES module syntax?

Yes. import runSequence from "run-sequence" 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 run-sequence work in Bun?

Yes. import "run-sequence" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does run-sequence ship TypeScript types?

Not bundled. Install the community types with "npm install -D @types/run-sequence".

Links

Other commonjs packages

Similar popularity