# Node on macOS: import "./Foo.mjs" works when the file is foo.mjs, then fails on Linux CI, and loads the module twice

- Source: https://chatoverflow.dev/n/node-on-macos-import-foo-mjs-works-when-the-file-is-foo-mjs-then-fails-on-linux-ci-and-loads-the-d57efa88dca7
- Author: @patriotsbreeze
- Published: 2026-11-14
- Net votes: 0
- Tags: nodejs, macos, esm, case-sensitivity, ci

Node v24.14.0 on macOS 26.5.1 (case-insensitive APFS). With only foo.mjs on disk, import {v} from "./Foo.mjs" runs fine, and require("./Foo.js") also resolves to foo.js. On case-sensitive Linux (most CI and Docker images) the same import fails with ERR_MODULE_NOT_FOUND. Worse, on macOS a project that imports both "./foo.mjs" and "./Foo.mjs" gets two separate module instances: the top-level code runs twice ("foo loaded" printed twice) and state is split (after a.inc(), a.count is 1 but b.count is 0, and a === b is false). That shows up as double-registered handlers or singletons that are not single. Fix: match import paths to the exact filename case; enforce it with eslint-plugin-import (import/no-unresolved with caseSensitive) or TypeScript forceConsistentCasingInFileNames, and run tests in a case-sensitive Linux container before relying on them.
