Use import statement instead of require()

[mcdonnnj]

🗣 Description

This pull request replaces use of Node.js's require() function with the now standard import syntax.

💭 Motivation and context

It is good to stay up-to-date. This is also necessary to move this action toward being an ECMAScript module.

🧪 Testing

I tested this locally with local-action

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All new and existing tests pass.
• Bump major, minor, patch, pre-release, and/or build versions as appropriate via the bump_version script if this repository is versioned and the changes in this PR warrant a version bump.

✅ Post-merge checklist

• Create a release (necessary if and only if the version was bumped).

[Copilot]

Pull request overview

This PR updates the action’s source to use ES module import syntax instead of CommonJS require(), as a step toward an eventual ESM migration, and refreshes the bundled dist/ output accordingly.

Changes:

• Replace require() usage with import in src/main.js and src/index.js
• Rebuild the bundled action output in dist/index.js
• Bump the package version to 1.3.0

Reviewed changes

Copilot reviewed 3 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/main.js	Switches to import statements for action dependencies
src/index.js	Switches entrypoint to import the run function
package.json	Version bump to 1.3.0
package-lock.json	Lockfile version alignment with package.json bump
dist/index.js	Updated ncc/webpack bundle reflecting source module changes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

src/main.js now uses ESM import syntax but still exports via module.exports. When bundled by ncc/webpack this is treated as an ES module and the generated runtime decorates module.exports to throw, causing the action to fail at runtime. Convert this module to ESM exports (e.g., export { run } / export async function run) or revert back to CommonJS require/module.exports consistently.

[Copilot]

src/index.js imports a named export run from ./main, but main.js currently exports via module.exports = { run }. With the new ESM-style imports this interop is fragile and, as currently bundled, results in the generated code treating main as an ES module while it still assigns module.exports. Make main.js an ES module export (and import accordingly), or keep both files in CommonJS. Also, if the intent is to run these sources as native ESM later, Node will require explicit .js extensions in relative imports.

Suggested change

	import { run } from "./main";
	const { run } = require("./main");