canirequire

canirequire › CommonJS › fsevents

Is fsevents ESM-only? Can you require() it?

Native Access to MacOS FSEvents

Last verified Sep 9, 2026 against fsevents@2.3.3. Markdown · JSON

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

fsevents ships CommonJS only. require("fsevents") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^8.16.0 || ^10.6.0 || >=11.0.0. import "fsevents" 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("fsevents") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^8.16.0 || ^10.6.0 || >=11.0.0.
  2. From ES modules use the default import: import fsevents from "fsevents"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
2.3.3 (Aug 21, 2023)
Module format
CommonJS
Last CommonJS version
2.3.3
TypeScript types
Bundled
Node engines
^8.16.0 || ^10.6.0 || >=11.0.0
Weekly downloads
30.2M
License
MIT

Does fsevents@2.3.3 actually load? Runtime test results

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

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

ES modules (import)

import fsevents from "fsevents";

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 fsevents = require("fsevents");

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

VersionsFormatFirst published
0.2.0 – 2.3.3CommonJSJan 31, 2014

Frequently asked

Is fsevents ESM-only?

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

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

Yes. import "fsevents" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does fsevents ship TypeScript types?

Yes. fsevents bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity