[GH-ISSUE #167] scan-todos script uses incorrect import path for globSync #111

New issue

Closed

opened 2026-10-15 18:21:14 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:21:14 +00:00

Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/167

Summary

scan-todos imports globSync from node:fs (non-existent in Node's fs API surface), which is an odd/non-portable module source.

Evidence

scripts/scan-todos.mjs:4:
- import { globSync } from "node:fs";
The script then calls globSync(...) as if it were Node's glob export.

Impact

Runtime portability depends on Node's implementation quirks. Importing from node:fs can fail in environments where this re-export is unavailable, breaking this script.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/167 ## Summary `scan-todos` imports `globSync` from `node:fs` (non-existent in Node's `fs` API surface), which is an odd/non-portable module source. ## Evidence - `scripts/scan-todos.mjs:4`: - `import { globSync } from "node:fs";` - The script then calls `globSync(...)` as if it were Node's `glob` export. ## Impact Runtime portability depends on Node's implementation quirks. Importing from `node:fs` can fail in environments where this re-export is unavailable, breaking this script.

bsakaguchi

2026-10-15 18:21:14 +00:00