refactor: Move fs/path to top-level imports in webpack plugin

[lightninglu10]

Summary

Refactors the webpack plugin to move dynamic require() calls for Node.js core modules (fs and path) to top-level ES6 imports. This follows conventional Node.js/TypeScript patterns and improves code maintainability.

Changes

• Added top-level imports for fs and path modules
• Removed dynamic require() calls from inside the getAliasMap method

Problem

Previously, the getAliasMap method had dynamic requires inside its body:

const fs = require("fs");
const path = require("path");

This is unconventional and could cause issues with module resolution and bundling.

Solution

Moved these to ES6 imports at the top of the file alongside other imports:

import fs from "fs";
import path from "path";

Test plan

• Build the project successfully
• Verify webpack plugin still resolves tsconfig.json aliases correctly
• Test with a Next.js project that uses @ path alias

🤖 Generated with Claude Code

[github-actions]

❇️ CodePress Review Summary

👋 Hey team,

Overall the changes look great! No specific issues found.

Here's the quick rundown:

✅ Decision: APPROVE
No clear blocking issues identified. The change is a safe refactor; only potential concern is TS interop configuration, which can be validated during type-check/build.